3l-ludvigsen.dk

Records from scan: 2026-10-23 12:09:18 · 65535ms total · last checked 2026-10-24 13:59 (unchanged)

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

3l-ludvigsen.dk is a registered .dk domain whose nameservers (ns1.dansketelecom.com, ns2.dansketelecom.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 June 1996 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 8021ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dansketelecom.com	15.197.172.60	a63452c77db78f54b.awsglobalaccelerator.com	AS16509 Amazon.com, Inc.
ns2.dansketelecom.com	15.197.172.60	a63452c77db78f54b.awsglobalaccelerator.com	AS16509 Amazon.com, Inc.

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

16065ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-24 19:54:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1996-06-03
Expires	2027-06-30 (248d)

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

8021ms

16036ms

9053ms

AAAA

16043ms

TXT

8082ms

CAA

8031ms

HTTPS

8031ms

TLSA

13ms

SOA

5896ms

MTA-STS

9058ms

DNSSEC

16065ms

SRV

16037ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-23 12:09:18 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-21 21:41:00	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 15:27:00	943ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 03:11:41	1097ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-24 23:57:22	3269ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-19 12:36:42	990ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:38:32	4838ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:21:35	5195ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:02:53	1089ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:10:20	1321ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:29:51	1292ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:32:09	1057ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:24:30	939ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:30:23	942ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 21:18:36	8939ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 22:32:15	3132ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 22:47:58	3165ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:57:52	1599ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:28:00	1108ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:05:52	1056ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:51:05	1009ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:50:56	1959ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 14:10:12	1167ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 01:43:34	1200ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 21:06:31	1097ms	2 NS 0 A 0 MX	❓ Unknown