rejsentilmexico.dk

Historical scan 2026-09-24 12:25:14  ·  ← Latest scan
Zone File Timeline & History Scan Now

rejsentilmexico.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 28 July 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   47ms

A Records#

2 records   54ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.47 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.186 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   56ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:4522:7d48:172f:1ad8:bb4a 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:943c:2c34:8510:d555:3011 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 21:35:34

TLSA / DANE#

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

DNSSEC#

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

SOA#

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

Registration#

WHOIS fetched 2026-10-29 20:48:55
FieldValue
RegistrarRealtime Register B.V.
Registered2025-07-28
Expires2027-07-27 (251d)

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
47ms
A
54ms
MX
47ms
AAAA
56ms
TXT
324ms
CAA
47ms
HTTPS
57ms
TLSA
83ms
SOA
0ms
MTA-STS
249ms
DNSSEC
128ms
SRV
475ms
Total
933ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 21:35:34 1018ms 2 NS 2 A 0 MX Insecure
2026-11-05 17:59:25 1894ms 2 NS 2 A 0 MX Insecure
2026-10-29 20:23:20 643ms 2 NS 2 A 0 MX Insecure
2026-10-23 16:32:53 775ms 2 NS 2 A 0 MX Insecure
2026-10-21 17:58:34 1519ms 2 NS 2 A 0 MX Insecure
2026-10-15 08:49:49 1549ms 2 NS 2 A 0 MX Insecure
2026-10-08 16:35:02 3872ms 2 NS 2 A 0 MX Insecure
2026-10-01 15:22:43 887ms 2 NS 2 A 0 MX Insecure
2026-09-30 15:14:48 1195ms 2 NS 2 A 0 MX Insecure
2026-09-24 12:25:14 shown 933ms 2 NS 2 A 0 MX Insecure
2026-09-19 23:24:41 1191ms 2 NS 2 A 0 MX Insecure
2026-09-11 13:16:13 922ms 2 NS 2 A 0 MX Insecure
2026-09-05 22:31:34 1316ms 2 NS 2 A 0 MX Insecure
2026-08-27 19:36:26 762ms 2 NS 2 A 0 MX Insecure
2026-08-20 11:27:49 1213ms 2 NS 2 A 0 MX Insecure
2026-08-13 18:40:27 8647ms 2 NS 2 A 0 MX Insecure
2026-08-06 05:44:05 1167ms 2 NS 2 A 0 MX Insecure
2026-08-05 03:16:23 1786ms 2 NS 2 A 0 MX Insecure
2026-08-01 15:35:39 1235ms 2 NS 1 A 0 MX Insecure
2026-07-23 07:52:52 720ms 2 NS 1 A 0 MX Insecure
2026-07-16 22:29:19 832ms 2 NS 1 A 0 MX Insecure
2026-07-11 19:28:22 8681ms 2 NS 1 A 0 MX Insecure
2026-07-03 13:12:33 7589ms 2 NS 1 A 0 MX Insecure
2026-06-27 08:38:05 2407ms 2 NS 1 A 0 MX Insecure
2026-06-20 08:24:27 952ms 2 NS 1 A 0 MX Insecure