SSL-Tools

SSL check results of silverorange.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for silverorange.com 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 Thu, 28 May 2020 00:32:32 +0000

We can not guarantee a secure connection to the mailservers of silverorange.com!

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

/mailservers/silverorange.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @silverorange.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.silverorange.com
24.222.7.12
 10
supported
mail.silverorange.com
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
  • SSLv3
17 s
mail2.silverorange.com
18.205.88.9
Results incomplete
100
unsupported
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 @silverorange.com address so far. Test mail delivery

Certificates

First seen at:

CN=mail.silverorange.com

Certificate chain
Subject
Common Name (CN)
  • mail.silverorange.com
Alternative Names
  • mail.silverorange.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-04-27
Not valid after
2020-07-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
32:13:1C:5C:45:ED:69:7E:B4:68:08:9D:6E:30:BF:9A:91:C2:57:C8:C4:6F:BB:6C:E5:76:71:5D:6D:1F:27:D9
SHA1
15:DD:AF:0B:20:0F:4B:26:37:20:46:68:45:09:D2:B7:2E:1A:99:B6
X509v3 extensions
subjectKeyIdentifier
  • 8B:A9:08:FE:5B:D3:41:B1:71:08:61:CB:E3:22:39:90:A8:BD:EF:1D
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 : Apr 27 11:02:43.362 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:47:8D:1C:75:DE:DE:7D:72:20:1B:51:28:
  • 31:70:84:1B:F4:72:9B:7C:3F:DB:C1:C6:94:8A:AD:6D:
  • FE:3C:3B:B2:02:21:00:EA:71:FA:09:3C:E9:A9:84:B8:
  • 7F:4B:E4:07:F3:21:AC:A6:E2:00:55:3C:03:EA:C3:B4:
  • 30:8A:80:B1:4F:C5:17
  • 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 : Apr 27 11:02:43.522 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:45:D8:A9:87:C3:89:59:69:32:EF:DC:1B:
  • F6:7F:8D:D0:C2:CF:FF:BA:C8:18:29:2B:08:79:FC:E6:
  • 34:59:19:BC:02:20:5B:A6:99:24:87:3A:6B:F8:8D:DF:
  • AB:F9:8A:66:B1:17:8F:45:42:0D:8B:1E:E0:7E:2B:B6:
  • 9A:B1:99:F6:FB:0C