SSL-Tools

SSL check results of roeder.cx

NEW You can also bulk check multiple servers.

Discover if the mail servers for roeder.cx 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 Sat, 25 Oct 2025 17:47:28 +0000

The mailservers of roeder.cx can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @roeder.cx addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp2.roeder.cx
2a02:a00:e004:41::3
 50
supported
smtp2.roeder.cx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
smtp2.roeder.cx
188.246.21.43
 50
supported
smtp2.roeder.cx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @roeder.cx sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.roeder.cx (IPv6:2a02:a00:e004:41::2)
TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256
mail.roeder.cx (82.161.139.79)
TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256

Certificates

First seen at:

CN=smtp2.roeder.cx

Certificate chain
  • smtp2.roeder.cx
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • smtp2.roeder.cx
Alternative Names
  • mail.roeder.cx
  • smtp2.roeder.cx
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2025-09-28
Not valid after
2025-12-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
17:89:FC:FF:30:29:34:36:25:C9:26:56:FE:C5:DC:8C:FA:55:2A:90:83:B8:64:E8:44:F7:0D:DA:B0:B2:58:42
SHA1
7A:F1:8A:16:CB:3C:17:92:8B:80:1E:E6:CE:2F:B0:D9:52:77:BE:86
X509v3 extensions
subjectKeyIdentifier
  • B3:2E:CA:00:CB:82:A0:E6:5D:DA:DD:1B:6A:3D:58:6F:D4:8D:DA:FE
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/7.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Sep 28 13:11:48.115 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6A:3D:DD:91:FA:AD:70:2E:51:CC:CD:6F:
  • 11:8A:62:72:35:FF:ED:FA:3E:74:D0:57:F3:4D:AD:AA:
  • 55:BA:FF:3D:02:20:47:21:0A:82:8C:06:60:5C:82:F7:
  • E4:0C:9A:13:68:1A:F2:B0:CD:75:54:DA:67:C9:84:95:
  • 3E:4F:AA:7B:6D:42
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Sep 28 13:11:48.212 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C5:6E:F9:B0:1D:84:81:E3:2C:8F:98:
  • E4:34:18:08:04:CC:6C:DB:01:EC:1D:87:74:29:FA:8C:
  • 93:23:C5:F2:D8:02:20:35:32:9B:53:09:2F:C9:0D:C6:
  • 29:46:CC:F4:3E:EE:AD:A0:E7:03:BB:41:EC:62:49:A3:
  • 8E:C8:E5:0A:F3:39:6F