weygaardtravel.dk

📜 Historical scan 2026-08-28 07:01:26 · ← Latest scan

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

weygaardtravel.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 12 March 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 98ms

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#

9158ms

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-12 03:17:48

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-03-12
Expires	2027-03-31 (156d)

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

98ms

103ms

131ms

AAAA

111ms

TXT

384ms

CAA

92ms

HTTPS

118ms

TLSA

88ms

SOA

35ms

MTA-STS

130ms

DNSSEC

9158ms

SRV

125ms

Total

10069ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 11:00:37	938ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 06:12:22	990ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 12:37:12	981ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-05 00:31:48	9833ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 07:01:26 shown	10069ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:25:32	1094ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:16:20	1133ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:55:56	6178ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:09:48	2093ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:44:14	6413ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 21:15:46	1203ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:34:32	2801ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:11:54	1107ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:28:54	8939ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:28:41	3077ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 17:38:28	5190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 20:19:37	2886ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 19:29:59	899ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 12:07:45	1349ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:15:17	9927ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:52:52	2698ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:41:57	2810ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:12:52	16679ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 15:11:58	17099ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:57:04	1250ms	2 NS 0 A 0 MX	❓ Unknown