denstorehan.dk

📜 Historical scan 2026-07-25 14:08:54 · ← Latest scan

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

denstorehan.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 4 September 2008 (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 1587ms

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#

2627ms

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-12 09:42:12

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-09-04
Expires	2027-09-30 (345d)

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

1587ms

106ms

1661ms

AAAA

3104ms

TXT

3375ms

CAA

91ms

HTTPS

100ms

TLSA

627ms

SOA

1585ms

MTA-STS

236ms

DNSSEC

2627ms

SRV

987ms

Total

10710ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 22:52:35	17241ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-24 16:13:49	17233ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-06 14:36:22	21399ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-01 01:10:32	8987ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:44:06	12483ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:57:52	15001ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:39:04	14887ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:24:31	18750ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:08:58	19323ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:02:16	12010ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:18:58	16156ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 11:44:48	13589ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:21:47	14868ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:47:06	20151ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 02:17:12	15213ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:43:06	11048ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 09:01:52	20326ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:29:41	17723ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 20:13:02	12869ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 19:40:57	17444ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 17:03:34	11015ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:14:47	11850ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:14:27	13897ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:08:54 shown	10710ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:00:10	18205ms	3 NS 0 A 0 MX	❓ Unknown