whitta.dk

Historical scan 2026-08-16 00:41:31  ·  ← Latest scan
Lame delegation Zone File Timeline & 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 registered on 17 September 2006 (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   356ms

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-25 06:45:08
www94.231.103.148 (AS48854) (address records, no CNAME)
www vs bare domainSame network
whitta.dk: 94.231.103.148 (AS48854)
www.whitta.dk: 94.231.103.148 (AS48854)
WildcardYes: any name under the zone resolves
Denial of existenceNSEC zone can be walked (all names enumerable)
CDS / CDNSKEYPublished: 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#

477ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-26 16:45:21
FieldValue
RegistrarSimply.com A/S
Registered2006-09-17
Expires2027-09-30 (313d)

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#

NS
356ms
A
334ms
MX
341ms
AAAA
329ms
TXT
1324ms
CAA
333ms
HTTPS
341ms
TLSA
205ms
SOA
202ms
MTA-STS
412ms
DNSSEC
477ms
SRV
368ms
Total
4171ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-25 06:45:08 483ms 3 NS 1 A 1 MX Secure
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 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 shown 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