SSL-Tools

SSL check results of eldesign.bg

NEW You can also bulk check multiple servers.

Discover if the mail servers for eldesign.bg 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 Fri, 27 Nov 2020 15:12:03 +0000

We can not guarantee a secure connection to the mailservers of eldesign.bg!

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

/mailservers/eldesign.bg

Servers

Incoming Mails

These servers are responsible for incoming mails to @eldesign.bg addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
a.mx.eldesign.bg
95.43.220.184
 0
supported
mx.eldesign.bg
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
4 s
b.mx.eldesign.bg
95.111.46.80
Results incomplete
0 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx.eldesign.bg

Certificate chain
  • mx.eldesign.bg
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority
      Let's Encrypt Authority X3
Subject
Common Name (CN)
  • mx.eldesign.bg
Alternative Names
  • mx.eldesign.bg
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-24
Not valid after
2021-01-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7A:56:98:12:8E:82:98:9E:DD:D9:88:44:6A:98:6D:E3:8F:14:1F:E7:9D:E0:BC:E1:45:F4:A7:7D:EC:2F:01:1C
SHA1
1D:BA:3B:99:63:CF:03:56:65:C9:2B:57:82:CC:0E:92:3D:BE:30:BC
X509v3 extensions
subjectKeyIdentifier
  • 13:CE:44:A0:D5:57:23:33:B6:DB:B8:9B:CD:B9:44:74:D0:68:8F:A2
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Oct 24 21:48:15.253 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:60:02:12:CE:1D:C3:C5:F9:01:53:04:4C:
  • B4:7D:49:4E:81:F7:36:CB:45:99:3A:D2:1D:3F:B4:2E:
  • DB:AC:59:74:02:21:00:83:09:AF:27:25:FF:1F:D1:29:
  • 81:D5:CC:CF:86:CF:3C:11:9D:25:4C:20:6B:9F:41:80:
  • 33:06:73:6A:29:01:04
  • 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 24 21:48:15.322 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:99:96:5D:9B:08:65:12:9A:D4:50:96:
  • CD:1E:99:C0:D6:93:72:B2:E4:0C:D2:76:24:2B:19:D4:
  • 33:20:58:F7:FA:02:21:00:88:44:27:B2:CA:2A:C5:41:
  • D9:0C:46:2B:9C:B6:78:37:5C:1E:C5:CB:42:AC:F6:78:
  • AD:8A:88:C7:6B:3B:B0:EC