SSL-Tools

SSL check results of bayern-cloud.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for bayern-cloud.org 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, 27 Apr 2022 01:55:41 +0000

The mailservers of bayern-cloud.org 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 @bayern-cloud.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mailedge.valcloud.de
159.69.228.227
 0
supported
mailedge.valcloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

We have not received any emails from a @bayern-cloud.org address so far. Test mail delivery

Certificates

First seen at:

CN=mailedge.valcloud.de

Certificate chain
  • mailedge.valcloud.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Expired
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailedge.valcloud.de
Alternative Names
  • mailedge.valcloud.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-01-15
Not valid after
2022-04-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9D:5C:3A:14:B4:5B:1A:CC:4F:84:BF:4A:BC:48:F1:33:B0:B1:59:CB:99:C5:F4:37:43:A2:71:56:1A:95:54:0D
SHA1
04:6D:F1:92:5E:93:0D:6A:40:6F:F2:AC:D9:60:4F:0B:2D:3E:2F:CA
X509v3 extensions
subjectKeyIdentifier
  • 58:F4:8A:5F:8F:8B:18:23:32:22:4A:EA:89:7E:9E:85:53:81:72:5E
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 : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Jan 15 07:22:32.716 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B7:0B:BE:68:18:3F:E0:B1:55:9E:3C:
  • 12:18:0D:81:3C:B7:E9:04:95:1C:2E:5C:93:43:C8:D1:
  • 41:53:36:BB:F3:02:21:00:91:71:35:5B:FA:36:4A:6E:
  • 19:62:EB:67:C5:CC:A2:CB:EA:4E:83:A4:FF:5B:DE:C7:
  • B5:A2:20:AE:09:C3:EC:90
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Jan 15 07:22:33.205 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:66:78:07:B4:3A:C8:10:E1:FB:F0:04:44:
  • 6F:8C:55:BD:23:F6:28:E7:FF:C8:8E:B4:C6:9E:83:B6:
  • 94:C2:DB:10:02:21:00:A0:0F:CD:9E:FA:AF:58:B7:11:
  • A1:31:F6:FC:CF:CD:F1:0A:53:91:A7:CA:B3:56:C2:BF:
  • 58:FD:95:76:DC:8B:D1