vordingborgspejderne.dk

📜 Historical scan 2026-09-30 19:37:32 · ← Latest scan

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

vordingborgspejderne.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 9 April 2008 (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 125ms

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#

212ms

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-13 05:37:12

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-04-09
Expires	2027-04-30 (184d)

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

125ms

142ms

189ms

AAAA

124ms

TXT

655ms

CAA

186ms

HTTPS

120ms

TLSA

113ms

SOA

28ms

MTA-STS

139ms

DNSSEC

212ms

SRV

193ms

Total

1439ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-27 18:10:59	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 19:37:32 shown	1439ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-19 15:36:07	41474ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:57:33	3149ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:56:15	1188ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:38:24	8757ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:28:46	6105ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:47:17	18657ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:32:48	16731ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:08:43	1583ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 12:05:48	1429ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:56:26	1548ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:30:16	3504ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:40:21	2926ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:50:03	2493ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:53:16	1338ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:32:48	1452ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 03:05:13	939ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:43:39	883ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:56:38	1435ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:13:41	839ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:50:59	10033ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:52:07	3930ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 09:03:24	1440ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 00:05:33	807ms	2 NS 0 A 0 MX	❓ Unknown