SSL-Tools

SSL check results of spd-rastatt.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for spd-rastatt.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, 05 Dec 2024 01:31:21 +0000

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

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

/mailservers/spd-rastatt.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spd-rastatt.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-rastatt.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-rastatt.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
      • R10
        • 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)
  • R10
validity period
Not valid before
2024-10-07
Not valid after
2025-01-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A0:C7:8D:0D:4B:A6:D5:3D:78:BB:7A:73:AC:E3:BC:2D:4F:62:2B:61:63:61:BF:F3:15:F8:8C:E7:D4:BA:2A:34
SHA1
50:83:D1:D7:71:F9:60:91:EC:E1:9E:90:41:94:9B:24:27:9A:9E:B0
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:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 7 22:35:12.010 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7A:8A:31:2F:87:92:12:D3:BF:A1:2D:ED:
  • 2A:C2:17:5A:1B:43:4B:87:A2:FE:B8:3D:A1:1C:C9:9C:
  • 8B:64:20:14:02:21:00:95:50:D7:CC:09:E2:AF:20:AC:
  • AA:CB:1B:16:CF:5C:FA:7F:AD:78:89:B3:7C:F1:33:47:
  • 35:B3:48:40:25:74:29
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Oct 7 22:35:11.955 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:25:E8:AE:A1:AC:C8:05:20:C1:83:71:46:
  • CD:D1:D4:C7:BD:08:AB:AB:CE:E1:7F:82:50:3E:B2:B6:
  • 3D:AA:06:BD:02:21:00:F1:91:60:E7:B0:73:37:17:EF:
  • E8:69:2A:AB:07:02:4E:91:24:62:76:19:34:5A:02:B8:
  • 05:8A:08:2B:96:41:1F