detdaligemeget.dk

Records from scan: 2026-10-06 10:35:27 · 844ms total · last checked 2026-10-27 04:47 (unchanged)

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

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

🖥️ Nameservers#

2 records 58ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.nameservices.us	—	—	—
ns2.nameservices.us	—	—	—

🌍 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

🧩 Web & zone#

checked 2026-10-05 10:13:24

www	Address record (no CNAME)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

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

🔐 DNSSEC#

72ms

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-12 14:34:53

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2003-04-07
Expires	2027-04-30 (184d)

🔗 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#

58ms

54ms

56ms

AAAA

50ms

TXT

116ms

CAA

49ms

HTTPS

42ms

TLSA

33ms

SOA

23ms

MTA-STS

52ms

DNSSEC

72ms

SRV

67ms

Total

844ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-06 10:35:27 shown	844ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-05 10:13:24	2570ms	2 NS 1 A 1 MX	🔓 Insecure
2026-10-02 10:00:34	3717ms	2 NS 1 A 1 MX	🔓 Insecure
2026-10-01 09:40:55	3374ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-30 09:37:20	3315ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-29 09:24:50	3272ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-28 09:20:56	3190ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-27 09:09:44	3142ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-26 09:01:34	3306ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-25 08:52:14	3303ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-24 08:41:28	3368ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-23 08:40:07	3526ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-16 07:14:50	3373ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-14 23:56:55	3340ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-12 21:25:40	4505ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-11 19:27:19	6542ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-07 18:37:19	3228ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-05 08:42:24	3256ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-30 17:54:51	3960ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-29 17:24:44	3625ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-28 17:18:55	3317ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-27 16:58:28	2788ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-26 19:47:29	3059ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-23 13:04:34	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:29:10	65535ms	2 NS 0 A 0 MX	❓ Unknown