morsoutdoor.dk

📜 Historical scan 2026-07-28 00:57:03 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

morsoutdoor.dk is a registered .dk domain whose nameservers (ns2.vpweb.com, ns3.vpweb.com, ns4.vpweb.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 February 2013 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

3 records 8072ms

Nameserver	IP addresses	PTR	ASN / ISP
ns2.vpweb.com	52.4.205.198	ec2-52-4-205-198.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.
ns3.vpweb.com	34.246.26.49	ec2-34-246-26-49.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns4.vpweb.com	34.234.174.79	ec2-34-234-174-79.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.

🌍 A Records#

🌍

No A records found

📧 MX Records#

📧

No MX records found

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

📝

No TXT records found

✉️ SPF#

✗ No SPF record — mail spoofing not restricted

📨 DMARC#

✗ No DMARC record — mail spoofing not restricted

📬 MTA-STS#

✗ No MTA-STS policy — SMTP TLS not enforced

📈 TLSRPT#

✗ No TLSRPT record — no SMTP TLS failure reporting

📜 CAA Records#

✗ No CAA records — any CA may issue certificates

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

8103ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-21 11:09:13

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-02-07
Expires	2028-02-29 (495d)

🔗 Same registrant#

0 domains

Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).

No other domain with this registrant in our WHOIS data yet

📋 WHOIS#

⏱️ Lookup Timing#

8072ms

8073ms

AAAA

8080ms

TXT

52204ms

CAA

8065ms

HTTPS

8086ms

TLSA

2039ms

SOA

31ms

MTA-STS

16050ms

DNSSEC

8103ms

SRV

16063ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-21 05:59:49	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-10-09 07:23:42	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-17 12:34:01	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 04:28:15	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-25 19:48:49	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 04:04:38	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:58:27	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:30:46	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:06:16	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:33:55	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:58:48	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:08:01	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 11:54:02	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:11:57	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 00:17:04	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:02:14	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:14:11	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 06:58:57	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 11:28:20	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 07:11:35	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 06:17:02	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 08:16:12	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:57:03 shown	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:19:10	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:46:41	65535ms	3 NS 0 A 0 MX	❓ Unknown