luxuskat.dk

Historical scan 2026-07-26 20:00:46  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

luxuskat.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 10 July 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#

3 records   123ms

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-11-01 22:20:13
www CNAMEshops.myshopify.com (all on myshopify.com)
www vs bare domainSame network
WildcardYes: any name under the zone resolves
Denial of existenceNSEC zone can be walked (all names enumerable)
CDS / CDNSKEYPublished: 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#

195ms
CheckResult
Validation Status Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates) Not set
DS Record Found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-26 13:45:48
FieldValue
RegistrarSimply.com A/S
Registered2024-07-10
Expires2027-07-09 (233d)
📋 WHOIS#

Lookup Timing#

NS
123ms
A
101ms
MX
115ms
AAAA
108ms
TXT
427ms
CAA
102ms
HTTPS
97ms
TLSA
134ms
SOA
33ms
MTA-STS
194ms
DNSSEC
195ms
SRV
366ms
Total
1348ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-01 22:20:13 683ms 3 NS 1 A 1 MX Secure
2026-10-02 18:25:53 2094ms 3 NS 1 A 1 MX Secure
2026-08-27 15:47:33 1004ms 3 NS 1 A 1 MX Secure
2026-08-26 15:35:24 503ms 3 NS 1 A 1 MX Secure
2026-08-03 04:21:39 898ms 3 NS 1 A 1 MX Secure
2026-08-01 10:31:38 3270ms 3 NS 0 A 0 MX Bogus
2026-07-29 07:18:27 1458ms 3 NS 0 A 0 MX Bogus
2026-07-27 20:08:24 1407ms 3 NS 0 A 0 MX Bogus
2026-07-26 20:00:46 shown 1348ms 3 NS 0 A 0 MX Bogus
2026-07-25 19:29:37 10030ms 3 NS 0 A 0 MX Bogus
2026-07-24 19:15:08 10132ms 3 NS 0 A 0 MX Bogus
2026-07-23 18:25:41 6256ms 3 NS 0 A 0 MX Bogus
2026-07-22 09:28:57 1261ms 3 NS 0 A 0 MX Bogus
2026-07-21 06:55:54 3210ms 3 NS 0 A 0 MX Bogus
2026-07-19 13:52:17 1375ms 3 NS 0 A 0 MX Bogus
2026-07-18 03:42:24 1479ms 3 NS 0 A 0 MX Bogus
2026-07-13 23:18:28 1296ms 3 NS 0 A 0 MX Bogus
2026-07-12 08:20:00 1238ms 3 NS 0 A 0 MX Bogus
2026-06-17 14:41:59 1252ms 3 NS 1 A 1 MX Secure