zanderdev.dk

📜 Historical scan 2026-08-14 20:47:50 · ← Latest scan

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

zanderdev.dk is a registered .dk domain whose nameservers (byte.dns-parking.com, pixel.dns-parking.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 April 2026 (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 66ms

Nameserver	IP addresses	PTR	ASN / ISP
byte.dns-parking.com	172.64.53.67 2606:4700:5a::ac40:3543	byte.dns-parking.com byte.dns-parking.com	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
pixel.dns-parking.com	172.64.52.230 2606:4700:52::ac40:34e6	pixel.dns-parking.com pixel.dns-parking.com	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.

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

170ms

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-21 14:22:53

Field	Value
Registrar	Realtime Register B.V.
Registered	2026-04-08
Expires	2027-04-07 (167d)

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

66ms

117ms

66ms

AAAA

102ms

TXT

360ms

CAA

57ms

HTTPS

53ms

TLSA

99ms

SOA

34ms

MTA-STS

259ms

DNSSEC

170ms

SRV

285ms

Total

1050ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 07:00:10	3820ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-24 13:09:53	11316ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 01:24:50	10425ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:10:57	2797ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:40:27	6324ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:34:31	2313ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:18:01	1976ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:53:06	1710ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 23:46:14	2653ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:47:50 shown	1050ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:36:46	5784ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:51:56	1337ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 04:16:20	1839ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:16:56	3281ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 03:25:56	10601ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 16:08:39	3344ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 06:55:34	11137ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 05:38:47	1442ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:06:03	2036ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:46:36	1413ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:25:45	1821ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:25:08	3228ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 01:08:48	10370ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:01:41	1762ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 05:49:48	1755ms	2 NS 0 A 0 MX	❓ Unknown