bobestyrer24.dk

Historical scan 2026-08-13 05:42:04  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

bobestyrer24.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 16 December 2019 (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   194ms

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 21:47:58
www46.30.211.38 (AS51468) (address records, no CNAME)
www vs bare domainSame network
bobestyrer24.dk: 46.30.211.38 (AS51468)
www.bobestyrer24.dk: 46.30.211.38 (AS51468)
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

9192ms
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-10-29 22:03:31
FieldValue
RegistrarONE.COM A/S
Registered2019-12-16
Expires2026-12-31 (41d)

Same registrant#

13 domains
📋 WHOIS#

Lookup Timing#

NS
194ms
A
195ms
MX
197ms
AAAA
200ms
TXT
678ms
CAA
190ms
HTTPS
147ms
TLSA
120ms
SOA
38ms
MTA-STS
199ms
DNSSEC
9192ms
SRV
209ms
Total
10147ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-04 21:47:58 591ms 2 NS 1 A 1 MX Secure
2026-11-01 03:16:20 1413ms 2 NS 1 A 1 MX Secure
2026-09-30 12:55:39 515ms 2 NS 1 A 1 MX Secure
2026-09-25 12:03:16 507ms 2 NS 1 A 1 MX Secure
2026-09-24 11:49:01 576ms 2 NS 1 A 1 MX Insecure
2026-09-19 12:15:46 51264ms 2 NS 0 A 0 MX Unknown
2026-08-26 06:55:42 2768ms 2 NS 0 A 0 MX Bogus
2026-08-24 00:30:52 885ms 2 NS 0 A 0 MX Bogus
2026-08-22 18:09:55 1215ms 2 NS 0 A 0 MX Bogus
2026-08-21 18:05:44 1811ms 2 NS 0 A 0 MX Bogus
2026-08-20 17:46:10 1263ms 2 NS 0 A 0 MX Bogus
2026-08-19 09:02:14 3754ms 2 NS 0 A 0 MX Bogus
2026-08-18 08:59:00 8972ms 2 NS 0 A 0 MX Bogus
2026-08-17 07:33:26 2648ms 2 NS 0 A 0 MX Bogus
2026-08-15 07:42:42 2710ms 2 NS 0 A 0 MX Bogus
2026-08-13 05:42:04 shown 10147ms 2 NS 0 A 0 MX Bogus
2026-08-12 03:52:51 3205ms 2 NS 0 A 0 MX Bogus
2026-08-10 21:32:19 1519ms 2 NS 0 A 0 MX Bogus
2026-08-08 11:28:40 885ms 2 NS 0 A 0 MX Bogus
2026-08-07 00:19:52 894ms 2 NS 0 A 0 MX Bogus
2026-08-05 22:46:39 27137ms 2 NS 0 A 0 MX Unknown
2026-08-04 05:45:46 10027ms 2 NS 0 A 0 MX Bogus
2026-07-31 00:03:34 826ms 2 NS 0 A 0 MX Bogus
2026-07-29 08:41:29 1347ms 2 NS 0 A 0 MX Bogus
2026-07-27 23:29:06 10118ms 2 NS 0 A 0 MX Bogus