SSL-Tools

SSL check results of spd-friedrichshafen.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for spd-friedrichshafen.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 Sat, 14 Sep 2024 13:58:15 +0000

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

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

/mailservers/spd-friedrichshafen.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spd-friedrichshafen.de
2001:1b60:3:267:5416::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.spd-friedrichshafen.de
87.118.126.90
 10
supported
kira.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-friedrichshafen.de address so far. Test mail delivery

Certificates

First seen at:

CN=kira.unaone.net

Certificate chain
  • kira.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)
  • kira.unaone.net
Alternative Names
  • kira.unaone.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-08-08
Not valid after
2024-11-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C5:7A:3D:24:EB:41:6F:FA:AB:14:8C:96:85:28:1A:38:5E:5C:10:42:60:10:FA:71:30:E6:AA:4C:25:E6:96:15
SHA1
C4:DD:29:3C:2B:52:C4:2B:71:5E:E9:97:0E:B5:CF:C5:ED:A8:3A:F3
X509v3 extensions
subjectKeyIdentifier
  • 06:97:D2:F1:EF:EF:B9:BF:57:39:C7:38:74:F0:5D:BA:A1:1D:C2:88
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 : 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 : Aug 8 22:35:10.496 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C1:59:B0:DA:72:D6:46:64:58:82:CE:
  • 77:8B:98:D9:83:A0:30:FB:FB:50:DF:DE:2D:EC:96:E9:
  • 75:41:D3:79:54:02:20:1C:E8:FF:FB:3C:77:AC:8C:0E:
  • F5:E1:6A:2F:39:6A:C9:CC:F2:85:8E:11:22:EE:B8:67:
  • 25:A6:EC:11:FB:36:34
  • 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 : Aug 8 22:35:10.507 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:38:25:BD:4A:F8:A7:36:5D:D0:F3:42:F1:
  • 42:42:44:F3:A1:83:EA:A4:47:2B:1B:05:1E:42:37:96:
  • 80:E8:9B:E1:02:21:00:C6:1B:51:A9:B9:1C:35:F5:7B:
  • 76:33:93:64:3D:9C:3A:37:47:FC:EC:1B:10:D6:3D:DC:
  • 68:84:49:FB:63:27:0F