cim-cloud.dk

Records from scan: 2026-08-24 01:40:40 · 17041ms total · last checked 2026-10-20 00:03 (unchanged)

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

cim-cloud.dk is a registered .dk domain whose nameservers (ns.scannet2.dk, ns2.scannet2.dk, ns3.scannet2.dk) 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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

3 records 107ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.scannet2.dk	185.25.141.9 2a02:2339:4006:10d::4171:4171	ns1.scannet.dk ns1.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.scannet2.dk	2a02:2339:1:112:0:5:1:b11 91.197.248.72	ns2.scannet.dk ns2.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.scannet2.dk	2a02:2339:1:112:0:5:1:b11 91.197.248.72	ns2.scannet.dk ns2.scannet.dk	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#

188ms

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#

107ms

130ms

118ms

AAAA

120ms

TXT

484ms

CAA

131ms

HTTPS

111ms

TLSA

74ms

SOA

35ms

MTA-STS

119ms

DNSSEC

188ms

SRV

16045ms

Total

17041ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-24 01:40:40 shown	17041ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 18:56:37	2343ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 18:55:33	7717ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 18:51:10	3208ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 17:53:56	2250ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 17:52:36	10443ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:15:17	1381ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 00:07:27	9243ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 14:39:42	1457ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 14:41:18	1223ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 05:02:12	1431ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 05:37:17	1204ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-28 05:39:46	2861ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 05:26:07	10015ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 05:03:49	1715ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 04:45:22	1205ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 04:05:44	2956ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 02:17:58	8936ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 07:36:33	1573ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-20 06:53:47	1148ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-19 04:28:56	10030ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-17 23:01:08	9013ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-16 15:57:39	1479ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-13 01:10:40	1207ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-12 00:18:34	1065ms	3 NS 0 A 0 MX	⚠️ Bogus