voldagergaard.dk

Records from scan: 2026-10-25 06:39:43 · 1847ms total · last checked 2026-10-26 15:46 (unchanged)

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

voldagergaard.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 February 2013 (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 225ms

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#

292ms

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 21:31:15

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-02-02
Expires	2027-02-28 (124d)

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

225ms

227ms

209ms

AAAA

229ms

TXT

1018ms

CAA

207ms

HTTPS

209ms

TLSA

201ms

SOA

27ms

MTA-STS

217ms

DNSSEC

292ms

SRV

211ms

Total

1847ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-25 06:39:43 shown	1847ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-03 15:41:32	9928ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 06:30:34	1573ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 22:27:41	10148ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:44:37	2498ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:31:27	4523ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:24:58	1342ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:58:34	1890ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:49:42	5637ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:54:57	3032ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 21:17:08	10118ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:09:16	10128ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:19:05	2890ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 13:02:23	746ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:47:09	742ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:52:09	4222ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:56:44	972ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 02:30:47	1633ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 07:18:44	1464ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:57:11	2967ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:19:12	2861ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 13:50:25	16970ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:33:19	903ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:48:23	9077ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:33:48	8647ms	2 NS 0 A 0 MX	❓ Unknown