luxureat.dk

📜 Historical scan 2026-06-23 20:20:23 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

luxureat.dk is a .dk domain with no delegation in this scan. It was registered on 2 June 2023 (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#

🖥️

No NS records found

🌍 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-23 09:04:56

www CNAME	luxureat.dk (all on luxureat.dk) → 82.112.243.150 2a02:4780:27:1892:0:3a7f:d0e3:2 (AS47583)
www vs bare domain	Same network luxureat.dk: 82.112.243.150 2a02:4780:27:1892:0:3a7f:d0e3:2 (AS47583) www.luxureat.dk: 82.112.243.150 2a02:4780:27:1892:0:3a7f:d0e3:2 (AS47583)
Wildcard	No

🔗 TLSA / DANE#

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

🔐 DNSSEC#

302ms

Check	Result
Validation Status	Not applicable: the domain has no delegation, so there is no zone to validate (stored verdict: ❓ Unknown).
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-23 09:35:53

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2023-06-02
Expires	2027-06-01 (219d)

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

191ms

195ms

203ms

AAAA

185ms

TXT

289ms

CAA

178ms

HTTPS

175ms

TLSA

17ms

SOA

203ms

MTA-STS

219ms

DNSSEC

302ms

SRV

213ms

Total

930ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-23 09:04:56	2003ms	2 NS 1 A 2 MX	🔓 Insecure
2026-10-16 00:01:58	1095ms	2 NS 1 A 2 MX	🔓 Insecure
2026-10-09 06:30:51	723ms	2 NS 1 A 2 MX	🔓 Insecure
2026-10-08 16:58:56	2175ms	2 NS 1 A 2 MX	🔓 Insecure
2026-10-01 14:04:01	1124ms	2 NS 1 A 2 MX	🔓 Insecure
2026-09-24 13:00:01	1665ms	2 NS 1 A 2 MX	🔓 Insecure
2026-09-18 00:10:15	1927ms	2 NS 1 A 2 MX	🔓 Insecure
2026-09-13 10:33:18	3730ms	2 NS 1 A 2 MX	🔓 Insecure
2026-09-04 01:09:00	1084ms	2 NS 1 A 2 MX	🔓 Insecure
2026-08-27 15:29:28	1158ms	2 NS 1 A 2 MX	🔓 Insecure
2026-08-27 10:42:41	2006ms	2 NS 1 A 2 MX	🔓 Insecure
2026-08-20 03:15:05	6109ms	2 NS 1 A 2 MX	🔓 Insecure
2026-08-14 01:48:28	4331ms	2 NS 1 A 2 MX	🔓 Insecure
2026-08-06 08:04:50	1343ms	2 NS 1 A 2 MX	🔓 Insecure
2026-07-23 11:12:45	972ms	2 NS 1 A 2 MX	🔓 Insecure
2026-07-16 08:16:44	1451ms	2 NS 1 A 2 MX	🔓 Insecure
2026-07-09 12:05:08	1016ms	2 NS 1 A 2 MX	🔓 Insecure
2026-07-03 17:50:33	2347ms	2 NS 1 A 2 MX	🔓 Insecure
2026-06-28 13:32:53	1223ms	2 NS 1 A 2 MX	🔓 Insecure
2026-06-26 22:40:23	11263ms	2 NS 1 A 2 MX	🔓 Insecure
2026-06-23 20:20:23 shown	930ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-18 07:30:30	1741ms	2 NS 1 A 2 MX	🔓 Insecure