vanløb.dk xn--vanlb-yua.dk

Historical scan 2026-06-19 03:11:20  ·  ← Latest scan
Zone File Timeline & History Scan Now

vanløb.dk is a .dk domain with no delegation in this scan. It was registered on 1 September 2010 (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#

No NS records found

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

Web & zone#

latest probe, not this scan · checked 2026-11-12 13:05:53
www CNAMExn--vanlb-yua.dk (all on xn--vanlb-yua.dk)
www vs bare domainSame network
vanløb.dk: 46.183.138.100 (AS47292)
www.vanløb.dk: 46.183.138.100 (AS47292)
WildcardYes: any name under the zone resolves

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

212ms
CheckResult
Validation StatusNot applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Secure).
AD Flag (resolver validates) Set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: ncache nxdomain

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-25 03:51:07
FieldValue
RegistrarGIGAHOST ApS
Registered2010-09-01
Expires2027-09-30 (315d)

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#

NS
73ms
A
116ms
MX
92ms
AAAA
137ms
TXT
152ms
CAA
114ms
HTTPS
63ms
TLSA
22ms
SOA
101ms
MTA-STS
105ms
DNSSEC
212ms
SRV
137ms
Total
432ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 13:05:53 590ms 5 NS 1 A 3 MX Insecure
2026-11-06 01:12:08 965ms 5 NS 1 A 3 MX Insecure
2026-11-02 20:58:00 830ms 5 NS 1 A 3 MX Insecure
2026-10-29 12:55:11 1604ms 5 NS 1 A 3 MX Insecure
2026-10-25 03:33:24 605ms 5 NS 1 A 3 MX Insecure
2026-10-15 11:34:48 798ms 5 NS 1 A 3 MX Insecure
2026-10-08 21:24:05 2231ms 5 NS 1 A 3 MX Insecure
2026-10-01 21:02:15 1818ms 5 NS 1 A 3 MX Unknown
2026-09-24 19:35:11 805ms 5 NS 1 A 3 MX Insecure
2026-09-18 08:46:12 960ms 5 NS 1 A 3 MX Insecure
2026-09-08 11:34:03 957ms 5 NS 1 A 3 MX Insecure
2026-08-27 21:50:33 796ms 5 NS 1 A 3 MX Insecure
2026-08-20 10:26:52 6650ms 5 NS 1 A 3 MX Unknown
2026-08-13 15:21:30 1217ms 5 NS 1 A 3 MX Insecure
2026-08-08 08:34:09 987ms 5 NS 1 A 3 MX Insecure
2026-07-23 08:38:19 1113ms 5 NS 1 A 3 MX Insecure
2026-07-17 09:45:21 8721ms 5 NS 1 A 3 MX Insecure
2026-07-11 06:45:58 2286ms 5 NS 1 A 3 MX Unknown
2026-07-03 13:03:20 999ms 5 NS 1 A 3 MX Insecure
2026-06-28 16:50:03 1035ms 5 NS 1 A 3 MX Insecure
2026-06-27 16:50:14 1050ms 5 NS 1 A 3 MX Insecure
2026-06-21 00:47:57 2927ms 5 NS 1 A 3 MX Secure
2026-06-20 17:03:05 303ms 0 NS 0 A 0 MX Secure
2026-06-20 03:31:28 294ms 0 NS 0 A 0 MX Secure
2026-06-19 03:11:20 shown 432ms 0 NS 0 A 0 MX Secure