stillezonen.dk

Historical scan 2026-06-20 22:02:00  ·  ← Latest scan
Zone File Timeline & History Scan Now

stillezonen.dk is a .dk domain with no delegation in this scan. It was registered on 9 November 2017 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. 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#

No NS records found

A Records#

No A records found

MX Records#

No MX records found

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-11 09:46:57

DKIM keys#

1 found
SelectorCNAMEKey
default — RSA · ~2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

TLSA / DANE#

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

DNSSEC#

325ms
CheckResult
Validation StatusNot applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown).
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-11 10:13:15
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2017-11-09
Expires2026-11-30 (12d)

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
219ms
A
235ms
MX
210ms
AAAA
232ms
TXT
328ms
CAA
241ms
HTTPS
254ms
TLSA
18ms
SOA
227ms
MTA-STS
269ms
DNSSEC
325ms
SRV
249ms
Total
1121ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-11 09:46:57 568ms 2 NS 1 A 1 MX Insecure
2026-11-01 00:09:46 2612ms 2 NS 1 A 1 MX Insecure
2026-09-30 22:29:49 835ms 2 NS 1 A 1 MX Insecure
2026-08-30 12:39:12 3360ms 2 NS 1 A 1 MX Insecure
2026-08-20 11:08:08 4906ms 2 NS 1 A 1 MX Insecure
2026-07-26 17:37:30 13588ms 2 NS 1 A 1 MX Insecure
2026-07-23 16:39:56 13611ms 2 NS 1 A 1 MX Insecure
2026-06-30 02:50:09 3943ms 2 NS 1 A 1 MX Insecure
2026-06-29 10:01:29 1570ms 2 NS 1 A 1 MX Insecure
2026-06-28 15:08:31 5818ms 2 NS 1 A 1 MX Insecure
2026-06-23 21:33:40 708ms 2 NS 1 A 1 MX Insecure
2026-06-23 02:19:53 5374ms 2 NS 1 A 1 MX Insecure
2026-06-22 14:51:10 1155ms 0 NS 0 A 0 MX Unknown
2026-06-21 17:13:08 2035ms 2 NS 1 A 1 MX Insecure
2026-06-20 22:02:00 shown 1121ms 0 NS 0 A 0 MX Unknown
2026-06-20 02:43:42 4530ms 2 NS 1 A 1 MX Insecure
2026-06-18 06:57:30 818ms 2 NS 1 A 1 MX Insecure