SSL-Tools

SSL check results of riverforcolorado.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for riverforcolorado.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, 18 Apr 2024 22:37:14 +0000

The mailservers of riverforcolorado.com can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.riverforcolorado.com
162.241.253.78
 0
supported
cpanel.qyk.sro.mybluehost.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
44 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpanel.qyk.sro.mybluehost.me

Certificate chain
  • cpanel.qyk.sro.mybluehost.me
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • cpanel.qyk.sro.mybluehost.me
Alternative Names
  • autodiscover.qyk.sro.mybluehost.me
  • cpanel.qyk.sro.mybluehost.me
  • cpcalendars.qyk.sro.mybluehost.me
  • cpcontacts.qyk.sro.mybluehost.me
  • mail.qyk.sro.mybluehost.me
  • mail.riverforcolorado.com
  • qyk.sro.mybluehost.me
  • riverforcolorado.com
  • webdisk.qyk.sro.mybluehost.me
  • webmail.qyk.sro.mybluehost.me
  • www.qyk.sro.mybluehost.me
  • www.riverforcolorado.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-28
Not valid after
2024-05-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
61:C6:A9:CC:21:5E:95:B8:96:77:92:C4:26:79:B2:47:E3:FA:EA:37:33:92:12:12:88:03:A3:E4:F0:43:0A:F9
SHA1
B2:71:89:49:01:41:CC:7B:4A:12:00:C1:BD:E3:92:7A:FB:21:F1:B7
X509v3 extensions
subjectKeyIdentifier
  • 49:5A:95:6D:38:4B:E2:79:C3:24:01:EF:BC:D6:07:A5:18:4E:BF:9B
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Feb 28 23:06:33.279 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:13:78:39:6E:63:CA:F4:9D:A6:C5:38:B6:
  • F6:0B:D1:A8:33:05:41:2E:92:CF:40:C1:DF:BC:AA:22:
  • 04:DE:86:99:02:20:59:AB:51:33:7E:60:87:EF:FF:D5:
  • 29:21:F6:68:4D:1C:8F:D5:5F:42:06:A8:23:E0:6A:E5:
  • BC:8D:A6:B0:43:D1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Feb 28 23:06:33.384 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A2:06:2C:AF:54:EB:85:90:B5:00:74:
  • 6C:C6:45:82:0A:BB:67:F6:7D:A2:12:2F:51:77:68:85:
  • 38:5E:84:9A:31:02:21:00:DD:C7:02:38:A8:DE:FB:51:
  • 4B:36:00:BB:4B:FD:30:49:A4:75:7D:35:67:C7:23:83:
  • 7A:3C:3C:84:39:50:2F:42