aaparken3.dk

📜 Historical scan 2026-08-22 12:20:13 · ← Latest scan

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

aaparken3.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 2 March 2010 (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 78ms

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#

331ms

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-24 01:20:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-03-02
Expires	2027-03-31 (158d)

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

78ms

65ms

78ms

AAAA

59ms

TXT

333ms

CAA

78ms

HTTPS

83ms

TLSA

120ms

SOA

64ms

MTA-STS

133ms

DNSSEC

331ms

SRV

154ms

Total

1488ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 12:34:10	16812ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:20:13 shown	1488ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:54:29	16904ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 11:15:51	11281ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 08:08:04	3661ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 08:02:46	32122ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 22:12:52	3689ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:58:43	13448ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:36:06	3393ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:25:02	27304ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:11:25	8929ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 03:16:49	9115ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 22:30:48	2303ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 12:16:18	10091ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:05:09	741ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:39:00	8750ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:00:50	2871ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 15:28:02	1079ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:55:38	27177ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:00:06	8685ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:44:56	764ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:19:29	909ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 08:03:27	27286ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 23:13:50	10046ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 10:43:52	1394ms	2 NS 0 A 0 MX	❓ Unknown