cooperskbh.dk

📜 Historical scan 2026-08-23 00:55:25 · ← Latest scan

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

cooperskbh.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 27 February 2024 (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 74ms

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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-10 22:59:42

www CNAME	shops.myshopify.com (all on myshopify.com) → 23.227.38.74 2620:127:f00f:e:: (AS13335)
www vs bare domain	Same network cooperskbh.dk: 23.227.38.65 2620:127:f00f:5:: (AS13335) www.cooperskbh.dk: 23.227.38.74 2620:127:f00f:e:: (AS13335)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE#

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

🔐 DNSSEC#

2098ms

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-04 11:41:12

Field	Value
Registrar	Simply.com A/S
Registered	2024-02-27
Expires	2027-02-26 (123d)

📋 WHOIS#

⏱️ Lookup Timing#

74ms

70ms

73ms

AAAA

79ms

TXT

318ms

CAA

70ms

HTTPS

85ms

TLSA

62ms

SOA

44ms

MTA-STS

79ms

DNSSEC

2098ms

SRV

128ms

Total

2930ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-04 11:38:22	640ms	3 NS 1 A 1 MX	🔓 Insecure
2026-09-11 16:31:43	798ms	3 NS 1 A 1 MX	🔓 Insecure
2026-08-28 08:03:47	726ms	3 NS 1 A 1 MX	🔓 Insecure
2026-08-27 08:00:52	9997ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:59:20	3872ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:55:25 shown	2930ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:43:07	1152ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:30:38	2196ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:16:43	12019ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:54:18	4069ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:56:11	3574ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 23:42:36	4134ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 23:41:36	897ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 16:01:40	907ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:28:43	4183ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 07:36:07	10010ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 16:23:33	2839ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:25:57	1279ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 10:52:32	1548ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:11:55	2806ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 09:25:33	1437ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 08:48:05	1549ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 02:39:25	1328ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 01:22:24	1570ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 20:28:21	1492ms	2 NS 0 A 0 MX	❓ Unknown