SSL-Tools

SSL check results of rockshrub.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rockshrub.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, 23 Apr 2024 04:57:21 +0000

We can not guarantee a secure connection to the mailservers of rockshrub.de!

Please contact the operator of rockshrub.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/rockshrub.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rockshrub.de
2a03:4000:6:207d::1
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.rockshrub.de
5.45.110.117
 10
supported
henry.rockshrub.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=henry.rockshrub.de

Certificate chain
  • henry.rockshrub.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • henry.rockshrub.de
Alternative Names
  • henry.rockshrub.de
  • imap.rockshrub.de
  • mail.rockshrub.de
  • pop.rockshrub.de
  • relay.rockshrub.de
  • rockshrub.de
  • smtp.rockshrub.de
  • talk.rockshrub.de
  • www.rockshrub.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-22
Not valid after
2024-05-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AC:D1:2C:EB:D9:86:F4:09:9E:D2:44:31:87:D7:3D:AB:63:9D:4C:B0:18:5B:82:CC:C2:43:18:42:88:76:FB:49
SHA1
D6:6C:98:C5:A9:B4:E7:14:10:CF:E2:59:29:16:74:E8:53:22:66:63
X509v3 extensions
subjectKeyIdentifier
  • FB:E2:AA:BF:04:D8:97:B2:99:77:3E:11:EE:7F:05:31:50:7B:06:27
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Feb 22 13:33:52.008 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:19:A7:31:91:A2:0D:6B:E8:44:CC:E4:5C:
  • DF:C2:51:5D:81:F3:B2:08:99:68:91:4A:EC:75:95:9A:
  • DF:E8:52:DF:02:20:5E:51:B0:FB:92:4C:13:35:2B:19:
  • 8D:4C:C6:2A:03:B1:C9:4D:6B:69:47:21:B1:E7:94:2C:
  • 8F:1F:F5:3D:2E:3E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Feb 22 13:33:52.069 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A7:DE:6F:5A:7B:20:73:75:E5:1F:B1:
  • 2C:25:21:1D:FC:C5:66:C6:4C:6B:30:2B:8C:81:68:49:
  • 0E:99:FE:E0:2D:02:20:0A:49:5D:40:E4:11:55:A7:EC:
  • B5:8E:FC:3B:16:DD:78:0C:C4:ED:15:46:63:B3:A4:6C:
  • B0:B3:6B:CE:2E:9E:2D