SSL-Tools

SSL check results of spo-bruchsal.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for spo-bruchsal.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, 24 Apr 2024 00:54:25 +0000

The mailservers of spo-bruchsal.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @spo-bruchsal.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spo-bruchsal.de
185.9.178.50
 10
supported
mail.spo-bruchsal.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.spo-bruchsal.de

Certificate chain
  • mail.spo-bruchsal.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)
  • mail.spo-bruchsal.de
Alternative Names
  • autoconfig.spo-bruchsal.de
  • autoconfig.sportorthopaedie-bruchsal.de
  • autodiscover.spo-bruchsal.de
  • autodiscover.sportorthopaedie-bruchsal.de
  • mail.spo-bruchsal.de
  • mail.sportorthopaedie-bruchsal.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-23
Not valid after
2024-07-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3A:C4:51:5B:B9:5D:CA:FE:9A:1D:55:48:9A:E3:FF:EB:5D:EC:9B:A4:E4:B9:C4:DE:E9:75:74:CE:EA:FC:95:EF
SHA1
85:3C:72:18:D4:5C:AE:DA:63:2C:DB:CB:67:03:77:28:5E:56:23:8B
X509v3 extensions
subjectKeyIdentifier
  • 45:A7:3E:DD:BE:6B:0B:2B:EE:B8:9A:4C:0A:72:94:5D:AC:C1:B0:7C
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 : 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 24 00:44:48.546 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:15:27:71:18:2F:EA:AD:3B:9B:62:63:50:
  • 66:98:C5:C0:16:00:F9:A3:47:E4:5C:43:44:64:C3:08:
  • 13:2D:44:5F:02:20:24:93:F0:AC:2D:E6:FF:AF:45:5C:
  • B0:5B:15:C6:C8:DF:91:39:03:6C:D6:09:77:E3:D5:06:
  • 8D:21:50:59:2D:20
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 24 00:44:48.612 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EC:C2:78:9C:4D:C5:08:FE:0D:62:29:
  • 1E:EC:31:AE:C1:F6:94:20:E9:81:9A:D7:7B:D8:8E:39:
  • 1A:22:DB:C7:EA:02:20:3C:82:DC:13:75:C7:22:5F:2F:
  • D9:44:2C:C1:28:C0:A6:98:9D:7B:0C:77:2C:3D:86:6C:
  • E2:14:18:18:6A:48:FF