hanslange.dk

Historical scan 2026-08-19 22:06:24  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

hanslange.dk is a registered .dk domain whose nameservers (ns4.dns-123.net, ns5.dns-123.net, ns6.dns-123.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 December 2005 (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   970ms

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-11-04 05:05:37

DKIM keys#

1 found
SelectorCNAMEKey
default — RSA · ~2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

TLSA / DANE#

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

DNSSEC#

1328ms
CheckResult
Validation Status Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates) Not set
DS Record Found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-04 05:10:12
FieldValue
RegistrarFIONIA IT ApS
Registered2005-12-02
Expires2026-12-31 (43d)

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
970ms
A
1019ms
MX
914ms
AAAA
977ms
TXT
4126ms
CAA
970ms
HTTPS
930ms
TLSA
719ms
SOA
259ms
MTA-STS
1196ms
DNSSEC
1328ms
SRV
1061ms
Total
9149ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-04 05:05:37 652ms 3 NS 1 A 1 MX Insecure
2026-10-23 21:08:47 1314ms 3 NS 1 A 1 MX Insecure
2026-09-26 12:48:54 9777ms 3 NS 1 A 1 MX Insecure
2026-09-08 17:51:57 2634ms 3 NS 1 A 1 MX Insecure
2026-09-02 12:00:45 6049ms 3 NS 0 A 0 MX Bogus
2026-08-23 23:43:06 7246ms 3 NS 0 A 0 MX Bogus
2026-08-22 22:38:24 8686ms 3 NS 0 A 0 MX Bogus
2026-08-21 22:35:37 12677ms 3 NS 0 A 0 MX Bogus
2026-08-20 22:29:42 2550ms 3 NS 0 A 0 MX Bogus
2026-08-19 22:06:24 shown 9149ms 3 NS 0 A 0 MX Bogus
2026-08-18 21:47:25 9550ms 3 NS 0 A 0 MX Bogus
2026-08-17 12:45:38 6580ms 3 NS 0 A 0 MX Bogus
2026-08-16 11:42:35 6731ms 3 NS 0 A 0 MX Bogus
2026-08-15 10:28:20 12511ms 3 NS 0 A 0 MX Bogus
2026-08-12 22:51:01 5589ms 3 NS 0 A 0 MX Bogus
2026-08-11 10:18:32 5505ms 3 NS 0 A 0 MX Bogus
2026-08-08 19:24:51 12561ms 3 NS 0 A 0 MX Bogus
2026-08-07 00:22:52 5520ms 3 NS 0 A 0 MX Bogus
2026-07-31 09:56:54 17232ms 3 NS 0 A 0 MX Bogus
2026-07-29 22:01:04 6740ms 3 NS 0 A 0 MX Bogus
2026-07-27 22:50:48 1954ms 3 NS 0 A 0 MX Bogus
2026-07-26 22:29:20 9361ms 3 NS 0 A 0 MX Bogus
2026-07-25 21:54:50 1928ms 3 NS 0 A 0 MX Bogus
2026-07-24 21:25:45 1907ms 3 NS 0 A 0 MX Bogus
2026-07-23 20:24:41 12401ms 3 NS 0 A 0 MX Bogus