arden-kommune.dk

📜 Historical scan 2026-08-08 00:57:54 · ← Latest scan

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

arden-kommune.dk is a registered .dk domain whose nameservers (ns1.euro909.com, ns3.euro909.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 April 2000 (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 328ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.euro909.com	156.154.130.100 2610:a1:1022::100	ns1.ascio.net kandns06.digitalarchives.com	AS12008 Vercara, LLC AS12008 Vercara, LLC
ns3.euro909.com	156.154.131.100 2610:a1:1023::100	pdns2.cscdns.net indom80.indomco.hk	AS12008 Vercara, LLC AS12008 Vercara, 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#

372ms

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-15 17:49:23

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2000-04-07
Expires	2027-06-30 (249d)

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

328ms

308ms

298ms

AAAA

308ms

TXT

1468ms

CAA

324ms

HTTPS

317ms

TLSA

292ms

SOA

47ms

MTA-STS

323ms

DNSSEC

372ms

SRV

320ms

Total

2933ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-20 23:29:40	4731ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-08 05:45:58	2587ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 16:25:20	10935ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 11:09:14	2909ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:43:22	6317ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:39:49	1706ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:12:02	3770ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:31:17	7141ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 01:07:00	11186ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:12:20	3520ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 03:11:51	4019ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:16:51	3445ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:55:30	5165ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 00:57:54 shown	2933ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 12:06:48	3826ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 10:46:06	18501ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 21:44:29	9083ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:19:41	1197ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:51:49	1059ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:32:59	1239ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:45:38	1182ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 15:53:01	10842ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:22:17	10900ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 16:29:36	10955ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 10:21:22	17770ms	2 NS 0 A 0 MX	❓ Unknown