lexar.dk

📜 Historical scan 2026-08-14 04:50:05 · ← Latest scan

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

lexar.dk is a registered .dk domain whose nameservers (ns1.icp100.net, ns2.icp100.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 23 October 2018 (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 409ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.icp100.net	173.248.225.85 46.165.246.211	173-248-225-085.static.imsbiz.com —	AS132585 SkyExchange Internet Access AS28753 Leaseweb Deutschland GmbH
ns2.icp100.net	173.248.225.179 173.248.225.85	173-248-225-179.static.imsbiz.com 173-248-225-085.static.imsbiz.com	AS132585 SkyExchange Internet Access AS132585 SkyExchange Internet Access

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

447ms

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-17 11:32:36

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-10-23
Expires	2027-10-31 (374d)

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

409ms

240ms

405ms

AAAA

435ms

TXT

21219ms

CAA

426ms

HTTPS

404ms

TLSA

875ms

SOA

58ms

MTA-STS

9551ms

DNSSEC

447ms

SRV

9237ms

Total

27425ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-04 06:28:50	41753ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-27 13:38:17	53168ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 19:17:24	39753ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:12:44	27305ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:07:25	40175ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:57:56	30192ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:32:47	52683ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:59:59	29969ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:40:02	44565ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:37:16	41607ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:15:06	40814ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 04:50:05 shown	27425ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:40:17	59144ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 06:45:23	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 17:09:18	37871ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 08:00:34	43033ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 17:38:31	49539ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:35:49	47270ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:09:39	43476ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:30:03	24239ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 15:47:54	41253ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:09:00	51343ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:59:54	38465ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:42:03	59384ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 21:05:32	38345ms	2 NS 0 A 0 MX	❓ Unknown