skjoldbroder.dk

Historical scan 2026-07-27 18:05:47  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

skjoldbroder.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 7 February 2001 (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   166ms

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-07 05:12:27
www5.75.225.158 (AS24940) (address records, no CNAME)
www vs bare domainSame network
skjoldbroder.dk: 5.75.225.158 (AS24940)
www.skjoldbroder.dk: 5.75.225.158 (AS24940)
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

9174ms
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-07 05:28:21
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2001-02-07
Expires2027-03-31 (132d)

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
166ms
A
128ms
MX
116ms
AAAA
218ms
TXT
625ms
CAA
219ms
HTTPS
218ms
TLSA
119ms
SOA
2027ms
MTA-STS
172ms
DNSSEC
9174ms
SRV
270ms
Total
14044ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-07 05:12:27 743ms 2 NS 1 A 0 MX Insecure
2026-10-29 11:36:19 1721ms 2 NS 0 A 0 MX Bogus
2026-09-30 10:55:15 1310ms 2 NS 0 A 0 MX Bogus
2026-08-24 04:29:36 1042ms 2 NS 0 A 0 MX Bogus
2026-08-22 22:33:36 1880ms 2 NS 0 A 0 MX Bogus
2026-08-21 22:10:39 4952ms 2 NS 0 A 0 MX Bogus
2026-08-20 22:03:07 15631ms 2 NS 0 A 0 MX Bogus
2026-08-19 21:26:54 1627ms 2 NS 0 A 0 MX Bogus
2026-08-18 20:56:30 2028ms 2 NS 0 A 0 MX Bogus
2026-08-17 10:50:46 949ms 2 NS 0 A 0 MX Bogus
2026-08-16 01:53:38 3217ms 2 NS 0 A 0 MX Bogus
2026-08-14 18:57:49 3257ms 2 NS 0 A 0 MX Bogus
2026-08-12 23:07:32 3173ms 2 NS 0 A 0 MX Bogus
2026-08-11 21:05:00 871ms 2 NS 0 A 0 MX Bogus
2026-08-10 09:15:26 4024ms 2 NS 0 A 0 MX Bogus
2026-08-07 19:49:16 964ms 2 NS 0 A 0 MX Bogus
2026-08-06 12:21:16 1587ms 2 NS 0 A 0 MX Bogus
2026-07-29 15:13:41 1364ms 2 NS 0 A 0 MX Bogus
2026-07-27 18:05:47 shown 14044ms 2 NS 0 A 0 MX Bogus
2026-07-26 18:01:43 8719ms 2 NS 0 A 0 MX Bogus
2026-07-25 17:19:16 840ms 2 NS 0 A 0 MX Bogus
2026-07-24 17:01:21 26366ms 2 NS 0 A 0 MX Bogus
2026-07-23 15:26:36 952ms 2 NS 0 A 0 MX Bogus
2026-07-22 14:25:56 845ms 2 NS 0 A 0 MX Bogus
2026-07-20 17:14:15 1021ms 2 NS 0 A 0 MX Bogus