hagelberg.dk

📜 Historical scan 2026-07-23 06:36:11 · ← Latest scan

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

hagelberg.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 6 June 2001 (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 16040ms

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#

16080ms

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-15 00:09:35

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-06-06
Expires	2027-06-30 (253d)

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

16040ms

16050ms

2082ms

AAAA

16046ms

TXT

65535ms

CAA

2088ms

HTTPS

16047ms

TLSA

16026ms

SOA

39ms

MTA-STS

16072ms

DNSSEC

16080ms

SRV

16055ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-26 14:11:04	61208ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 10:34:22	61333ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 09:20:13	57743ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 10:01:29	61485ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:44:46	57387ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:21:33	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:20:44	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:17:52	59366ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:40:28	59412ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 04:15:36	63344ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 14:49:49	56870ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:41:24	57024ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 03:39:14	63500ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:27:39	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:06:43	57993ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 06:57:17	61347ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 08:03:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 02:41:37	65319ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 23:13:17	61273ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:59:22	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:23:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:43:48	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 08:40:29	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:36:11 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:59:06	61308ms	2 NS 0 A 0 MX	❓ Unknown