zachart.dk

📜 Historical scan 2026-07-16 13:22:02 · ← Latest scan

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

zachart.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 May 2008 (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 56ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark 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#

161ms

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-22 05:23:34

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-05-02
Expires	2027-05-31 (221d)

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

56ms

91ms

80ms

AAAA

76ms

TXT

365ms

CAA

70ms

HTTPS

51ms

TLSA

62ms

SOA

22ms

MTA-STS

162ms

DNSSEC

161ms

SRV

314ms

Total

1040ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 10:09:59	1415ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 07:25:23	9765ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:24:33	1304ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:37:43	1658ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:26:12	6831ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:17:49	6060ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 18:08:24	1068ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 18:02:03	10467ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 05:27:21	3396ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 07:23:26	2886ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 11:29:25	3907ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:59:55	1436ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:18:01	2845ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 00:22:42	1533ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 22:02:32	9942ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 21:48:06	1253ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 02:31:57	9247ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 21:39:21	9128ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:21:04	1188ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:48:04	10059ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:21:03	1717ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:04:48	1172ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:46:18	963ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:35:36	1049ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 08:56:04	1060ms	2 NS 0 A 0 MX	❓ Unknown