170474.dk

📜 Historical scan 2026-07-09 03:54:40 · ← Latest scan

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

170474.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 1 July 2011 (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 62ms

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#

123ms

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

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-07-01
Expires	2027-07-31 (281d)

📋 WHOIS#

⏱️ Lookup Timing#

62ms

48ms

56ms

AAAA

52ms

TXT

294ms

CAA

37ms

HTTPS

48ms

TLSA

90ms

SOA

53ms

MTA-STS

76ms

DNSSEC

123ms

SRV

110ms

Total

1092ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 06:06:42	1348ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 00:43:59	1350ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 23:13:46	2054ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 20:09:59	3520ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 14:05:01	5382ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:48:45	1189ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:28:52	3867ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:19:43	2022ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 18:00:42	1531ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 01:40:24	854ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 00:44:03	4274ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 09:19:11	3534ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:05:22	27202ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 14:48:40	10202ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 11:20:30	1567ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 10:46:45	1432ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:34:08	8677ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:19:46	2838ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:03:08	5823ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:36:04	10244ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:46:15	736ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 05:22:54	734ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:08:44	682ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:20:05	894ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 20:05:57	744ms	2 NS 0 A 0 MX	❓ Unknown