swanlake.dk

Records from scan: 2026-08-23 13:45:09 · 3178ms total · last checked 2026-10-20 03:24 (unchanged)

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

swanlake.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 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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 222ms

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#

374ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-07 14:03:51

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-10-02
Expires	2026-10-31 (10d)

📋 WHOIS#

⏱️ Lookup Timing#

222ms

252ms

237ms

AAAA

270ms

TXT

1031ms

CAA

254ms

HTTPS

250ms

TLSA

191ms

SOA

85ms

MTA-STS

260ms

DNSSEC

374ms

SRV

282ms

Total

3178ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 13:45:09 shown	3178ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 12:39:26	1120ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 12:24:31	17002ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 11:57:31	7230ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 04:45:14	3146ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 04:04:16	3423ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 03:29:00	2710ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 15:19:50	1091ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 21:15:32	1142ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 16:18:58	8761ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-07 03:42:21	8806ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-01 02:06:50	2323ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-29 17:10:49	10098ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-28 02:58:53	913ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 02:27:27	2885ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 01:53:14	1081ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 01:22:58	27139ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:35:33	8705ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 23:50:30	823ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 20:48:44	1333ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-20 06:03:51	3037ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-19 01:43:38	890ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-18 01:00:44	1083ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-16 14:41:52	10018ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-14 15:59:16	1052ms	2 NS 0 A 0 MX	⚠️ Bogus