zenaarhus.dk

📜 Historical scan 2026-07-24 21:44:10 · ← Latest scan

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

zenaarhus.dk is a registered .dk domain whose nameservers (ns4.dns-123.net, ns5.dns-123.net, ns6.dns-123.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 September 2011 (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 725ms

Nameserver	IP addresses	PTR	ASN / ISP
ns4.dns-123.net	35.198.132.83	83.132.198.35.bc.googleusercontent.com	AS396982 Google LLC
ns5.dns-123.net	35.187.184.173	173.184.187.35.bc.googleusercontent.com	AS396982 Google LLC
ns6.dns-123.net	35.228.54.1	1.54.228.35.bc.googleusercontent.com	AS396982 Google LLC

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

9680ms

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-11 22:08:41

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-09-09
Expires	2027-09-30 (344d)

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

725ms

714ms

638ms

AAAA

725ms

TXT

3304ms

CAA

644ms

HTTPS

717ms

TLSA

637ms

SOA

24ms

MTA-STS

753ms

DNSSEC

9680ms

SRV

727ms

Total

12681ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-26 17:19:25	12583ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-23 03:02:30	5850ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-08 15:10:40	5811ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:55:14	5840ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:08:08	8714ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:04:57	2527ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:45:42	3575ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:20:52	9622ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:05:04	3377ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 08:28:36	6326ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 01:28:30	9627ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 00:34:38	3371ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:16:16	12513ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 20:10:15	1445ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:08:18	1826ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 16:11:43	5518ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 09:54:08	12652ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-05 22:05:07	5811ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 05:19:17	17336ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 23:41:12	2688ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 02:33:18	7769ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:18:44	1885ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:49:36	9089ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:06:39	12448ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:44:10 shown	12681ms	3 NS 0 A 0 MX	❓ Unknown