wlykke.dk

📜 Historical scan 2026-08-08 08:34:14 · ← Latest scan

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

wlykke.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 November 2010 (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 199ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

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

246ms

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-26 14:54:51

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-11-02
Expires	2026-11-30 (34d)

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

199ms

162ms

196ms

AAAA

168ms

TXT

879ms

CAA

162ms

HTTPS

152ms

TLSA

137ms

SOA

35ms

MTA-STS

218ms

DNSSEC

246ms

SRV

332ms

Total

1738ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 06:00:58	1887ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-29 16:51:47	1190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 06:37:07	1281ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 00:59:58	3454ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:35:44	8708ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:34:02	1319ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:25:51	1291ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:04:00	5167ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:31:29	6151ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:16:57	2379ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 13:40:09	3288ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:07:48	8906ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:58:35	10145ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 16:07:41	14080ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:34:16	27264ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 08:34:14 shown	1738ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 14:51:45	25113ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 00:49:51	43351ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:23:42	1358ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:13:00	10086ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:44:38	755ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:03:52	1375ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:07:12	2858ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 08:45:18	8831ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:56:07	1499ms	2 NS 0 A 0 MX	❓ Unknown