jskt.dk

Historical scan 2026-09-29 15:24:19  ·  ← Latest scan
Zone File Timeline & History Scan Now

jskt.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 29 August 2018 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 77.37.83.53 is hosted by Hostinger International Limited (AS47583) in The Netherlands. Mail is handled by mx1.onlinemail.io, mx2.onlinemail.io. 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   99ms

A Records#

2 records   113ms

MX Records#

2 records   71ms

AAAA Records (IPv6)#

2 records   71ms

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

1 records   434ms
TXT Record
v=spf1 a include:spf.curanet.dk ~all

SPF#

PolicyRecord (jskt.dk)
~all (soft fail) v=spf1 a include:spf.curanet.dk ~all

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 08:24:40

DNS lookups: 4/10 · policy: ~all

No problems found

TLSA / DANE#

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

DNSSEC#

206ms
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-11-05 04:00:07
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2018-08-29
Expires2027-08-31 (286d)

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
99ms
A
113ms
MX
71ms
AAAA
71ms
TXT
434ms
CAA
105ms
HTTPS
108ms
TLSA
1237ms
SOA
0ms
MTA-STS
183ms
DNSSEC
206ms
SRV
323ms
Total
3022ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 08:24:40 763ms 2 NS 2 A 2 MX Insecure
2026-11-05 03:43:00 1717ms 2 NS 2 A 2 MX Insecure
2026-10-29 06:51:50 816ms 2 NS 2 A 2 MX Insecure
2026-10-23 00:23:32 1849ms 2 NS 2 A 2 MX Insecure
2026-10-15 14:21:40 757ms 2 NS 2 A 2 MX Insecure
2026-10-08 18:12:39 991ms 2 NS 2 A 2 MX Insecure
2026-10-01 15:52:41 2427ms 2 NS 2 A 2 MX Insecure
2026-09-29 15:24:19 shown 3022ms 2 NS 2 A 2 MX Insecure
2026-09-24 21:48:43 932ms 2 NS 2 A 2 MX Insecure
2026-09-23 20:34:04 2893ms 2 NS 2 A 2 MX Insecure
2026-09-18 06:30:31 1191ms 2 NS 2 A 2 MX Insecure
2026-09-10 20:52:06 2996ms 2 NS 2 A 2 MX Insecure
2026-09-08 05:25:32 1487ms 2 NS 2 A 2 MX Insecure
2026-08-27 07:35:23 1547ms 2 NS 2 A 2 MX Insecure
2026-08-20 15:10:21 1227ms 2 NS 2 A 2 MX Insecure
2026-08-14 06:30:23 2797ms 2 NS 2 A 2 MX Insecure
2026-08-06 14:52:09 1547ms 2 NS 2 A 2 MX Insecure
2026-07-23 14:37:13 16957ms 2 NS 2 A 2 MX Insecure
2026-07-16 11:05:57 8926ms 2 NS 2 A 2 MX Insecure
2026-07-09 04:36:02 1177ms 2 NS 2 A 2 MX Insecure
2026-07-03 16:21:00 1850ms 2 NS 2 A 2 MX Insecure
2026-06-25 07:06:57 1810ms 2 NS 2 A 2 MX Insecure
2026-06-20 19:12:03 1347ms 2 NS 2 A 2 MX Insecure
2026-06-17 15:26:05 2903ms 2 NS 2 A 2 MX Insecure