ellingardcollection.dk

📜 Historical scan 2026-08-17 09:36:55 · ← Latest scan

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

ellingardcollection.dk is a registered .dk domain whose nameservers (dns1.sircon.net, dns2.sircon.net, dns3.sircon.net) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 691ms

Nameserver	IP addresses	PTR	ASN / ISP
dns1.sircon.net	178.164.11.72	dns1.sircon.net	AS34087 Nte Telekom As
dns2.sircon.net	178.164.11.35	dns2.sircon.net	AS34087 Nte Telekom As
dns3.sircon.net	2001:1af8:4700:a128:d::1 81.171.19.108	— dns3.sircon.net	AS60781 LeaseWeb Netherlands B.V. AS60781 LeaseWeb Netherlands B.V.

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

618ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

691ms

587ms

586ms

AAAA

579ms

TXT

2620ms

CAA

587ms

HTTPS

574ms

TLSA

499ms

SOA

576ms

MTA-STS

592ms

DNSSEC

618ms

SRV

575ms

Total

5190ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 19:52:53	4944ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 09:48:23	5774ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 02:57:19	8714ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:30:18	8773ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:19:07	9522ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:15:43	10836ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 19:45:45	11457ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 19:42:08	11369ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:36:55 shown	5190ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 05:31:04	6928ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:12:01	6119ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 23:03:43	6920ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:36:14	5342ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 02:12:23	8600ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 05:02:35	12361ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 15:27:13	2358ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-30 19:13:10	4819ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 01:21:25	5437ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:52:07	5151ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:08:20	1854ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:47:46	1611ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:28:47	12269ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:47:23	1975ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 18:10:20	12832ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:57:35	4694ms	3 NS 0 A 0 MX	❓ Unknown