SSL-Tools

SSL check results of your-sponsoring.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for your-sponsoring.eu 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, 05 Aug 2020 22:23:20 +0000

The mailservers of your-sponsoring.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @your-sponsoring.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.hchristo.de
2a0a:51c0::13b:194:48:168:72
 5
supported
mx.hchristo.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mx.hchristo.de
194.48.168.72
 5
supported
mx.hchristo.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mx.hchristo.de
2a0a:51c0::13b:194:48:168:72
 10
supported
mx.hchristo.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mx.hchristo.de
194.48.168.72
 10
supported
mx.hchristo.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 @your-sponsoring.eu address so far. Test mail delivery

Certificates

First seen at:

CN=mx.hchristo.de

Certificate chain
Subject
Common Name (CN)
  • mx.hchristo.de
Alternative Names
  • mx.hchristo.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-07-12
Not valid after
2020-10-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
62:B8:08:CF:BA:C6:A8:FD:8B:32:45:C6:BA:58:20:CD:4C:7D:7B:4C:3C:44:E0:60:40:80:E9:F9:14:D8:C4:F4
SHA1
0A:2A:05:FC:A8:02:A2:90:EE:B4:32:FE:E9:4A:CA:AF:01:9B:49:41
X509v3 extensions
subjectKeyIdentifier
  • 1C:4D:2A:BE:5E:16:79:6D:B7:4A:A3:00:D2:05:3A:C0:EB:24:6D:EF
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 : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
  • 4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
  • Timestamp : Jul 12 15:58:36.062 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:76:7D:5C:A6:A6:E4:B7:4A:47:B6:32:B6:
  • A5:74:C4:89:68:A3:23:9F:18:35:6B:9F:DF:34:13:3B:
  • 39:A5:D6:44:02:20:3E:E2:F5:27:1A:2D:EF:3C:C6:E3:
  • 76:2F:DA:6D:98:E5:AC:2C:D0:2E:C2:54:4B:E5:58:AC:
  • 25:E3:BC:24:2F:B8
  • 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 : Jul 12 15:58:36.044 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C7:94:11:5A:EE:38:D8:88:7D:AE:5E:
  • A4:57:A6:7E:79:77:ED:91:55:E7:7F:BC:8E:4A:95:A8:
  • CD:15:EA:C4:82:02:21:00:9A:23:CA:3F:38:81:EC:2E:
  • 62:C1:B0:9F:BA:CC:57:73:F5:C0:83:22:A8:47:A2:E7:
  • 78:6D:63:ED:9D:03:7B:1A