bjoerkman.dk

📜 Historical scan 2026-08-16 21:17:04 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

bjoerkman.dk is a registered .dk domain whose nameservers (ns.gullestrupnet.dk, ns2.gullestrupnet.dk, ns5.gullestrupnet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 January 2007 (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#

3 records 2144ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.gullestrupnet.dk	82.165.189.144	gn51.gullestrupnet.dk	AS8560 IONOS SE
ns2.gullestrupnet.dk	82.165.203.134	mail51.gullestrupnet.dk	AS8560 IONOS SE
ns5.gullestrupnet.dk	82.165.124.183	—	AS8560 IONOS SE

🌍 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#

1397ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: ncache nxdomain

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-15 13:07:34

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-01-09
Expires	2027-01-31 (102d)

🔗 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#

2144ms

89ms

153ms

AAAA

94ms

TXT

507ms

CAA

158ms

HTTPS

2143ms

TLSA

100ms

SOA

92ms

MTA-STS

154ms

DNSSEC

1397ms

SRV

2196ms

Total

8998ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 00:59:52	18076ms	3 NS 0 A 0 MX	❓ Unknown
2026-10-08 05:50:51	11900ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 00:15:21	12712ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:16:49	15144ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:02:21	11386ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 16:49:20	17290ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 14:54:56	14593ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 14:51:02	14298ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 21:17:04 shown	8998ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:15:56	14495ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:10:00	20648ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:01:33	10283ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:32:54	17396ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 03:01:32	12183ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 21:59:50	21216ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 13:42:02	20222ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 09:01:45	10819ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:50:49	12075ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:19:00	14853ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:34:36	11522ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:28:40	17785ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:14:38	11022ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:07:55	10976ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:00:11	14915ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 07:20:51	17472ms	3 NS 0 A 0 MX	❓ Unknown