voresberlin.dk

📜 Historical scan 2026-08-20 12:20:51 · ← Latest scan

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

voresberlin.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 6 January 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 154ms

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#

225ms

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-18 10:39:38

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-01-06
Expires	2027-01-31 (96d)

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

154ms

186ms

183ms

AAAA

144ms

TXT

619ms

CAA

147ms

HTTPS

181ms

TLSA

118ms

SOA

41ms

MTA-STS

163ms

DNSSEC

225ms

SRV

189ms

Total

2449ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-03 13:28:38	10124ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 04:26:24	2834ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:49:49	2915ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:51:47	3748ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:41:42	2976ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:20:51 shown	2449ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:43:41	10379ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:07:16	4008ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:25:51	2514ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 10:39:05	2838ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:28:29	1036ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:36:41	3534ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:07:39	2551ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 14:33:11	2425ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 18:21:57	1443ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 18:14:15	10054ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 11:09:13	10124ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 07:03:50	10019ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:23:04	818ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:41:47	823ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:25:19	2392ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 04:47:39	14296ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 02:05:49	706ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:39:28	1398ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 14:44:05	10043ms	2 NS 0 A 0 MX	❓ Unknown