katcraft.dk

Historical scan 2026-09-24 22:10:51  ·  ← Latest scan
Zone File Timeline & History Scan Now

katcraft.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 20 March 2026 (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   59ms

A Records#

2 records   56ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.94 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.53 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   230ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:e087:b9a5:2487:d1c2:7707 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:677c:3f:f83:217c:cdc 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-13 00:06:30

TLSA / DANE#

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

DNSSEC#

143ms
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-30 01:20:27
FieldValue
RegistrarRealtime Register B.V.
Registered2026-03-20
Expires2027-03-19 (122d)

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
59ms
A
56ms
MX
68ms
AAAA
230ms
TXT
621ms
CAA
63ms
HTTPS
55ms
TLSA
97ms
SOA
0ms
MTA-STS
91ms
DNSSEC
143ms
SRV
154ms
Total
1108ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-13 00:06:30 741ms 2 NS 2 A 0 MX Insecure
2026-11-06 00:31:53 903ms 2 NS 2 A 0 MX Insecure
2026-10-31 01:56:01 1008ms 2 NS 2 A 0 MX Insecure
2026-10-30 01:18:20 997ms 2 NS 2 A 0 MX Insecure
2026-10-24 06:04:30 711ms 2 NS 2 A 0 MX Insecure
2026-10-15 02:11:51 644ms 2 NS 2 A 0 MX Insecure
2026-10-09 12:57:45 879ms 2 NS 2 A 0 MX Insecure
2026-10-08 10:10:39 959ms 2 NS 2 A 0 MX Insecure
2026-10-02 01:32:41 1926ms 2 NS 2 A 0 MX Insecure
2026-10-01 01:26:35 1221ms 2 NS 2 A 0 MX Insecure
2026-09-26 02:17:22 900ms 2 NS 2 A 0 MX Insecure
2026-09-24 22:10:51 shown 1108ms 2 NS 2 A 0 MX Insecure
2026-09-21 06:08:27 10455ms 2 NS 2 A 0 MX Insecure
2026-09-17 20:46:13 925ms 2 NS 2 A 0 MX Insecure
2026-09-14 17:16:09 1291ms 2 NS 2 A 0 MX Insecure
2026-09-07 16:26:52 820ms 2 NS 2 A 0 MX Insecure
2026-09-02 03:26:10 1165ms 2 NS 2 A 0 MX Insecure
2026-08-27 02:10:39 749ms 2 NS 2 A 0 MX Insecure
2026-08-20 15:00:14 2583ms 2 NS 2 A 0 MX Insecure
2026-08-13 04:38:05 1236ms 2 NS 2 A 0 MX Insecure
2026-08-06 22:07:22 1351ms 2 NS 2 A 0 MX Insecure
2026-08-01 00:22:40 1044ms 2 NS 2 A 0 MX Insecure
2026-07-24 01:57:05 1053ms 2 NS 2 A 0 MX Insecure
2026-07-16 15:48:07 2540ms 2 NS 2 A 0 MX Insecure
2026-07-11 03:39:36 871ms 2 NS 2 A 0 MX Insecure