vestpolering.dk

Historical scan 2026-06-21 18:43:38  ·  ← Latest scan
Zone File Timeline & History Scan Now

vestpolering.dk is a .dk domain with no delegation in this scan. It was registered on 3 March 2014 (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 05:52:49
www CNAMEvestpolering.dk (all on vestpolering.dk)
www vs bare domainSame network
vestpolering.dk: 217.116.232.214 (AS47292)
www.vestpolering.dk: 217.116.232.214 (AS47292)
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

301ms
CheckResult
Validation StatusNot applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown).
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-31 00:08:17
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2014-03-03
Expires2027-03-31 (132d)

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
157ms
A
177ms
MX
171ms
AAAA
163ms
TXT
279ms
CAA
155ms
HTTPS
176ms
TLSA
17ms
SOA
197ms
MTA-STS
168ms
DNSSEC
301ms
SRV
214ms
Total
982ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 05:52:49 551ms 5 NS 1 A 3 MX Insecure
2026-11-05 17:55:07 891ms 5 NS 1 A 3 MX Insecure
2026-10-30 23:44:45 1037ms 5 NS 1 A 3 MX Insecure
2026-10-28 13:24:45 1372ms 5 NS 1 A 3 MX Insecure
2026-10-25 19:03:34 2015ms 5 NS 1 A 3 MX Insecure
2026-10-23 22:40:58 655ms 5 NS 1 A 3 MX Unknown
2026-10-22 05:44:37 882ms 5 NS 1 A 3 MX Insecure
2026-10-22 04:28:47 736ms 5 NS 1 A 3 MX Insecure
2026-10-15 08:49:58 834ms 5 NS 1 A 3 MX Insecure
2026-10-08 17:41:42 2664ms 5 NS 1 A 3 MX Insecure
2026-10-01 16:44:45 2443ms 5 NS 1 A 3 MX Insecure
2026-09-24 15:35:10 773ms 5 NS 1 A 3 MX Insecure
2026-09-23 15:01:37 1019ms 5 NS 1 A 3 MX Insecure
2026-09-15 01:42:21 739ms 5 NS 1 A 3 MX Insecure
2026-09-04 06:48:29 798ms 5 NS 1 A 3 MX Insecure
2026-08-27 16:03:58 2672ms 5 NS 1 A 3 MX Insecure
2026-08-20 15:42:59 3421ms 5 NS 1 A 3 MX Insecure
2026-08-14 05:44:35 1305ms 5 NS 1 A 3 MX Insecure
2026-08-07 20:09:55 1087ms 5 NS 1 A 3 MX Insecure
2026-07-30 20:03:43 8670ms 5 NS 1 A 3 MX Insecure
2026-07-23 19:47:47 8645ms 5 NS 1 A 3 MX Insecure
2026-07-16 16:55:48 1099ms 5 NS 1 A 3 MX Insecure
2026-07-09 17:40:57 2784ms 5 NS 1 A 3 MX Insecure
2026-07-03 15:23:31 1097ms 5 NS 1 A 3 MX Insecure
2026-06-27 21:06:47 1010ms 5 NS 1 A 3 MX Insecure