escortx.dk

Historical scan 2026-08-27 20:09:42  ·  ← Latest scan
Zone File Timeline & History Scan Now

escortx.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 10 December 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, has no DMARC policy and is reachable over IPv6. 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   56ms

A Records#

2 records   60ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.159 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.255 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   58ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:602a:3760:8106:48d4:45dc 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:a7e9:640a:4bd8:ce85:5bf9 60s — AS47583 — — 🇨🇾 Cyprus —

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 01:51:24

TLSA / DANE#

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

DNSSEC#

127ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsunsigned answer

SOA#

0ms
FieldValue
Serial2026082701
Primary NS (MNAME)ns1.dns-parking.com
Responsible (RNAME)dns@hostinger.com
Refresh10000s
Retry2400s
Expire604800s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-11-01 10:43:05
FieldValue
RegistrarRealtime Register B.V.
Registered2025-12-10
Expires2026-12-09 (21d)

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
56ms
A
60ms
MX
51ms
AAAA
58ms
TXT
406ms
CAA
54ms
HTTPS
145ms
TLSA
421ms
SOA
0ms
MTA-STS
376ms
DNSSEC
127ms
SRV
239ms
Total
1152ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 01:51:24 723ms 2 NS 2 A 2 MX Insecure
2026-11-05 15:23:00 722ms 2 NS 2 A 0 MX Insecure
2026-11-01 10:26:03 847ms 2 NS 2 A 0 MX Insecure
2026-10-23 17:20:09 946ms 2 NS 2 A 0 MX Insecure
2026-10-15 10:38:33 1320ms 2 NS 2 A 0 MX Insecure
2026-10-08 04:10:27 1246ms 2 NS 2 A 0 MX Insecure
2026-10-01 22:59:10 875ms 2 NS 2 A 0 MX Insecure
2026-09-25 21:53:33 884ms 2 NS 2 A 0 MX Insecure
2026-09-24 02:07:40 925ms 2 NS 2 A 0 MX Insecure
2026-09-16 00:24:59 837ms 2 NS 2 A 0 MX Insecure
2026-09-08 22:43:24 1815ms 2 NS 2 A 0 MX Insecure
2026-08-28 10:02:41 2729ms 2 NS 2 A 0 MX Insecure
2026-08-27 20:09:42 shown 1152ms 2 NS 2 A 0 MX Insecure
2026-08-20 11:51:20 9725ms 2 NS 2 A 0 MX Insecure
2026-08-14 06:39:19 3047ms 2 NS 2 A 0 MX Insecure
2026-08-06 08:22:23 1034ms 2 NS 2 A 0 MX Insecure
2026-07-31 16:55:12 1201ms 2 NS 2 A 0 MX Insecure
2026-07-23 18:19:17 9688ms 2 NS 2 A 0 MX Insecure
2026-07-16 20:31:02 8481ms 2 NS 2 A 0 MX Insecure
2026-07-10 05:44:18 8701ms 2 NS 2 A 0 MX Insecure
2026-07-03 13:27:14 1025ms 2 NS 2 A 0 MX Insecure
2026-06-27 20:28:32 661ms 2 NS 2 A 0 MX Insecure
2026-06-22 23:16:25 1140ms 2 NS 2 A 0 MX Insecure
2026-06-17 08:29:29 505ms 2 NS 2 A 0 MX Insecure
2026-06-17 08:20:12 473ms 2 NS 2 A 0 MX Insecure