SSL-Tools

SSL check results of sync.knop-neustadt.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for sync.knop-neustadt.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 Wed, 25 Nov 2020 09:22:07 +0000

We can not guarantee a secure connection to the mailservers of sync.knop-neustadt.de!

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

/mailservers/sync.knop-neustadt.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @sync.knop-neustadt.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
sync.knop-neustadt.de
90.187.237.165
 -
supported
sync.knop-neustadt.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s
sync.knop-neustadt.de
2a02:8108::1d:28d7:5d18:f089:e3bb
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

We have not received any emails from a @sync.knop-neustadt.de address so far. Test mail delivery

Certificates

First seen at:

CN=sync.knop-neustadt.de

Certificate chain
Subject
Common Name (CN)
  • sync.knop-neustadt.de
Alternative Names
  • sync.knop-neustadt.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-15
Not valid after
2021-01-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
24:DB:8B:2C:29:6B:16:56:E0:79:6A:78:21:69:85:4D:09:AC:74:B9:18:A4:26:D7:88:DC:78:DC:01:F8:D9:B3
SHA1
A8:1C:C7:08:EE:4C:D2:67:0E:D5:A8:0E:D5:F3:27:8A:A4:3D:F0:15
X509v3 extensions
subjectKeyIdentifier
  • 5B:35:19:09:82:6D:A6:10:4D:63:FE:3C:C6:0A:49:1E:A0:15:CF:D2
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Oct 15 04:35:22.750 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:82:2A:E5:DA:FD:E8:1F:45:E3:8D:4E:
  • AB:DF:AF:11:DD:C5:8D:0F:F6:02:F5:69:52:BE:95:06:
  • B0:07:BD:9B:AB:02:21:00:BB:3F:EE:4E:10:1D:E9:ED:
  • D2:DD:3F:71:FC:59:7D:C9:16:EE:24:B7:28:A9:6F:E8:
  • 1C:B8:4D:12:12:11:60:C8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Oct 15 04:35:22.808 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9E:A3:99:FA:C3:96:F9:5C:46:39:E5:
  • 3B:D9:AC:19:AA:12:E0:B4:CC:C6:CD:E3:62:3F:05:A7:
  • 01:73:71:B2:FC:02:20:32:AF:CF:92:39:6B:BD:CC:FA:
  • 46:7A:D9:68:65:DC:07:61:60:84:C6:A3:4F:7C:E2:53:
  • CD:2E:A2:20:55:E1:22