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 Sun, 17 Aug 2025 17:15:31 +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
      • R11
        • 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)
  • R11
validity period
Not valid before
2025-07-29
Not valid after
2025-10-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AE:8D:8E:A8:22:4B:4A:9C:20:C5:9D:13:7C:C9:38:07:FC:D2:4F:4F:8D:FF:84:FB:13:63:1D:CC:C8:A6:DF:EA
SHA1
26:3A:40:F8:49:39:B1:B7:BA:58:38:7C:77:54:E3:95:D9:CA:24:50
X509v3 extensions
subjectKeyIdentifier
  • CF:D6:0D:26:88:53:EB:DE:17:15:5E:AE:2C:14:D0:40:C4:7D:23:38
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/25.crl
ct_precert_scts
  • 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 : Jul 29 11:25:59.776 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:75:7E:FD:35:AC:2E:AA:12:3E:B7:38:D3:
  • 3E:A2:03:9E:35:CD:74:91:B5:06:5E:98:A1:FE:14:5F:
  • CB:AB:DF:DD:02:21:00:9D:C1:63:44:E7:19:F8:8D:CE:
  • C5:00:38:81:91:02:A9:B6:51:BC:81:72:55:33:CA:73:
  • 30:98:71:51:6C:AE:26
  • 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 : Jul 29 11:26:01.722 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:39:EE:CB:BB:42:17:CB:14:47:00:4E:91:
  • BB:0B:DB:21:F9:4C:85:F2:14:22:F8:E6:16:CE:83:9F:
  • 2D:03:58:31:02:21:00:AE:83:90:86:C6:C6:25:6C:E9:
  • 13:3F:CC:B8:CC:10:87:B5:8C:61:FD:25:EE:50:8E:F4:
  • FE:C0:79:4E:3D:3E:BC