SSL-Tools

SSL check results of sc-lippstadt.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for sc-lippstadt.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 Tue, 02 Apr 2024 14:40:41 +0000

We can not guarantee a secure connection to the mailservers of sc-lippstadt.de!

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

/mailservers/sc-lippstadt.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @sc-lippstadt.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.sc-lippstadt.de
2a01:7e0:0:132::14
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.sc-lippstadt.de
79.174.3.103
 10
supported
sc-lippstadt.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=sc-lippstadt.de

Certificate chain
  • sc-lippstadt.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • sc-lippstadt.de
Alternative Names
  • *.sc-lippstadt.de
  • sc-lippstadt.de
  • sclippstadt.de
  • www.sclippstadt.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-11
Not valid after
2024-06-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E7:04:56:2E:90:EB:74:92:23:3E:1E:0C:41:5B:2B:1E:50:06:50:A1:26:3B:81:A4:C6:29:1C:A8:19:60:FB:44
SHA1
AE:D3:63:B2:7F:15:F7:38:01:44:7A:F9:8F:E1:BF:7B:55:C9:17:9B
X509v3 extensions
subjectKeyIdentifier
  • F1:9F:06:51:D2:9B:1B:FA:0B:8D:58:89:94:78:43:9D:16:3D:07:C0
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 : 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 : Mar 11 15:31:44.296 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6E:31:1A:10:C5:C3:F5:6F:0C:E5:FD:57:
  • 56:82:01:23:F3:EF:A1:94:2E:A9:DC:52:D8:9C:2C:C8:
  • AE:28:F6:BC:02:21:00:B1:F0:EB:22:59:9E:94:DF:31:
  • 0C:41:A6:3B:48:AF:80:72:A1:BC:83:CD:D4:E4:9C:62:
  • 49:A0:07:10:F2:B3:AB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 11 15:31:44.319 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D8:D5:B4:E7:3E:49:24:52:A1:33:C0:
  • 72:74:0F:39:41:CD:FC:DB:46:37:48:8F:F8:A6:CF:FA:
  • 39:E2:CD:2D:87:02:21:00:FC:BB:6E:3C:59:50:F3:0B:
  • 20:00:2F:F7:33:06:78:D8:01:E8:87:7C:2E:EA:28:0B:
  • C3:80:0F:DE:C2:65:2B:6C