bamsefabrik.dk

📜 Historical scan 2026-07-27 21:36:46 · ← Latest scan

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

bamsefabrik.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 12 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 753ms

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#

184ms

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	broken trust chain resolving 'bamsefabrik.dk/A/IN': 127.0.0.1#53

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-11 11:18:50

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

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

753ms

97ms

51ms

AAAA

46ms

TXT

422ms

CAA

47ms

HTTPS

205ms

TLSA

143ms

SOA

201ms

MTA-STS

8118ms

DNSSEC

184ms

SRV

16036ms

Total

23485ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:26:22	10511ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-29 17:28:41	12356ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-01 09:58:37	10755ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:44:55	12755ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:30:31	11127ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:17:14	25686ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 11:01:33	15160ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:34:56	10088ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 05:44:01	12139ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 22:08:45	10316ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 14:07:06	20568ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:59:07	12176ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:48:57	10771ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 06:13:55	12499ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:14:29	11285ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 13:43:34	10744ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 07:41:38	11170ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-04 22:20:36	15530ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:36:46 shown	23485ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 20:39:16	15073ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:10:12	14928ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 19:55:18	9995ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:54:18	22890ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:16:54	18063ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:27:04	16874ms	3 NS 0 A 0 MX	❓ Unknown