SSL-Tools

SSL check results of spyra.rocks

NEW You can also bulk check multiple servers.

Discover if the mail servers for spyra.rocks can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Tue, 15 Apr 2025 18:44:34 +0000

The mailservers of spyra.rocks can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @spyra.rocks addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spyra.rocks
2a01:239:32e:c100::
 10
supported
spyra.rocks
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.spyra.rocks
212.227.143.87
 10
supported
spyra.rocks
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @spyra.rocks address so far. Test mail delivery

Certificates

First seen at:

CN=spyra.rocks

Certificate chain
  • spyra.rocks
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • spyra.rocks
Alternative Names
  • *.spyra.rocks
  • spyra.rocks
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-04-03
Not valid after
2025-07-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C6:3F:8E:2A:D7:FB:B0:F7:5F:6B:21:42:D6:E8:A4:2D:53:97:6D:1F:B6:7F:E7:EA:1D:77:C9:C0:4D:68:CC:10
SHA1
B1:81:E1:4C:CB:89:9C:93:E7:B2:EA:9F:50:1C:7C:5F:D3:E1:95:6D
X509v3 extensions
subjectKeyIdentifier
  • CD:2B:D0:D2:F6:D6:38:D4:2E:C8:43:47:23:D4:3F:E3:E2:EA:B9:F8
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/49.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Apr 3 18:41:17.807 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:42:94:F3:9B:15:81:9F:55:C2:56:21:DD:
  • 97:78:76:78:7E:54:3D:66:2A:D5:35:79:07:BC:94:60:
  • B6:49:3F:50:02:20:31:0A:74:CB:A2:E0:F3:8C:42:20:
  • DD:C6:6B:17:1B:85:67:B3:33:A5:B9:16:88:25:7C:29:
  • 3E:CF:0E:9C:1E:5E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Apr 3 18:41:17.876 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:46:CF:DB:8D:C9:1A:98:3D:A3:BB:BD:E1:
  • B9:4E:C0:E6:23:87:EA:B9:73:52:12:1F:27:65:D3:21:
  • 69:FB:3E:DD:02:20:15:92:98:C8:C6:06:06:E5:F3:D2:
  • 75:73:EC:D4:EC:98:B6:0F:E6:EC:DE:68:AD:AB:D8:E4:
  • E9:5C:B9:09:93:DB

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.spyra.rocks
  • DANE-EE: Domain Issued Certificate
  • Use full certificate
  • SHA-256 Hash
valid
valid