SSL check results of redlibrary.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for redlibrary.net 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

Report created Fri, 21 Nov 2025 01:31:21 +0000

The mailservers of redlibrary.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @redlibrary.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.redlibrary.net
2a00:da00:f451:3c00::1
10
supported
mail.redlibrary.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mail.redlibrary.net
217.154.57.113
10
supported
mail.redlibrary.net
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 @redlibrary.net address so far. Test mail delivery

Certificates

First seen at:

CN=mail.redlibrary.net

Certificate chain
  • mail.redlibrary.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E7
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.redlibrary.net
Alternative Names
  • mail.redlibrary.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E7
validity period
Not valid before
2025-10-17
Not valid after
2026-01-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
55:23:71:96:F2:5C:FB:31:7A:6A:15:3C:24:C3:5F:21:76:C9:E0:C7:5B:BA:DE:5D:05:EE:88:86:74:FA:61:9C
SHA1
BE:4B:EA:6A:DC:2C:24:66:95:BC:BC:DE:BA:96:DB:32:AE:71:1D:29
X509v3 extensions
subjectKeyIdentifier
  • 5A:74:79:A9:0E:10:B6:DD:44:62:E2:5C:E4:7D:90:06:2C:69:68:AB
authorityKeyIdentifier
  • keyid:AE:48:9E:DC:87:1D:44:A0:6F:DA:A2:E5:60:74:04:78:C2:9C:00:80
authorityInfoAccess
  • CA Issuers - URI:http://e7.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e7.c.lencr.org/56.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 96:97:64:BF:55:58:97:AD:F7:43:87:68:37:08:42:77:
  • E9:F0:3A:D5:F6:A4:F3:36:6E:46:A4:3F:0F:CA:A9:C6
  • Timestamp : Oct 17 01:37:09.889 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8C:F7:05:09:95:D4:35:2B:8F:6E:0C:
  • 23:26:E2:1C:FF:BD:FA:A1:52:9F:48:78:61:AE:6E:4F:
  • A2:6A:9C:A8:28:02:20:6B:D8:1C:03:F5:A2:DA:9E:7E:
  • C3:BA:04:0C:23:0D:02:FE:31:89:B8:78:37:C5:76:61:
  • C4:78:DB:D9:AD:BA:E5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 64:11:C4:6C:A4:12:EC:A7:89:1C:A2:02:2E:00:BC:AB:
  • 4F:28:07:D4:1E:35:27:AB:EA:FE:D5:03:C9:7D:CD:F0
  • Timestamp : Oct 17 01:37:11.835 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D0:FC:2E:28:00:3A:5A:4B:5A:17:23:
  • E5:BD:FF:1D:0C:DF:EA:5F:83:56:7D:61:49:68:98:1A:
  • ED:DB:DD:91:3C:02:20:4E:F9:A7:38:E0:A0:05:27:48:
  • 61:F4:8F:4B:C8:27:A2:7E:E5:2D:37:32:C1:56:FF:AA:
  • 4E:CB:E6:74:20:F9:63