liam-k.dk

📜 Historical scan 2026-08-01 08:06:03 · ← Latest scan

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

liam-k.dk is a registered .dk domain whose nameservers (ns01.servage.net, ns02.servage.net, ns03.servage.net and 2 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 16 May 2007 (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#

5 records 594ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.servage.net	—	—	—
ns02.servage.net	—	—	—
ns03.servage.net	—	—	—
ns04.servage.net	—	—	—
ns05.servage.net	—	—	—

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

641ms

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-12 13:44:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-05-16
Expires	2027-05-31 (223d)

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

594ms

600ms

679ms

AAAA

263ms

TXT

1938ms

CAA

264ms

HTTPS

262ms

TLSA

166ms

SOA

31ms

MTA-STS

97ms

DNSSEC

641ms

SRV

16047ms

Total

18669ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 07:10:56	2022ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:41:55	3442ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:37:09	1896ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:24:22	7696ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:18:44	8126ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-19 19:44:02	1914ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-18 19:39:08	5598ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:12:20	1697ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:32:45	3718ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:24:48	1516ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-13 14:00:09	57659ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:49:11	3384ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:40:52	3281ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-08 15:24:14	1908ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-01 08:06:03 shown	18669ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-28 20:19:12	1898ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:37:11	34322ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:08:51	2231ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:57:19	34440ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:15:11	1977ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:28:35	35115ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:53:21	34454ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-21 02:44:59	34612ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:08:52	34427ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-18 05:16:41	3958ms	5 NS 0 A 0 MX	❓ Unknown