wizardry.dk

📜 Historical scan 2026-08-24 03:49:42 · ← Latest scan

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

wizardry.dk is a registered .dk domain whose nameservers (ns1.cliche.dk, ns2.cliche.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 1 November 2001 (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 14493ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.cliche.dk	195.249.40.140	—	AS3292 TDC Holding A/S
ns2.cliche.dk	195.249.40.141	—	AS3292 TDC Holding 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#

16170ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-23 13:54:23

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-11-01
Expires	2026-12-31 (68d)

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

14493ms

16101ms

16062ms

AAAA

16066ms

TXT

16217ms

CAA

8110ms

HTTPS

9074ms

TLSA

16051ms

SOA

16118ms

MTA-STS

8152ms

DNSSEC

16170ms

SRV

16131ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-10 20:59:32	61462ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 04:00:45	60057ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 03:49:42 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:59:21	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:27:38	63590ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:17:10	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:07:03	63236ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:59:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 19:31:59	57299ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:12:27	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 11:52:28	59313ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:45:45	55268ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:58:17	59749ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:48:15	58841ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:06:42	63343ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 21:18:17	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 11:01:28	63381ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 20:39:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:35:12	61277ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:40:56	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:00:20	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:49:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:15:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:48:22	57261ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 19:13:59	65535ms	2 NS 0 A 0 MX	❓ Unknown