SSL-Tools

SSL check results of mail.rlsb.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.rlsb.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 Tue, 11 Jun 2024 16:47:57 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rlsb.de
142.132.131.223
 -
supported
mail1.rlsb.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mail.rlsb.de
2a01:4f8:272:2812::3
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail1.rlsb.de

Certificate chain
  • mail1.rlsb.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail1.rlsb.de
Alternative Names
  • autoconfig.rlsb.de
  • autodiscover.rlsb.de
  • mail.rlsb.de
  • mail1.rlsb.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-14
Not valid after
2024-07-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7F:FE:3F:32:AD:8D:34:B4:B2:A2:B5:A7:79:86:EE:5E:71:F9:43:75:A3:07:8D:2F:41:19:CB:1F:8D:45:87:F1
SHA1
EB:30:81:52:51:5C:AF:39:72:22:7D:7B:CB:1F:65:3E:EC:EA:59:75
X509v3 extensions
subjectKeyIdentifier
  • 52:EA:60:10:7F:D1:29:58:6E:2F:B1:B2:13:7A:65:EE:FE:F1:78:4D
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 14 21:00:10.630 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AF:03:9A:DD:5A:F1:12:42:54:EF:50:
  • 33:BA:37:B6:70:B3:AE:F7:5B:5E:F6:26:11:A5:47:69:
  • F8:CF:40:83:45:02:21:00:DF:F4:45:8C:2A:F6:80:42:
  • 20:7C:8D:7B:BE:12:3C:44:98:C9:A7:AD:D3:77:4E:92:
  • C6:13:83:11:77:4D:91:A7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Apr 14 21:00:10.662 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9A:72:8D:82:CE:4E:4D:35:67:6A:FC:
  • BF:6C:7D:18:11:B6:7E:B4:74:E6:46:B3:FE:5B:E4:3E:
  • F5:0F:30:A3:03:02:20:14:90:FD:FE:1A:EB:4A:DA:77:
  • EA:50:8B:66:25:AA:7F:8E:09:76:2A:61:4B:28:1F:EC:
  • 0E:0F:AE:44:46:BF:CA