tc-cloud.dk

📜 Historical scan 2026-07-20 02:29:25 · ← Latest scan

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

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

🖥️ Nameservers#

2 records 73ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.dandomain.dk	185.25.141.3 2a02:2339:4006:109::dd	ns.dandomain.dk ns.dandomain.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.dandomain.dk	2a02:2339:1:108::dd:dd 91.197.248.66	ns2.dandomain.dk ns2.dandomain.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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-23 06:37:39

www	212.237.249.17 (AS48854) (address records, no CNAME)
www vs bare domain	Same network tc-cloud.dk: 212.237.249.17 (AS48854) www.tc-cloud.dk: 212.237.249.17 (AS48854)
Wildcard	Yes: any name under the zone resolves
CDS / CDNSKEY	None 0 CDS, 0 CDNSKEY

🔗 TLSA / DANE#

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

🔐 DNSSEC#

150ms

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#

73ms

101ms

85ms

AAAA

75ms

TXT

8395ms

CAA

85ms

HTTPS

73ms

TLSA

259ms

SOA

22ms

MTA-STS

290ms

DNSSEC

150ms

SRV

141ms

Total

9328ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-23 06:37:39	367ms	2 NS 1 A 0 MX	❓ Unknown
2026-10-22 03:41:50	858ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-20 11:53:52	1425ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-19 05:54:08	357ms	2 NS 1 A 0 MX	❓ Unknown
2026-10-18 05:18:52	1452ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-17 03:43:53	664ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-16 02:52:48	690ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-13 23:20:38	338ms	2 NS 1 A 0 MX	❓ Unknown
2026-10-12 23:06:48	1505ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-11 22:22:03	1526ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-10 20:54:07	755ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-09 19:44:42	337ms	2 NS 1 A 0 MX	❓ Unknown
2026-10-08 15:21:42	756ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-07 15:17:28	1267ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-06 13:40:10	2419ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-01 11:15:54	318ms	2 NS 1 A 0 MX	❓ Unknown
2026-09-30 11:12:27	1380ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-29 10:46:53	652ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-28 10:36:17	690ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-27 10:29:31	634ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-26 10:25:37	445ms	2 NS 1 A 0 MX	❓ Unknown
2026-09-25 16:43:52	681ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-24 16:30:32	664ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-23 15:34:14	718ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-18 16:08:51	648ms	2 NS 0 A 0 MX	⚠️ Bogus