ikati.dk

📜 Historical scan 2026-07-22 00:07:54 · ← Latest scan

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

ikati.dk is a registered .dk domain whose nameservers (dns17.ovh.net, ns17.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 October 2010 (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 423ms

Nameserver	IP addresses	PTR	ASN / ISP
dns17.ovh.net	2001:41d0:d00:f600::2 5.135.112.105	dns17.ovh.net dns17.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns17.ovh.net	2001:41d0:b00:f000::2 5.39.116.57	ns17.ovh.net ns17.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

2054ms

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 03:30:48

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-10-13
Expires	2026-10-31 (12d)

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

423ms

444ms

459ms

AAAA

424ms

TXT

1953ms

CAA

459ms

HTTPS

424ms

TLSA

365ms

SOA

24ms

MTA-STS

710ms

DNSSEC

2054ms

SRV

546ms

Total

3873ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 23:28:58	5604ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:59:31	6315ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:56:25	7060ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:55:19	2852ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 17:42:14	3217ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 17:39:28	12203ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:58:02	7115ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 03:43:45	3891ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:23:14	3893ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 15:59:40	19268ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:27:54	3900ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:09:41	7075ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 16:22:14	16900ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 02:29:27	8265ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 05:08:24	15637ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:18:26	19553ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:07:18	3701ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:38:25	15231ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:19:23	3884ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:38:28	12376ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:14:35	3535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:07:54 shown	3873ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:51:16	3776ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 10:31:26	22745ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 08:59:51	6366ms	2 NS 0 A 0 MX	❓ Unknown