comunicat.dk

📜 Historical scan 2026-08-11 15:10:41 · ← Latest scan

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

comunicat.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 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 148ms

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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-09 09:35:52

www	185.20.205.64 (AS48854) (address records, no CNAME)
www vs bare domain	Same network comunicat.dk: 185.20.205.64 (AS48854) www.comunicat.dk: 185.20.205.64 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

9147ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ 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#

148ms

142ms

AAAA

132ms

TXT

594ms

CAA

139ms

HTTPS

155ms

TLSA

80ms

SOA

129ms

MTA-STS

153ms

DNSSEC

9147ms

SRV

207ms

Total

10190ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 09:35:52	1471ms	3 NS 1 A 1 MX	🔒 Secure
2026-10-03 02:22:44	460ms	3 NS 1 A 1 MX	🔒 Secure
2026-10-01 02:14:11	491ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-16 23:10:01	2926ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-15 18:23:27	9252ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 10:22:10	1553ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 07:06:03	1412ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 15:10:41 shown	10190ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 10:01:00	1564ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 08:26:13	1417ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 03:48:15	10176ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-06 21:41:03	1481ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-31 11:59:45	10352ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 08:01:03	2102ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 06:51:00	1411ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 06:23:10	1320ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 05:41:24	1358ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 05:07:37	9698ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 04:12:29	1518ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-06-29 16:01:11	635ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-27 08:19:39	592ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-21 15:30:07	2336ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-16 23:27:20	65535ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-16 22:25:50	1489ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-16 22:09:44	410ms	3 NS 1 A 1 MX	🔒 Secure