esimly.dk

📜 Historical scan 2026-07-21 18:28:22 · ← Latest scan

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

esimly.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 23 September 2025 (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#

3 records 378ms

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
ns3.simply.com	91.197.248.79	ns3.simply.com	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#

516ms

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-26 09:26:34

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2025-09-23
Expires	2026-09-22 (expired)

📋 WHOIS#

⏱️ Lookup Timing#

378ms

423ms

454ms

AAAA

414ms

TXT

735ms

CAA

444ms

HTTPS

434ms

TLSA

139ms

SOA

35ms

MTA-STS

80ms

DNSSEC

516ms

SRV

8445ms

Total

9549ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-24 22:57:39	347ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-23 11:45:41	344ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-20 06:44:36	188ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-19 05:40:28	237ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-18 04:02:05	300ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-17 03:09:20	214ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-16 00:36:11	97ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-15 00:04:23	352ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-13 22:56:46	332ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-12 20:55:42	103ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-11 20:31:52	212ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-10 19:32:08	126ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-09 18:19:43	221ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-08 14:45:00	268ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-07 14:29:46	659ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-06 19:17:18	107ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-05 18:14:10	254ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-04 18:07:26	255ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-03 18:01:37	90ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-02 18:00:57	263ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-01 17:57:44	89ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-30 17:52:35	794ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-19 02:03:18	1367ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 16:07:14	3814ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:23:33	6185ms	3 NS 0 A 0 MX	❓ Unknown