ezypoly.dk

📜 Historical scan 2026-08-21 13:43:22 · ← Latest scan

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

ezypoly.dk is a registered .dk domain whose nameservers (ns1.crazydomains.com, ns2.crazydomains.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 25 February 2022 (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 1183ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.crazydomains.com	162.159.24.7 2400:cb00:2049:1::a29f:1807	— e.ns.zerigo.net	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.crazydomains.com	162.159.25.129 2400:cb00:2049:1::a29f:1981	— ns3.linode.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#

1461ms

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-25 18:14:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2022-02-25
Expires	2027-02-24 (121d)

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

1183ms

1328ms

1641ms

AAAA

1339ms

TXT

5817ms

CAA

1368ms

HTTPS

1365ms

TLSA

987ms

SOA

335ms

MTA-STS

1621ms

DNSSEC

1461ms

SRV

1802ms

Total

13372ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 00:44:59	12656ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-18 20:06:22	10216ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 16:32:27	11017ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 14:08:54	13859ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:43:22 shown	13372ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:35:30	10354ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:53:42	8409ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:47:45	13378ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:09:31	11846ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 13:21:07	8226ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:01:34	8651ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:55:46	9118ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:42:49	9091ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 14:25:39	13043ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 03:08:09	3947ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:08:57	12237ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:35:21	3859ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:15:17	7924ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:45:37	15985ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:18:59	19713ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:39:35	8417ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 14:32:22	6547ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:08:08	7866ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:51:51	7204ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 21:29:52	7109ms	2 NS 0 A 0 MX	❓ Unknown