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 Mon, 08 Jun 2020 00:36:55 +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:

/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
3 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
2020-05-04
Not valid after
2020-08-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
50:EF:CB:15:1C:72:78:39:43:AB:E3:10:74:3F:F8:ED:98:57:E6:52:D7:11:48:52:25:B5:09:84:FD:47:61:E7
SHA1
76:BE:12:72:FA:F9:91:69:53:37:F5:3B:B3:10:EE:1B:64:20:91:21
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 : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
  • 7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
  • Timestamp : May 4 16:55:26.911 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:25:07:9B:9D:50:2B:2F:EF:BA:4A:FE:73:
  • 4B:DF:4E:9D:67:6F:D5:AC:DD:01:17:EB:73:6D:A4:46:
  • EE:D2:0A:BD:02:21:00:D6:7A:A5:7E:A8:E2:D3:22:F6:
  • 95:A8:8E:82:94:BC:16:9E:08:2C:A3:6F:92:C3:AE:EA:
  • 1C:B4:61:B2:A0:6F:69
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : May 4 16:55:26.952 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9E:4E:91:A2:A8:AB:DB:65:63:EB:FA:
  • 37:C5:FF:A8:B1:15:35:72:2D:3D:8F:25:64:8C:F0:74:
  • 30:B0:5D:5D:8C:02:20:11:43:BB:C6:6D:33:79:25:61:
  • E8:69:19:4D:9A:86:56:64:A6:C1:EA:AA:3F:73:3B:D6:
  • 65:AD:B6:DC:58:84:D8