8660haarby.dk

📜 Historical scan 2026-08-11 18:18:01 · ← Latest scan

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

8660haarby.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 7 November 2023 (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 169ms

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#

227ms

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-23 11:22:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2023-11-07
Expires	2026-11-06 (13d)

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

169ms

224ms

155ms

AAAA

206ms

TXT

597ms

CAA

165ms

HTTPS

142ms

TLSA

140ms

SOA

64ms

MTA-STS

221ms

DNSSEC

227ms

SRV

232ms

Total

1704ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 05:42:21	1380ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-19 22:21:48	1304ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 09:36:04	9997ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 11:42:47	1429ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 05:56:08	4536ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:50:41	5078ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:43:41	1409ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:34:49	1862ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 13:12:41	5843ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 13:11:38	1616ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:09:20	2921ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:04:23	2961ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:43:56	3756ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:18:01 shown	1704ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:24:21	1406ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 22:38:38	48690ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 09:40:43	2836ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-03 19:40:43	1878ms	2 NS 1 A 3 MX	🔓 Insecure
2026-07-02 00:42:44	1856ms	2 NS 1 A 3 MX	🔓 Insecure
2026-06-16 13:15:40	653ms	2 NS 1 A 3 MX	🔓 Insecure