forundringsledelse.dk

Records from scan: 2026-09-28 06:14:32  ·  1536ms total  ·  last checked 2026-11-19 06:29 (unchanged)
Lame delegation Zone File Timeline & History Scan Now

forundringsledelse.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 4 June 2011 (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   119ms

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#

422ms
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-16 12:00:55
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2011-06-04
Expires2027-06-30 (222d)

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
119ms
A
122ms
MX
408ms
AAAA
403ms
TXT
866ms
CAA
112ms
HTTPS
378ms
TLSA
118ms
SOA
25ms
MTA-STS
139ms
DNSSEC
422ms
SRV
186ms
Total
1536ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-28 06:14:32 shown 1536ms 2 NS 0 A 0 MX Bogus
2026-08-26 20:43:31 2960ms 2 NS 0 A 0 MX Bogus
2026-08-23 03:35:48 5655ms 2 NS 0 A 0 MX Bogus
2026-08-22 03:23:03 5986ms 2 NS 0 A 0 MX Bogus
2026-08-21 03:16:28 14586ms 2 NS 0 A 0 MX Bogus
2026-08-20 02:51:00 1203ms 2 NS 0 A 0 MX Bogus
2026-08-19 01:47:48 2902ms 2 NS 0 A 0 MX Bogus
2026-08-17 00:29:11 5507ms 2 NS 0 A 0 MX Bogus
2026-08-15 03:26:09 2827ms 2 NS 0 A 0 MX Bogus
2026-08-13 05:34:14 2917ms 2 NS 0 A 0 MX Bogus
2026-08-12 03:28:49 1421ms 2 NS 0 A 0 MX Bogus
2026-08-10 07:29:13 10192ms 2 NS 0 A 0 MX Bogus
2026-08-08 10:20:30 1577ms 2 NS 0 A 0 MX Bogus
2026-08-06 05:01:58 1694ms 2 NS 0 A 0 MX Bogus
2026-08-03 09:23:00 829ms 2 NS 0 A 0 MX Bogus
2026-07-31 13:13:41 2330ms 2 NS 0 A 0 MX Bogus
2026-07-28 18:28:24 1366ms 2 NS 0 A 0 MX Bogus
2026-07-27 10:20:10 881ms 2 NS 0 A 0 MX Bogus
2026-07-26 10:03:06 8581ms 2 NS 0 A 0 MX Bogus
2026-07-25 09:28:42 10012ms 2 NS 0 A 0 MX Bogus
2026-07-24 08:32:33 868ms 2 NS 0 A 0 MX Bogus
2026-07-23 07:13:20 10173ms 2 NS 0 A 0 MX Bogus
2026-07-22 05:32:21 708ms 2 NS 0 A 0 MX Bogus
2026-07-20 19:58:27 2520ms 2 NS 0 A 0 MX Bogus
2026-07-19 14:35:45 10074ms 2 NS 0 A 0 MX Bogus