bogense-hotel.dk

📜 Historical scan 2026-08-10 00:39:59 · ← Latest scan

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

bogense-hotel.dk is a registered .dk domain whose nameservers (nss.servnet.dk, nss2.servnet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 June 2000 (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 4052ms

Nameserver	IP addresses	PTR	ASN / ISP
nss.servnet.dk	195.249.40.2	—	AS3292 TDC Holding A/S
nss2.servnet.dk	195.249.40.3	—	AS3292 TDC Holding A/S

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

10084ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-23 12:43:45

Field	Value
Registrar	nordicway ApS
Registered	2000-06-09
Expires	2027-06-30 (249d)

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

4052ms

4036ms

4041ms

AAAA

4052ms

TXT

20174ms

CAA

4043ms

HTTPS

4040ms

TLSA

2025ms

SOA

4038ms

MTA-STS

4046ms

DNSSEC

10084ms

SRV

4062ms

Total

61318ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 12:27:45	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-03 10:34:07	63093ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 04:03:33	61624ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 06:55:50	63258ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 21:54:24	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 10:23:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 08:43:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:23:13	63153ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:15:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:52:12	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 05:24:54	59404ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 15:37:05	59899ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 04:54:39	57867ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:28:24	59348ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:39:59 shown	61318ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:24:01	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 14:43:16	63329ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 06:09:54	62027ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:40:54	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:32:00	55169ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 07:21:01	63354ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 06:49:40	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:06:49	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:06:05	61226ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 14:09:12	65237ms	2 NS 0 A 0 MX	❓ Unknown