badkompagniet.dk

Historical scan 2026-09-30 22:25:13  ·  ← Latest scan
Lame delegation Zone File Timeline & History

badkompagniet.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 23 January 2012 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 10 November 2026, when it moved from direct registration at Punktum to CURANET A/S. 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   178ms

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#

170ms
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-10 16:37:47
FieldValue
RegistrarCURANET A/S
Registered2012-01-23
Expires2027-01-31 (70d)

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
178ms
A
126ms
MX
113ms
AAAA
151ms
TXT
570ms
CAA
132ms
HTTPS
114ms
TLSA
111ms
SOA
45ms
MTA-STS
125ms
DNSSEC
170ms
SRV
208ms
Total
1276ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-30 19:42:31 17589ms 2 NS 0 A 0 MX Bogus
2026-10-22 06:20:02 65535ms 2 NS 0 A 0 MX Unknown
2026-10-07 21:58:35 1272ms 2 NS 0 A 0 MX Bogus
2026-09-30 22:25:13 shown 1276ms 2 NS 0 A 0 MX Bogus
2026-09-24 21:34:42 1913ms 2 NS 0 A 0 MX Bogus
2026-09-23 21:18:47 391ms 2 NS 1 A 0 MX Secure
2026-08-29 03:11:18 1739ms 2 NS 0 A 0 MX Bogus
2026-08-28 01:40:54 677ms 2 NS 1 A 0 MX Secure
2026-08-22 16:51:46 1172ms 2 NS 0 A 0 MX Bogus
2026-08-21 16:48:21 3240ms 2 NS 0 A 0 MX Bogus
2026-08-20 16:35:55 5532ms 2 NS 0 A 0 MX Bogus
2026-08-19 16:21:41 27609ms 2 NS 0 A 0 MX Unknown
2026-08-18 16:18:07 3011ms 2 NS 0 A 0 MX Bogus
2026-08-17 14:06:14 858ms 2 NS 0 A 0 MX Bogus
2026-08-16 10:31:10 1597ms 2 NS 0 A 0 MX Bogus
2026-08-15 07:26:26 25449ms 2 NS 0 A 0 MX Unknown
2026-08-14 00:43:06 1014ms 2 NS 0 A 0 MX Bogus
2026-08-11 11:11:25 3019ms 2 NS 0 A 0 MX Bogus
2026-08-10 04:38:33 1041ms 2 NS 0 A 0 MX Bogus
2026-08-03 16:02:38 8982ms 2 NS 0 A 0 MX Bogus
2026-07-29 13:21:11 10108ms 2 NS 0 A 0 MX Bogus
2026-07-27 10:03:58 1350ms 2 NS 0 A 0 MX Bogus
2026-07-26 09:31:48 1498ms 2 NS 0 A 0 MX Bogus
2026-07-25 09:22:49 754ms 2 NS 0 A 0 MX Bogus
2026-07-24 07:19:24 29287ms 2 NS 0 A 0 MX Unknown