SSL-Tools

SSL check results of spd-sindelfingen.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for spd-sindelfingen.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 Thu, 10 Oct 2024 00:30:46 +0000

We can not guarantee a secure connection to the mailservers of spd-sindelfingen.de!

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

/mailservers/spd-sindelfingen.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @spd-sindelfingen.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spd-sindelfingen.de
2001:1b60:3:234:233::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.spd-sindelfingen.de
87.118.120.166
 10
supported
spock.unaone.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=spock.unaone.net

Certificate chain
  • spock.unaone.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • spock.unaone.net
Alternative Names
  • spock.unaone.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-16
Not valid after
2024-12-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A4:F5:E5:76:EA:FF:28:08:62:3F:20:15:CF:C8:6A:01:BF:6F:91:69:F0:3D:A7:88:AA:63:E1:CD:99:AE:3D:A1
SHA1
FB:71:3F:BC:6F:68:24:8A:5B:62:6D:25:B1:B1:74:B8:BC:01:29:72
X509v3 extensions
subjectKeyIdentifier
  • 13:25:35:D1:FD:B7:54:6A:98:2E:CC:08:CC:AB:80:4B:55:51:B7:B8
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Sep 16 22:14:14.856 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AC:69:0A:0A:A0:F1:E5:61:7F:44:FF:
  • CB:02:9C:6F:BF:4B:74:1C:65:5D:9F:FD:16:2C:79:D2:
  • 79:C9:97:ED:C8:02:21:00:B4:69:47:93:53:08:2B:A7:
  • 40:94:A8:FB:51:2E:C0:AF:87:83:F6:4C:14:00:AF:5A:
  • FB:66:5F:57:3B:69:21:AB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Sep 16 22:14:14.852 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F6:C1:4C:AE:6E:40:D9:3D:1C:AA:C8:
  • 2B:7A:FF:C8:53:EA:EC:A5:47:3F:23:61:F9:56:4B:3E:
  • 31:EB:9B:75:BB:02:21:00:98:09:EF:24:E0:6B:F5:29:
  • 56:30:D4:9D:41:59:F4:5E:C2:04:24:FA:F9:49:BB:7A:
  • 07:54:12:AE:60:80:EE:24