ziebellthoegersen.dk

📜 Historical scan 2026-07-27 01:49:24 · ← Latest scan

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

ziebellthoegersen.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 November 2009 (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 104ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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#

178ms

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: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-22 03:20:01

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2009-11-05
Expires	2026-11-30 (37d)

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

104ms

114ms

110ms

AAAA

108ms

TXT

421ms

CAA

101ms

HTTPS

97ms

TLSA

56ms

SOA

36ms

MTA-STS

77ms

DNSSEC

178ms

SRV

97ms

Total

993ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 04:08:01	1214ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-24 20:27:47	9964ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 03:34:09	10265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:59:24	2889ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 01:54:59	1267ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 01:51:58	4706ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 01:10:48	31346ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:26:05	4519ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 23:42:13	10165ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:55:34	3765ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 00:23:14	2894ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 15:33:48	1533ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:19:13	914ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:23:30	3141ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 14:27:13	51447ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 17:58:12	8896ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 01:40:53	1061ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 01:59:25	1452ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:49:24 shown	993ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:56:44	8774ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 00:47:01	10021ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 22:56:20	925ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:01:06	8824ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:51:07	879ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:01:36	8984ms	2 NS 0 A 0 MX	❓ Unknown