SSL-Tools

SSL check results of stone-mail.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for stone-mail.org 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, 05 Nov 2024 11:04:05 +0000

The mailservers of stone-mail.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @stone-mail.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx0.stone-mail.org
2a01:4f8:262:51e7:9000::25
 10
supported
mx0.stone-mail.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mx0.stone-mail.org
136.243.252.130
 10
supported
mx0.stone-mail.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

We have not received any emails from a @stone-mail.org address so far. Test mail delivery

Certificates

First seen at:

CN=mx0.stone-mail.org

Certificate chain
  • mx0.stone-mail.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx0.stone-mail.org
Alternative Names
  • mx0.stone-mail.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-10-20
Not valid after
2025-01-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D4:F6:32:12:94:EB:4E:CC:16:04:14:32:90:66:1D:F2:EC:2A:FC:25:B4:FB:AF:0A:25:91:D3:4B:79:06:C3:50
SHA1
2C:3D:9A:E6:8F:B3:C2:7D:ED:E6:DB:A7:21:50:65:BE:E2:42:06:E5
X509v3 extensions
subjectKeyIdentifier
  • 45:16:39:A0:5D:A2:41:BF:E8:0A:2E:F2:5E:E8:89:B6:F5:0D:39:CC
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Oct 20 09:09:52.930 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B7:E7:D4:68:F3:3E:B3:53:ED:55:B9:
  • 03:77:38:46:4B:CC:DF:6D:F7:AC:0F:90:1A:69:F4:39:
  • 54:22:44:07:A9:02:21:00:E4:AF:D6:1C:4E:96:14:72:
  • 07:41:35:6D:3A:5B:25:89:79:A3:25:03:8B:3F:20:70:
  • 97:27:69:7E:7C:2C:54:AD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 20 09:09:52.997 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3C:49:5D:86:0F:D2:D3:DC:71:76:48:DD:
  • 21:D7:80:7E:01:27:09:5B:DA:C0:42:00:15:45:98:9A:
  • A9:D8:B9:F3:02:21:00:92:AD:AE:E8:6F:6E:63:D2:19:
  • F2:7D:6B:79:34:97:46:94:E7:36:71:08:F1:6C:4F:1F:
  • 0A:F5:E7:89:F6:B8:AD

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.mx0.stone-mail.org
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid