naviate.dk

📜 Historical scan 2026-08-17 06:51:16 · ← Latest scan

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

naviate.dk is a registered .dk domain whose nameservers (ns1.iplace.se, ns2.iplace.se, ns3.iplace.se) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 March 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#

3 records 922ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.iplace.se	84.19.146.195	ns1.iplace.se	AS49419 Iver Sverige AB
ns2.iplace.se	193.44.15.8	ns2.iplace.se	AS3301 Telia Company AB
ns3.iplace.se	88.131.112.129	ns3.iplace.se	AS1257 Tele2 SWIPnet

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

942ms

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-13 05:43:13

Field	Value
Registrar	Abion AB
Registered	2012-03-09
Expires	2027-03-31 (163d)

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

922ms

825ms

897ms

AAAA

900ms

TXT

3539ms

CAA

871ms

HTTPS

876ms

TLSA

663ms

SOA

98ms

MTA-STS

925ms

DNSSEC

942ms

SRV

901ms

Total

6550ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 21:41:02	5004ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-30 10:22:45	4571ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-30 07:29:18	5178ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-25 18:45:27	4807ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-13 17:01:16	4756ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-02 14:52:17	4695ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 12:03:36	4953ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:45:11	2777ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:34:26	8000ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:21:50	60586ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:10:24	2776ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:42:23	5094ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:51:16 shown	6550ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 04:55:24	9891ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 00:48:59	8472ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 03:19:00	12185ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 22:59:07	4883ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:30:21	12739ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 19:33:07	6456ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 12:37:03	1674ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-04 17:57:17	5140ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:51:57	12129ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:44:55	6767ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:10:32	1685ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:48:37	1682ms	3 NS 0 A 0 MX	❓ Unknown