ssje.dk

Historical scan 2026-08-10 12:02:26  ·  ← Latest scan
Deactivated by the registry Zone File Timeline & History Scan Now

ssje.dk is a .dk domain the registry has taken out of service: it is delegated to the registry's own sentinel nameservers (nonexistent.punktum.dk), so it does not resolve. It was registered on 7 August 2023 (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#

1 records   8073ms
NameserverIP addressesPTRASN / ISP
nonexistent.punktum.dk — — —

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-16 22:21:20
www162.159.135.42 (AS13335) (address records, no CNAME)
www vs bare domainSame network
ssje.dk: 162.159.135.42 (AS13335)
www.ssje.dk: 162.159.135.42 (AS13335)
WildcardYes: any name under the zone resolves
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

8098ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
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-15 22:22:59
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2023-08-07
Expires2027-08-06 (261d)

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
8073ms
A
8057ms
MX
8071ms
AAAA
8070ms
TXT
8214ms
CAA
8070ms
HTTPS
111ms
TLSA
66ms
SOA
47ms
MTA-STS
157ms
DNSSEC
8098ms
SRV
8100ms
Total
8763ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-16 22:21:20 467ms 2 NS 1 A 4 MX Secure
2026-11-15 22:20:20 587ms 2 NS 1 A 4 MX Secure
2026-11-14 22:16:53 584ms 2 NS 1 A 4 MX Secure
2026-11-13 22:09:41 509ms 2 NS 1 A 4 MX Secure
2026-11-12 22:05:34 700ms 2 NS 1 A 4 MX Secure
2026-11-11 21:32:47 1507ms 2 NS 1 A 4 MX Secure
2026-11-10 03:08:44 442ms 2 NS 1 A 4 MX Secure
2026-11-09 02:08:54 771ms 2 NS 1 A 4 MX Secure
2026-11-08 01:44:52 603ms 2 NS 1 A 4 MX Secure
2026-11-07 01:34:41 635ms 2 NS 1 A 4 MX Secure
2026-11-06 01:16:34 421ms 2 NS 1 A 4 MX Secure
2026-11-05 01:14:33 670ms 2 NS 1 A 4 MX Secure
2026-11-04 01:05:23 666ms 2 NS 1 A 4 MX Secure
2026-11-03 00:32:55 447ms 2 NS 1 A 4 MX Secure
2026-11-01 13:02:55 693ms 2 NS 1 A 4 MX Secure
2026-10-30 12:55:09 505ms 2 NS 1 A 4 MX Secure
2026-10-28 10:02:52 1993ms 2 NS 1 A 4 MX Secure
2026-10-27 08:09:21 1405ms 2 NS 1 A 4 MX Secure
2026-10-26 02:46:09 502ms 2 NS 1 A 4 MX Secure
2026-10-25 02:34:20 551ms 2 NS 1 A 4 MX Secure
2026-10-23 16:41:58 426ms 2 NS 1 A 4 MX Secure
2026-10-22 05:26:20 751ms 2 NS 1 A 4 MX Secure
2026-10-21 03:57:08 692ms 2 NS 1 A 4 MX Secure
2026-10-19 15:32:20 844ms 2 NS 1 A 4 MX Secure
2026-10-18 14:36:26 781ms 2 NS 1 A 4 MX Secure