aarhusexplorers.dk

📜 Historical scan 2026-07-05 19:29:02 · ← Latest scan

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

aarhusexplorers.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 6 May 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 49ms

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#

196ms

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 16:51:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-05-06
Expires	2027-05-31 (218d)

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

49ms

86ms

83ms

AAAA

70ms

TXT

223ms

CAA

78ms

HTTPS

84ms

TLSA

135ms

SOA

41ms

MTA-STS

106ms

DNSSEC

196ms

SRV

144ms

Total

1637ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 20:22:49	1301ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-12 06:26:19	38901ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 12:21:23	864ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:24:26	10162ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:11:10	17884ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:57:50	1428ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:25:47	2252ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:18:24	2709ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 18:14:07	2999ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:40:05	8993ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:01:18	5040ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:44:02	3013ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:37:58	3340ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 22:48:28	1461ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 22:25:18	890ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 08:26:33	1583ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 04:27:37	8765ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 14:19:21	10095ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 07:47:41	886ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:01:44	1624ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:40:48	8992ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 06:01:14	1133ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 04:36:16	8958ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 02:15:08	1219ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 12:19:15	963ms	2 NS 0 A 0 MX	❓ Unknown