whitta.dk

📜 Historical scan 2026-08-18 22:58:38 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Record History ⚡ Scan Now

whitta.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 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 4049ms

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

🧩 Web & zone

latest probe, not this scan · checked 2026-10-03 13:32:49

www	Address record (no CNAME)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE

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

🔐 DNSSEC

10085ms

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: timed out

🏷️ SOA

✗ No SOA record found

📋 Registration

✗ No registration data — collected automatically when SOA serial changes

📋 WHOIS

⏱️ Lookup Timing

4049ms

132ms

2128ms

AAAA

2136ms

TXT

604ms

CAA

4048ms

HTTPS

4037ms

TLSA

4028ms

SOA

38ms

MTA-STS

4047ms

DNSSEC

10085ms

SRV

4056ms

Total

19131ms

🕐 Scan History

Scanned At	Duration	Records	DNSSEC
2026-10-03 13:32:49	365ms	3 NS 1 A 1 MX	🔒 Secure
2026-09-20 14:38:04	725ms	3 NS 1 A 1 MX	🔒 Secure
2026-09-07 04:25:38	24697ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 18:49:40	2835ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:15:36	3714ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:07:59	10090ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:58:14	1139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:46:58	9133ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:19:21	6301ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:58:38 shown	19131ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 03:34:09	2917ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:41:31	4171ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 22:14:48	27979ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 04:08:08	4142ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:23:56	1380ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 08:16:35	10231ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 10:51:49	2384ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 17:12:45	2834ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:04:42	653ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:53:46	862ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:12:16	1411ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:57:47	1358ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:25:43	10016ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:18:53	625ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:24:24	665ms	2 NS 0 A 0 MX	❓ Unknown