8560.dk

📜 Historical scan 2026-08-08 17:03:23 · ← Latest scan

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

8560.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 4 February 2009 (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 75ms

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#

202ms

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-16 16:27:32

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2009-02-04
Expires	2027-02-28 (127d)

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

75ms

63ms

59ms

AAAA

92ms

TXT

388ms

CAA

97ms

HTTPS

123ms

TLSA

33ms

SOA

50ms

MTA-STS

67ms

DNSSEC

202ms

SRV

141ms

Total

945ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-15 22:29:23	1305ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-13 00:15:13	1464ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 06:57:53	10056ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:26:15	3245ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:03:13	1770ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:54:26	4951ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:45:06	10883ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:20:24	1580ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:17:48	9969ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:01:42	9003ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:39:54	3953ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 03:02:43	3583ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 20:11:13	1016ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:49:58	4509ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 13:29:39	3463ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 17:03:23 shown	945ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 05:22:52	3087ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 05:03:28	2353ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 20:18:18	1082ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:55:59	1416ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:32:55	10129ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:57:59	1348ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:39:03	1116ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:43:27	891ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:35:12	27221ms	2 NS 0 A 0 MX	❓ Unknown