1960-cadillac.dk

📜 Historical scan 2026-07-27 09:01:15 · ← Latest scan

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

1960-cadillac.dk is a registered .dk domain whose nameservers (ns1.jetcom.dk, ns2.jetcom.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 January 2006 (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 146ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.jetcom.dk	193.242.107.7	ns1.jetcom.dk	AS31027 GlobalConnect A/S
ns2.jetcom.dk	193.242.107.8	ns2.jetcom.dk	AS31027 GlobalConnect 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-20 02:17:27

www

SERVFAIL

🔗 TLSA / DANE#

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

🔐 DNSSEC#

285ms

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#

WHOIS fetched 2026-10-26 00:58:03

Field	Value
Registrar	ONE.COM A/S
Registered	2006-01-07
Expires	2027-01-31 (96d)

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

146ms

128ms

107ms

AAAA

164ms

TXT

499ms

CAA

120ms

HTTPS

145ms

TLSA

116ms

SOA

64ms

MTA-STS

187ms

DNSSEC

285ms

SRV

208ms

Total

3724ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 17:51:11	1431ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-21 03:48:31	26481ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-20 02:17:27	5888ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 21:58:58	1132ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 17:28:05	10059ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 07:20:55	1410ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 20:30:57	3135ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:38:44	4164ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:25:51	3939ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:19:21	2507ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 16:55:24	6469ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 16:54:08	40704ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 04:38:17	1328ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 18:25:00	8907ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:59:57	1596ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 10:31:01	10295ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 09:47:43	19209ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:31:16	1595ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:20:23	25917ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 13:09:32	17378ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:01:15 shown	3724ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 08:37:23	1279ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:05:54	3885ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:58:51	11744ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:00:03	1227ms	2 NS 0 A 0 MX	❓ Unknown