akkedal.dk

📜 Historical scan 2026-07-19 12:28:29 · ← Latest scan

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

akkedal.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 8 November 2004 (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 166ms

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#

241ms

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-27 05:23:44

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-11-08
Expires	2026-11-30 (34d)

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

166ms

164ms

138ms

AAAA

139ms

TXT

619ms

CAA

215ms

HTTPS

164ms

TLSA

115ms

SOA

24ms

MTA-STS

224ms

DNSSEC

241ms

SRV

220ms

Total

1401ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 21:20:49	33266ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 18:16:10	3682ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:13:16	1339ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:10:15	866ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:45:03	1595ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 11:40:10	27383ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 11:37:20	3132ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 23:20:51	960ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 17:11:09	8743ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:12:13	3556ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:29:17	4591ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:05:27	2681ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 05:26:09	1498ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 20:36:55	10048ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:21:02	2296ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:17:10	822ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:53:03	957ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:39:22	826ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:43:23	27236ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:23:07	1031ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:52:01	825ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:28:29 shown	1401ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 10:01:34	896ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 05:56:04	838ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 13:30:06	8764ms	2 NS 0 A 0 MX	❓ Unknown