bohjelm.dk

Historical scan 2026-08-11 14:20:24  ·  ← Latest scan
Lame delegation Zone File Timeline & History

bohjelm.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 3 June 2009 (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   432ms

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#

552ms
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-15 05:21:30
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2009-06-03
Expires2027-06-30 (219d)

Same registrant#

3 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).

DomainRegistrar
ethusibevaegelse.dkPunktum dk A/S (direct)
pawhjelm.dkPunktum dk A/S (direct)
trinehjelm.dkPunktum dk A/S (direct)
📋 WHOIS#

Lookup Timing#

NS
432ms
A
324ms
MX
323ms
AAAA
468ms
TXT
1441ms
CAA
312ms
HTTPS
452ms
TLSA
198ms
SOA
179ms
MTA-STS
373ms
DNSSEC
552ms
SRV
477ms
Total
3810ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-09 11:27:48 1171ms 2 NS 0 A 0 MX Bogus
2026-09-26 19:00:50 1336ms 2 NS 0 A 0 MX Bogus
2026-09-16 11:58:36 49402ms 2 NS 0 A 0 MX Unknown
2026-08-28 09:58:34 10080ms 2 NS 0 A 0 MX Bogus
2026-08-23 05:49:15 1917ms 2 NS 0 A 0 MX Bogus
2026-08-22 05:44:40 2808ms 2 NS 0 A 0 MX Bogus
2026-08-21 05:22:28 5658ms 2 NS 0 A 0 MX Bogus
2026-08-20 04:26:25 1790ms 2 NS 0 A 0 MX Bogus
2026-08-19 03:42:39 1697ms 2 NS 0 A 0 MX Bogus
2026-08-18 01:22:57 10065ms 2 NS 0 A 0 MX Bogus
2026-08-16 01:19:47 8956ms 2 NS 0 A 0 MX Bogus
2026-08-14 08:39:20 15107ms 2 NS 0 A 0 MX Bogus
2026-08-13 06:05:53 4241ms 2 NS 0 A 0 MX Bogus
2026-08-11 14:20:24 shown 3810ms 2 NS 0 A 0 MX Bogus
2026-08-10 09:48:00 3118ms 2 NS 0 A 0 MX Bogus
2026-08-09 01:29:07 2890ms 2 NS 0 A 0 MX Bogus
2026-08-05 23:01:43 1643ms 2 NS 0 A 0 MX Bogus
2026-08-03 20:48:41 704ms 2 NS 0 A 0 MX Bogus
2026-07-28 23:05:29 2357ms 2 NS 0 A 0 MX Bogus
2026-07-27 22:31:19 1475ms 2 NS 0 A 0 MX Bogus
2026-07-26 22:26:55 10028ms 2 NS 0 A 0 MX Bogus
2026-07-25 22:11:05 1020ms 2 NS 0 A 0 MX Bogus
2026-07-24 22:02:33 1109ms 2 NS 0 A 0 MX Bogus
2026-07-23 18:00:09 1207ms 2 NS 0 A 0 MX Bogus
2026-07-22 17:12:14 1107ms 2 NS 0 A 0 MX Bogus