SSL check results of redo2oo.ch

NEW You can also bulk check multiple servers.

Discover if the mail servers for redo2oo.ch 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 Wed, 24 Feb 2021 14:25:58 +0000

The mailservers of redo2oo.ch can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @redo2oo.ch addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.redo2oo.ch
178.63.103.72
10
supported
mail.redcor.ch
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.redcor.ch

Certificate chain
  • mail.redcor.ch
    • 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)
  • mail.redcor.ch
Alternative Names
  • imap.redcor.ch
  • mail.redcor.ch
  • pop.redcor.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2020-12-30
Not valid after
2021-03-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A5:85:D5:65:AA:34:0F:2E:9A:26:9C:F2:60:13:9A:38:F0:E3:C8:9C:D2:B9:85:20:64:27:80:33:14:BB:0A:47
SHA1
A5:90:DC:C9:9F:EC:22:DF:87:51:37:DB:FB:46:89:73:16:56:E5:D8
X509v3 extensions
subjectKeyIdentifier
  • E7:77:6B:2F:21:0B:4E:88:64:AD:1E:21:75:C4:DF:C3:72:D8:12:26
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 : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Dec 30 21:38:32.999 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A8:56:B3:81:68:85:F8:8C:AC:6C:B5:
  • 73:03:28:9D:6B:94:35:75:61:FD:B5:8D:94:56:01:50:
  • D3:76:34:BB:50:02:20:49:C7:1E:D8:FB:E7:7D:DF:95:
  • 02:B7:C7:CF:52:A4:0B:37:32:70:CD:8E:7C:DC:35:08:
  • 81:01:AC:3C:D0:3C:A7
  • 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 : Dec 30 21:38:33.346 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:82:C8:E4:4A:C7:3B:01:60:AB:B7:B7:
  • E9:32:D6:B5:A2:72:D9:D3:76:A0:0F:E2:D7:4A:B7:AE:
  • 98:43:B6:AF:B1:02:20:54:C0:CE:8C:1B:1D:0A:38:E2:
  • 56:3E:E9:BA:08:7B:D3:CE:D4:4A:52:38:A0:5D:69:76:
  • 46:3C:BF:60:48:F1:12