SSL check results of scholsweb.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for scholsweb.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

Report created Wed, 06 Nov 2019 20:22:54 +0000

We can not guarantee a secure connection to the mailservers of scholsweb.de!

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

https://ssl-tools.net/mailservers/scholsweb.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @scholsweb.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
kundencenter.scholsweb.de
2a02:180:6:1::14c
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
kundencenter.scholsweb.de
91.143.80.82
10
supported
kundencenter.scholsweb.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=kundencenter.scholsweb.de

Certificate chain
  • kundencenter.scholsweb.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Unknown Authority

      Let's Encrypt Authority X3
Subject
Common Name (CN)
  • kundencenter.scholsweb.de
Alternative Names
  • kundencenter.scholsweb.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2019-11-06
Not valid after
2020-02-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4C:88:DF:E5:4D:C3:F3:C2:39:42:35:CC:9A:B9:49:21:78:35:45:71:6A:26:69:9D:3E:9E:E7:56:AC:5E:E2:50
SHA1
2E:93:17:57:78:6A:67:6E:02:29:3F:3A:E8:0D:6B:FC:0B:9A:7F:02
X509v3 extensions
subjectKeyIdentifier
  • 7F:06:05:F3:15:D6:F9:99:71:9C:B8:53:1E:00:A3:DD:D4:95:3E:E5
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Nov 6 18:25:31.606 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:02:7B:44:6A:7E:DE:E8:B3:8E:F5:5A:45:
  • EF:87:7B:E3:02:4C:DC:93:C5:B4:93:AD:56:13:0F:17:
  • 60:EB:54:48:02:20:7F:68:1F:54:7A:E3:D6:D4:04:64:
  • A0:D2:99:6B:8C:13:BD:4D:21:9B:D1:17:99:0E:12:99:
  • C5:63:2E:59:22:37
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Nov 6 18:25:31.657 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FB:F2:16:EC:72:B2:7B:83:86:B8:EC:
  • 56:DD:ED:C1:7D:CF:AB:FA:98:10:B0:A0:82:57:6C:53:
  • 77:99:8C:EC:49:02:20:00:87:9E:B8:F5:9D:99:F5:64:
  • 38:37:A5:96:D3:AD:B4:07:A3:45:E4:BE:24:0E:E5:96:
  • E2:82:35:D4:93:57:95