vordingborgrejser.dk

📜 Historical scan 2026-07-31 04:46:34 · ← Latest scan

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

vordingborgrejser.dk is a registered .dk domain whose nameservers (ns.scannet2.dk, ns2.scannet2.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 April 2001 (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 93ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.scannet2.dk	185.25.141.9 2a02:2339:4006:10d::4171:4171	ns1.scannet.dk ns1.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.scannet2.dk	2a02:2339:1:112:0:5:1:b11 91.197.248.72	ns2.scannet.dk ns2.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark 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#

324ms

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-14 06:26:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-04-02
Expires	2027-06-30 (246d)

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

93ms

82ms

81ms

AAAA

93ms

TXT

681ms

CAA

86ms

HTTPS

90ms

TLSA

265ms

SOA

25ms

MTA-STS

119ms

DNSSEC

324ms

SRV

363ms

Total

6614ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-26 19:45:43	1068ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 18:08:09	2919ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:13:54	5345ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:06:39	1653ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:51:01	6883ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 09:46:43	4815ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 09:44:26	1241ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:52:41	1180ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 03:48:53	2502ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:47:19	2708ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:48:05	4126ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:32:45	4269ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 06:18:03	10416ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:39:48	2496ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 10:24:25	1453ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 04:46:34 shown	6614ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 04:13:13	2951ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:00:57	893ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:42:15	1326ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:18:04	8785ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:57:35	879ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:17:31	1320ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:46:34	10048ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:45:31	909ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 01:13:13	1194ms	2 NS 0 A 0 MX	❓ Unknown