supersteam.dk

Historical scan 2026-11-06 17:40:38  ·  ← Latest scan
Zone File Timeline & History

supersteam.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 6 November 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is DNSSEC-signed and validates, 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#

2 records   35ms

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#

1 records   93ms
TXT Record
v=spf1 -all

SPF#

PolicyRecord (supersteam.dk)
-all (hard fail) v=spf1 -all

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-06 17:40:38
wwwNXDOMAIN
www vs bare domainNeither resolves
supersteam.dk: no address
www.supersteam.dk: no address
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

DNS lookups: 0/10 · policy: -all

No problems found

TLSA / DANE#

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

DNSSEC#

99ms
CheckResult
Validation Status Secure
AD Flag (resolver validates) Set
DS Record Found
DNSKEY Record Found
Flagsresolution failed: ncache nxrrset

SOA#

34ms
FieldValue
Serial2026110601
Primary NS (MNAME)ns01.one.com
Responsible (RNAME)hostmaster@one.com
Refresh14400s
Retry3600s
Expire1209600s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-11-09 18:26:43
FieldValue
RegistrarONE.COM A/S
Registered2025-11-06
Expires2026-11-05 (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
35ms
A
32ms
MX
26ms
AAAA
34ms
TXT
93ms
CAA
29ms
HTTPS
23ms
TLSA
20ms
SOA
34ms
MTA-STS
37ms
DNSSEC
99ms
SRV
37ms
Total
350ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-22 23:29:20 171ms 1 NS 0 A 0 MX Unknown
2026-11-21 23:29:11 303ms 1 NS 0 A 0 MX Unknown
2026-11-20 23:28:49 143ms 1 NS 0 A 0 MX Unknown
2026-11-19 23:28:35 160ms 1 NS 0 A 0 MX Unknown
2026-11-18 23:28:15 379ms 1 NS 0 A 0 MX Unknown
2026-11-17 12:52:36 94ms 1 NS 0 A 0 MX Unknown
2026-11-16 11:48:59 153ms 1 NS 0 A 0 MX Unknown
2026-11-15 11:46:21 171ms 1 NS 0 A 0 MX Unknown
2026-11-14 11:45:33 162ms 1 NS 0 A 0 MX Unknown
2026-11-13 11:34:31 223ms 1 NS 0 A 0 MX Unknown
2026-11-12 11:24:46 187ms 1 NS 0 A 0 MX Unknown
2026-11-09 18:04:27 581ms 1 NS 0 A 0 MX Unknown
2026-11-06 17:40:38 shown 350ms 2 NS 0 A 0 MX Secure
2026-11-01 17:47:11 498ms 2 NS 1 A 4 MX Secure
2026-10-31 09:09:25 877ms 2 NS 1 A 4 MX Secure
2026-10-26 11:26:12 593ms 2 NS 1 A 4 MX Secure
2026-10-24 09:33:15 1722ms 2 NS 1 A 4 MX Secure
2026-09-27 18:55:41 674ms 2 NS 1 A 4 MX Secure
2026-09-23 05:12:53 748ms 2 NS 1 A 4 MX Secure
2026-09-04 03:29:38 894ms 2 NS 1 A 4 MX Secure
2026-08-27 18:14:30 780ms 2 NS 1 A 4 MX Secure
2026-08-27 00:50:30 696ms 2 NS 1 A 4 MX Secure
2026-08-23 02:07:11 8383ms 2 NS 1 A 4 MX Secure
2026-07-29 02:37:07 4931ms 2 NS 1 A 4 MX Secure
2026-07-22 16:27:19 1007ms 2 NS 1 A 4 MX Secure