cadd.dk

📜 Historical scan 2026-07-13 18:19:13 · ← Latest scan

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

cadd.dk is a registered .dk domain whose nameservers (dns17.ovh.net, ns17.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 16 December 2010 (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 177ms

Nameserver	IP addresses	PTR	ASN / ISP
dns17.ovh.net	2001:41d0:d00:f600::2 5.135.112.105	dns17.ovh.net dns17.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns17.ovh.net	2001:41d0:b00:f000::2 5.39.116.57	ns17.ovh.net ns17.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

984ms

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-19 17:21:40

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-12-16
Expires	2026-12-31 (71d)

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

177ms

187ms

188ms

AAAA

188ms

TXT

878ms

CAA

199ms

HTTPS

187ms

TLSA

217ms

SOA

33ms

MTA-STS

143ms

DNSSEC

984ms

SRV

807ms

Total

2154ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 21:24:44	3298ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:39:36	5299ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:40:38	14836ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:26:56	9489ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:51:50	5735ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:42:09	3704ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 02:47:59	3888ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 01:36:39	5006ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 20:16:04	5926ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 13:12:05	3680ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 09:21:49	9617ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 08:01:10	5747ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:11:41	14798ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:50:02	11798ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 14:59:56	11739ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 11:53:24	11619ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 17:58:22	5768ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:06:38	8066ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:19:21	11484ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:38:26	4012ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:22:00	10361ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 15:49:18	4565ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:34:28	11494ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:53:01	7020ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 12:20:26	3950ms	2 NS 0 A 0 MX	❓ Unknown