nannaklok.dk

📜 Historical scan 2026-07-31 11:28:19 · ← Latest scan

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

nannaklok.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 October 2017 (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#

2 records 167ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

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

192ms

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-24 14:07:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-10-08
Expires	2026-10-31 (6d)

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

167ms

168ms

AAAA

146ms

TXT

601ms

CAA

145ms

HTTPS

167ms

TLSA

116ms

SOA

25ms

MTA-STS

174ms

DNSSEC

192ms

SRV

169ms

Total

1391ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-23 06:20:46	1872ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:06:45	27296ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:43:58	8907ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:40:15	1323ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:22:35	5553ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:04:59	8877ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 01:29:55	6651ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 14:07:21	831ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 03:58:16	10127ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 14:26:07	27172ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 04:26:10	4805ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 00:01:38	27499ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:51:33	10116ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 05:04:20	2390ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 11:28:19 shown	1391ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 18:14:22	2493ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 04:44:48	751ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:55:08	16723ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 03:29:40	917ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:06:50	774ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:18:40	918ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:43:00	2830ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:48:21	847ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 04:30:59	935ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 03:16:51	16774ms	2 NS 0 A 0 MX	❓ Unknown