SSL-Tools

SSL check results of mx1.mediadesign.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mx1.mediadesign.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, 27 May 2020 11:38:21 +0000

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

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

/mailservers/mx1.mediadesign.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.mediadesign.de
94.186.199.231
 10
supported
mx1.mediadesign.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_EXPORT_WITH_RC4_40_MD5
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
18 s
mx2.mediadesign.de
89.31.143.1
Results incomplete
20 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 @mx1.mediadesign.de address so far. Test mail delivery

Certificates

First seen at:

CN=mx1.mediadesign.de

Certificate chain
Subject
Common Name (CN)
  • mx1.mediadesign.de
Alternative Names
  • mx1.mediadesign.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-22
Not valid after
2020-08-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CD:7E:9A:78:E4:42:D7:B5:07:37:75:F8:73:1F:81:1F:FD:F2:D2:E1:CD:F6:D4:25:A4:93:45:8C:FB:51:5F:24
SHA1
1B:34:06:CC:D5:B5:C7:8A:83:D4:5C:D2:88:E7:A5:0E:DF:E6:AF:F8
X509v3 extensions
subjectKeyIdentifier
  • E3:3E:A8:DE:E3:20:FB:ED:BC:85:52:EF:A6:03:2B:99:3B:6D:57:50
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 : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
  • 7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
  • Timestamp : May 22 10:33:34.553 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:02:6E:FA:D3:EE:4A:BC:A9:BB:43:5D:39:
  • E9:FB:8F:59:00:35:B2:22:46:77:EA:C8:3C:64:0A:FE:
  • D7:34:C7:CF:02:20:44:2E:60:39:75:E9:FE:25:46:DE:
  • 7B:38:62:B0:99:39:A2:1A:B6:79:AD:0E:C0:06:56:5E:
  • A4:CD:12:5B:7E:B5
  • 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 22 10:33:34.591 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D0:4F:67:70:26:EC:5C:EE:D1:5B:6F:
  • 05:FC:49:6C:EF:E9:0B:FF:95:8E:F5:D0:DC:0D:87:83:
  • 69:6D:7F:27:FB:02:21:00:C4:70:52:52:C7:53:C0:C0:
  • FD:8C:00:23:05:17:8E:B9:35:24:EF:26:F8:12:3E:9A:
  • B2:13:DF:14:B3:7C:46:C1