5214.dk

📜 Historical scan 2026-07-24 03:26:21 · ← Latest scan

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

5214.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 15 April 2012 (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 126ms

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#

9162ms

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-09 15:09:39

Field	Value
Registrar	DANDOMAIN A/S
Registered	2012-04-15
Expires	2027-04-30 (189d)

📋 WHOIS#

⏱️ Lookup Timing#

126ms

139ms

140ms

AAAA

138ms

TXT

681ms

CAA

137ms

HTTPS

171ms

TLSA

114ms

SOA

24ms

MTA-STS

133ms

DNSSEC

9162ms

SRV

170ms

Total

10029ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 19:09:37	1254ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-07 21:02:05	1291ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 18:29:48	1261ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-27 06:59:13	1360ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 17:14:02	2972ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:24:22	3744ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:02:13	4691ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:30:54	937ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:04:38	7789ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 10:23:39	6072ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 10:20:46	10278ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 15:28:09	10174ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 00:50:19	4444ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 12:26:59	1489ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 13:45:19	43101ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:31:38	2557ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 11:12:09	1482ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 11:51:24	35114ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:01:05	1009ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:54:22	1026ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:35:51	956ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:17:35	878ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:26:21 shown	10029ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:52:33	877ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:54:25	55726ms	2 NS 0 A 0 MX	❓ Unknown