3456.dk

📜 Historical scan 2026-08-03 07:04:13 · ← Latest scan

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

3456.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 5 March 2003 (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 159ms

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#

9185ms

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-22 17:49:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2003-03-05
Expires	2027-03-31 (159d)

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

159ms

136ms

234ms

AAAA

185ms

TXT

627ms

CAA

151ms

HTTPS

176ms

TLSA

116ms

SOA

27ms

MTA-STS

160ms

DNSSEC

9185ms

SRV

233ms

Total

10140ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-26 21:54:02	1433ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:22:05	3075ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:49:07	6381ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:36:01	4035ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:28:22	6781ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 15:03:11	6192ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 15:01:07	3878ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:29:57	27359ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 18:12:28	1028ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 09:40:21	4244ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 06:27:37	3030ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:20:13	2423ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 04:05:50	1509ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 07:04:13 shown	10140ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 03:37:19	33688ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 15:25:38	17298ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 02:06:07	2375ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:27:31	16675ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:28:15	8754ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:02:00	10049ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:41:44	10033ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 15:54:54	1393ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:31:09	49728ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:14:02	944ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 11:41:16	1543ms	2 NS 0 A 0 MX	❓ Unknown