watchwindershop.dk

📜 Historical scan 2026-08-10 16:00:58 · ← Latest scan

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

watchwindershop.dk is a registered .dk domain whose nameservers (ns1.curanet.dk, ns2.curanet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 March 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 463ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.curanet.dk	185.25.141.12 2a02:2339:4006:108::123	ns1.curanet.dk ns1.curanet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.curanet.dk	2a02:2339:1:10f::123:123 91.197.248.75	ns2.curanet.dk ns2.curanet.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#

691ms

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 03:32:26

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-03-03
Expires	2029-03-31 (886d)

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

463ms

457ms

402ms

AAAA

458ms

TXT

1317ms

CAA

383ms

HTTPS

394ms

TLSA

181ms

SOA

197ms

MTA-STS

584ms

DNSSEC

691ms

SRV

542ms

Total

2936ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-26 14:28:14	9786ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 12:56:04	1058ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 12:13:34	2788ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:19:06	5710ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:07:37	1233ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:20:02	6654ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 08:03:32	1413ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:27:57	1448ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:17:38	3155ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 14:15:13	2389ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:12:03	1366ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 22:20:24	4014ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 16:00:58 shown	2936ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 02:49:26	1137ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 03:08:00	1059ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 02:30:41	9935ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:54:02	9155ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:03:28	25244ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:42:09	1452ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:16:04	9064ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 22:22:14	1490ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:02:51	2790ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:51:21	9255ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:36:20	1367ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 06:24:11	10010ms	2 NS 0 A 0 MX	❓ Unknown