SSL-Tools

SSL check results of mail.liboplus.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.liboplus.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 Wed, 13 Jan 2021 09:15:23 +0000

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

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

/mailservers/mail.liboplus.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.liboplus.de
185.185.24.40
 -
supported
uf-hosting.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mail.liboplus.de
2a01:4f8:bc:a7c::e985:e012
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=uf-hosting.de

Certificate chain
  • uf-hosting.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • uf-hosting.de
Alternative Names
  • uf-hosting.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-03
Not valid after
2021-04-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
ED:51:75:77:85:2D:40:78:90:4F:0C:95:68:72:E9:D0:90:C4:EA:DC:DF:CE:25:FC:A5:F2:B2:D3:F8:F3:25:8F
SHA1
B8:6F:F0:3F:3A:F1:40:D9:34:DD:A0:9B:0D:CC:82:1E:11:5A:B6:6F
X509v3 extensions
subjectKeyIdentifier
  • ED:E8:C0:5C:25:30:C6:B4:C5:18:5E:85:3D:7B:99:8A:95:24:A1:2D
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Jan 3 13:37:29.566 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:ED:AD:AE:07:FF:CE:2F:07:C6:46:DA:
  • 97:E3:AE:92:89:66:C7:E7:55:3F:0D:5A:FE:AC:3E:AD:
  • 34:32:26:40:0F:02:20:69:2E:A5:BD:95:85:4F:B7:08:
  • 03:09:25:DA:2D:18:4E:87:82:56:6D:00:4C:5C:C2:9B:
  • A4:54:DB:9B:F0:97:13
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Jan 3 13:37:29.567 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0C:65:00:CF:F0:BE:13:55:54:D2:43:6B:
  • B2:B8:B2:1F:1F:84:A5:C8:A3:38:7A:64:CD:59:87:24:
  • 79:F0:73:35:02:20:05:D7:5D:14:EA:13:DD:1F:3E:52:
  • 75:F5:75:E5:8B:36:5F:E8:31:40:EE:E3:99:B5:C1:A7:
  • 53:50:B1:31:2C:CD