coldiron.dk

📜 Historical scan 2026-08-24 09:30:53 · ← Latest scan

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

coldiron.dk is a registered .dk domain whose nameservers (ns1.nameservices.us, ns2.nameservices.us) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 March 2004 (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#

2 records 16053ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.nameservices.us	—	—	—
ns2.nameservices.us	—	—	—

🌍 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-02 14:13:19

www	Address record (no CNAME)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

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

🔐 DNSSEC#

16074ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-16 13:38:40

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-03-08
Expires	2027-03-31 (154d)

🔗 Same registrant#

0 domains

Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).

No other domain with this registrant in our WHOIS data yet

📋 WHOIS#

⏱️ Lookup Timing#

16053ms

16032ms

16033ms

AAAA

16032ms

TXT

65535ms

CAA

16043ms

HTTPS

16055ms

TLSA

16028ms

SOA

16030ms

MTA-STS

16036ms

DNSSEC

16074ms

SRV

16050ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 11:25:14	824ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-05 14:19:00	989ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 14:13:19	2618ms	2 NS 1 A 1 MX	🔓 Insecure
2026-10-01 14:12:11	2583ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-30 14:04:30	2748ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-28 18:28:47	3164ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-27 18:13:39	3296ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-26 17:57:35	3243ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-25 17:55:51	3128ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-24 17:35:29	3188ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-23 17:13:01	3029ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-23 11:06:11	3329ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-20 12:38:53	5976ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-13 22:29:20	3370ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-11 07:09:35	3388ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-06 09:23:30	10065ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-03 16:28:02	3260ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-31 00:43:35	3210ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-28 15:55:24	3265ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-27 14:43:17	3128ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-26 13:54:17	3361ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-24 09:30:53 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:35:32	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:26:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:19:30	65535ms	2 NS 0 A 0 MX	❓ Unknown