designninja.dk

Historical scan 2026-07-30 04:46:17  ·  ← Latest scan
Zone File Timeline & History Scan Now

designninja.dk is a .dk domain served by 5 nameservers (ns1.gigahost.dk, ns2.gigahost.dk, ns3.gigahost.dk and 2 more). It was registered on 18 September 2019 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Mail is handled by mx1.gigahost.dk, mx2.gigahost.dk and 1 more. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. 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#

5 records   43ms

A Records#

No A records found

MX Records#

3 records   184ms

AAAA Records (IPv6)#

No AAAA records — IPv6 not configured

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-19 23:57:04
www CNAMEdesignninja.dk (all on designninja.dk)
www vs bare domainSame network
WildcardYes: any name under the zone resolves

ACME Challenge#

TypeNameValue
CNAME _acme-challenge.designninja.dk designninja.dk

TLSA / DANE#

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

DNSSEC#

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

SOA#

0ms
FieldValue
Serial2026073001
Primary NS (MNAME)ns1.gigahost.dk
Responsible (RNAME)hostmaster@designninja.dk
Refresh10800s
Retry3600s
Expire604800s
Minimum (neg-cache TTL)3600s

Registration#

WHOIS fetched 2026-11-20 00:11:21
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2019-09-18
Expires2027-09-30 (313d)

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
43ms
A
4030ms
MX
184ms
AAAA
4028ms
TXT
6672ms
CAA
4029ms
HTTPS
4029ms
TLSA
373ms
SOA
0ms
MTA-STS
4040ms
DNSSEC
9088ms
SRV
4033ms
Total
12387ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 23:57:04 853ms 5 NS 2 A 3 MX Insecure
2026-11-12 23:47:59 1633ms 5 NS 2 A 3 MX Insecure
2026-11-05 14:33:48 1628ms 5 NS 2 A 3 MX Insecure
2026-10-29 05:56:28 804ms 5 NS 2 A 3 MX Insecure
2026-10-24 03:28:32 681ms 5 NS 2 A 3 MX Insecure
2026-10-15 21:21:40 1021ms 5 NS 2 A 3 MX Insecure
2026-10-08 10:09:52 1164ms 5 NS 2 A 3 MX Insecure
2026-10-01 04:59:19 876ms 5 NS 2 A 3 MX Insecure
2026-09-24 12:39:18 1125ms 5 NS 2 A 3 MX Insecure
2026-09-17 14:50:19 1021ms 5 NS 2 A 3 MX Insecure
2026-09-10 13:35:55 1475ms 5 NS 2 A 3 MX Insecure
2026-09-06 04:27:06 1199ms 5 NS 2 A 3 MX Insecure
2026-09-01 00:55:12 1637ms 5 NS 2 A 3 MX Insecure
2026-08-27 13:14:47 768ms 5 NS 2 A 3 MX Insecure
2026-08-20 17:27:07 9543ms 5 NS 2 A 3 MX Insecure
2026-08-14 03:44:06 2018ms 5 NS 2 A 3 MX Insecure
2026-08-06 19:31:24 1426ms 5 NS 2 A 3 MX Insecure
2026-07-30 04:46:17 shown 12387ms 5 NS 0 A 3 MX Insecure
2026-07-23 15:44:59 1056ms 5 NS 2 A 3 MX Unknown
2026-07-16 20:47:49 4114ms 5 NS 2 A 3 MX Insecure
2026-07-09 06:11:42 9267ms 5 NS 2 A 3 MX Unknown
2026-07-03 13:49:48 819ms 5 NS 2 A 3 MX Insecure
2026-06-30 04:32:29 874ms 5 NS 2 A 3 MX Insecure
2026-06-26 04:19:34 880ms 5 NS 2 A 3 MX Insecure
2026-06-18 20:29:13 2583ms 5 NS 2 A 3 MX Insecure