SSL-Tools

SSL check results of rot26.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rot26.de 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 Fri, 15 Aug 2025 11:17:03 +0000

The mailservers of rot26.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rot26.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rot26.de
2a01:238:4350:b800:3ac:c2ef:4cc6:d0cd
 10
supported
rot26.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.rot26.de
85.214.107.12
 10
supported
rot26.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=rot26.de

Certificate chain
  • rot26.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • rot26.de
Alternative Names
  • *.rot26.de
  • rot26.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-07-22
Not valid after
2025-10-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
86:4A:F5:B9:0E:FE:6A:7A:ED:19:85:AD:A8:9C:50:E9:08:51:4B:6B:C7:1C:20:F3:7A:66:32:F7:B0:AB:48:FD
SHA1
E4:BE:C0:E4:CA:A3:32:D6:EC:F5:93:34:4F:65:1D:0A:D1:E2:7C:CC
X509v3 extensions
subjectKeyIdentifier
  • 20:3E:2D:0E:BF:F0:51:08:6D:5B:D6:0F:E9:DB:F1:A7:0F:53:7F:AB
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/20.crl
ct_precert_scts
  • 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 22 06:49:10.612 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F3:6D:74:94:84:F9:5E:6E:01:82:B4:
  • 80:B9:D5:ED:FE:7F:94:F0:89:34:11:F1:FF:8B:9A:53:
  • 4D:D1:09:8F:89:02:20:34:21:71:D6:5C:A7:EF:4D:DD:
  • A8:B0:94:22:01:34:22:62:88:FE:4D:A5:67:F5:73:D2:
  • A1:B0:48:DD:D8:0A:7C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Jul 22 06:49:10.619 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:99:86:7A:29:07:B9:4E:6C:9F:3B:43:
  • E9:6C:66:D2:B1:95:8A:96:F0:09:89:08:47:12:EC:6D:
  • 9C:01:A1:1C:94:02:21:00:B5:34:80:10:D9:9B:33:07:
  • 70:C2:4C:4B:B9:56:14:C3:BB:47:9C:E5:77:6B:C9:5D:
  • 70:21:DF:58:7D:5D:36:EF