aardance.dk

📜 Historical scan 2026-08-08 21:11:10 · ← Latest scan

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

aardance.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 1 January 2015 (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 130ms

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#

233ms

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-21 08:03:43

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-01-01
Expires	2027-01-31 (99d)

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

130ms

132ms

143ms

AAAA

192ms

TXT

630ms

CAA

133ms

HTTPS

193ms

TLSA

122ms

SOA

45ms

MTA-STS

215ms

DNSSEC

233ms

SRV

198ms

Total

1461ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 23:13:32	1182ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-24 15:43:49	10029ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-13 19:21:27	9897ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:19:48	2956ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:40:21	2914ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:11:57	1518ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 16:02:00	4796ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 10:24:25	6017ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 10:21:28	10108ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 23:46:59	3043ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:00:56	1622ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:01:46	3437ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 14:57:04	1487ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:56:22	27225ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 02:23:53	3038ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 21:11:10 shown	1461ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 18:29:37	2315ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:50:30	2843ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:26:08	10072ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 15:48:49	8649ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 15:21:02	10168ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:16:29	10032ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 10:34:22	909ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 08:48:59	2444ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 23:28:27	791ms	2 NS 0 A 0 MX	❓ Unknown