naniko.dk

📜 Historical scan 2026-07-18 15:44:04 · ← Latest scan

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

naniko.dk is a registered .dk domain whose nameservers (ns1.fozzy.com, ns2.fozzy.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 17 February 2015 (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 8403ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.fozzy.com	206.54.190.9 2607:fbe0:1:49::a	ns1.fozzy.com ns1.fozzy.com	AS40824 Webzilla Inc. AS40824 Webzilla Inc.
ns2.fozzy.com	2a00:1178:1:66:6::2 88.85.81.2	ns2.fozzy.com ns2.fozzy.com	AS35415 Webzilla B.V. AS35415 Webzilla B.V.

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

8400ms

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-12 12:46:34

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-02-17
Expires	2030-02-28 (1221d)

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

8403ms

8380ms

391ms

AAAA

16043ms

TXT

17162ms

CAA

375ms

HTTPS

8379ms

TLSA

1925ms

SOA

30ms

MTA-STS

332ms

DNSSEC

8400ms

SRV

910ms

Total

31766ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-04 03:22:39	10315ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-17 21:59:38	14712ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:37:26	6140ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:28:56	18060ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:21:22	12438ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:40:10	15664ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:06:51	10234ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:48:21	11007ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:25:26	14261ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 18:13:51	14104ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:46:05	12083ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:22:25	15282ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:46:27	10055ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 14:53:05	10064ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 08:36:19	13617ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 17:39:45	11871ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:07:09	25154ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:43:54	19241ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 13:56:44	51340ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:34:56	33349ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:29:48	8393ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:12:34	37322ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 05:36:14	8718ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 04:19:20	31650ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 15:44:04 shown	31766ms	2 NS 0 A 0 MX	❓ Unknown