parlux.dk

📜 Historical scan 2026-07-26 02:10:49 · ← Latest scan

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

parlux.dk is a registered .dk domain whose nameservers (ns1.register.it, ns2.register.it) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 25 September 2009 (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 515ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.register.it	2a01:8100:2911::2:184:2 81.88.61.2	— host-81-88-61-2.dedicatedservers.it	AS39729 Register S.p.A. AS39729 Register S.p.A.
ns2.register.it	195.7.227.1 2a00:13b0:2::227:1	ns2.register.it —	AS8622 Team Blue Internet Services Uk Limited AS8622 Team Blue Internet Services Uk Limited

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

9563ms

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-23 03:54:35

Field	Value
Registrar	Marcaria.com LLC
Registered	2009-09-25
Expires	2027-09-30 (339d)

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

515ms

583ms

562ms

AAAA

511ms

TXT

2592ms

CAA

517ms

HTTPS

515ms

TLSA

532ms

SOA

23ms

MTA-STS

528ms

DNSSEC

9563ms

SRV

533ms

Total

12269ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-26 02:51:12	26267ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 22:24:50	5139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 20:01:11	5010ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 09:27:43	12682ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 05:29:02	12247ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 15:38:23	6188ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:08:39	10197ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:53:35	2729ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 11:18:09	10162ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 09:46:30	4856ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 09:41:14	2001ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 12:17:53	4596ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 09:53:54	4821ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:11:08	12484ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:50:43	11268ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:49:53	6978ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 15:38:05	5129ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 12:21:55	12234ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 10:31:20	5102ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 08:24:20	4890ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:34:03	4761ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:10:49	4859ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:10:49 shown	12269ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:41:49	10053ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:15:44	12329ms	2 NS 0 A 0 MX	❓ Unknown