joy-manicure-pedicure.dk

Historical scan 2026-08-28 02:58:02  ·  ← Latest scan
Zone File Timeline & History Scan Now

joy-manicure-pedicure.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 2 February 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   66ms

A Records#

2 records   42ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.156 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.48 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   52ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:bedc:2ec5:66bf:eb4d:3c5e 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:d1bf:1dad:377a:97d6:516e 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 06:41:04

TLSA / DANE#

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

DNSSEC#

129ms
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-12 06:53:15
FieldValue
RegistrarRealtime Register B.V.
Registered2025-02-02
Expires2027-02-01 (74d)

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
66ms
A
42ms
MX
57ms
AAAA
52ms
TXT
298ms
CAA
52ms
HTTPS
56ms
TLSA
91ms
SOA
0ms
MTA-STS
89ms
DNSSEC
129ms
SRV
249ms
Total
770ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 06:41:04 688ms 2 NS 2 A 0 MX Insecure
2026-11-05 21:08:50 1524ms 2 NS 2 A 0 MX Insecure
2026-11-02 18:28:38 874ms 2 NS 2 A 0 MX Insecure
2026-10-30 08:26:58 759ms 2 NS 2 A 0 MX Insecure
2026-10-22 13:35:24 1180ms 2 NS 2 A 0 MX Insecure
2026-10-15 23:23:05 1383ms 2 NS 2 A 0 MX Insecure
2026-10-08 11:08:46 1309ms 2 NS 2 A 0 MX Insecure
2026-10-01 03:58:00 1032ms 2 NS 2 A 0 MX Insecure
2026-09-25 02:24:20 900ms 2 NS 2 A 0 MX Insecure
2026-09-17 09:05:44 1451ms 2 NS 2 A 0 MX Insecure
2026-09-12 05:50:24 1412ms 2 NS 2 A 0 MX Insecure
2026-09-03 23:31:17 1081ms 2 NS 2 A 0 MX Insecure
2026-09-03 23:28:17 987ms 2 NS 2 A 0 MX Insecure
2026-08-28 02:58:02 shown 770ms 2 NS 2 A 0 MX Insecure
2026-08-23 21:24:20 2603ms 2 NS 2 A 0 MX Insecure
2026-08-20 20:28:48 1245ms 2 NS 2 A 0 MX Insecure
2026-08-14 04:24:07 3177ms 2 NS 2 A 0 MX Insecure
2026-08-08 02:10:44 1182ms 2 NS 2 A 0 MX Insecure
2026-08-01 01:42:34 860ms 2 NS 1 A 0 MX Insecure
2026-07-23 19:38:52 850ms 2 NS 1 A 0 MX Insecure
2026-07-22 18:24:47 9557ms 2 NS 1 A 0 MX Insecure
2026-07-17 04:01:33 820ms 2 NS 1 A 0 MX Insecure
2026-07-10 05:49:53 9646ms 2 NS 1 A 0 MX Insecure
2026-07-03 15:25:52 2537ms 2 NS 1 A 0 MX Insecure
2026-06-25 15:46:55 688ms 2 NS 1 A 0 MX Insecure