bomberp.dk

📜 Historical scan 2026-08-19 12:05:28 · ← Latest scan

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

bomberp.dk is a registered .dk domain whose nameservers (coco.bunny.net, kiki.bunny.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 15 February 2025 (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 60ms

Nameserver	IP addresses	PTR	ASN / ISP
coco.bunny.net	109.104.147.1 2400:52e0:fff2::1	coco.bunny.net —	AS200325 BUNNYWAY, informacijske storitve d.o.o. AS200325 BUNNYWAY, informacijske storitve d.o.o.
kiki.bunny.net	2400:52e0:fff0::1 91.200.176.1	— kiki.bunny.net	AS200325 BUNNYWAY, informacijske storitve d.o.o. AS200325 BUNNYWAY, informacijske storitve d.o.o.

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

155ms

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 nxrrset

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-11 19:16:57

Field	Value
Registrar	DANDOMAIN A/S
Registered	2025-02-15
Expires	2027-02-14 (120d)

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

60ms

59ms

73ms

AAAA

64ms

TXT

208ms

CAA

64ms

HTTPS

71ms

TLSA

39ms

SOA

70ms

MTA-STS

57ms

DNSSEC

155ms

SRV

1576ms

Total

2193ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 13:17:56	1083ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 01:10:12	657ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 02:06:22	1644ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 22:07:15	1025ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 15:26:28	772ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:36:35	1357ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:39:29	8980ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:13:09	1227ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:04:17	1141ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:05:28 shown	2193ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:03:16	2902ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:24:33	2493ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:35:56	2033ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 01:36:18	2624ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 10:24:01	1128ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:06:06	10207ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 23:43:16	3096ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 22:42:55	924ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:13:14	1082ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:03:33	1073ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:30:59	10980ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:16:02	8875ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:45:36	2670ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:31:06	1151ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:51:54	16710ms	2 NS 0 A 0 MX	❓ Unknown