dengyldneshaker.dk

Historical scan 2026-08-27 16:38:26  ·  ← Latest scan
Zone File Timeline & History Scan Now

dengyldneshaker.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 12 November 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   58ms

A Records#

2 records   50ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.141 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.104 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   60ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:b50e:d46:ff73:4e9a:4a75 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:c9e1:8b16:6e51:ed17:cc6f 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-05 10:45:13

TLSA / DANE#

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

DNSSEC#

126ms
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 22:59:14
FieldValue
RegistrarRealtime Register B.V.
Registered2025-11-12
Expires2026-11-11 (expired)

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
58ms
A
50ms
MX
57ms
AAAA
60ms
TXT
323ms
CAA
48ms
HTTPS
55ms
TLSA
90ms
SOA
0ms
MTA-STS
215ms
DNSSEC
126ms
SRV
284ms
Total
801ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-16 23:43:21 147ms 1 NS 0 A 0 MX Unknown
2026-11-15 23:38:43 342ms 1 NS 0 A 0 MX Unknown
2026-11-14 23:26:22 703ms 1 NS 0 A 0 MX Unknown
2026-11-13 22:45:11 149ms 1 NS 0 A 0 MX Unknown
2026-11-12 22:31:14 1920ms 1 NS 0 A 0 MX Unknown
2026-11-05 10:45:13 2007ms 2 NS 2 A 0 MX Insecure
2026-10-29 10:52:02 2100ms 2 NS 2 A 0 MX Insecure
2026-10-25 17:24:10 760ms 2 NS 2 A 0 MX Insecure
2026-10-24 14:57:07 1291ms 2 NS 2 A 0 MX Insecure
2026-10-22 03:14:15 729ms 2 NS 2 A 0 MX Insecure
2026-10-15 12:58:29 1388ms 2 NS 2 A 0 MX Insecure
2026-10-08 17:08:42 819ms 2 NS 2 A 0 MX Insecure
2026-10-01 12:23:01 1968ms 2 NS 2 A 0 MX Insecure
2026-09-30 12:19:12 961ms 2 NS 2 A 0 MX Insecure
2026-09-24 05:20:09 2686ms 2 NS 2 A 0 MX Insecure
2026-09-20 05:47:08 839ms 2 NS 2 A 0 MX Insecure
2026-09-13 11:48:27 1112ms 2 NS 2 A 0 MX Insecure
2026-09-07 05:23:44 955ms 2 NS 2 A 0 MX Insecure
2026-08-27 16:38:26 shown 801ms 2 NS 2 A 0 MX Insecure
2026-08-20 23:54:43 1734ms 2 NS 2 A 0 MX Insecure
2026-08-14 00:23:25 1145ms 2 NS 2 A 0 MX Insecure
2026-08-06 07:44:33 979ms 2 NS 2 A 0 MX Insecure
2026-07-30 23:41:31 8882ms 2 NS 2 A 0 MX Insecure
2026-07-23 09:46:21 968ms 2 NS 2 A 0 MX Insecure
2026-07-16 14:57:13 1067ms 2 NS 2 A 0 MX Insecure