SSL-Tools

SSL check results of reckoningz.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for reckoningz.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 Mon, 05 May 2025 00:31:36 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.reckoningz.com
50.6.153.169
 0
supported
cpanel.zey.jfk.mybluehost.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
42 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpanel.zey.jfk.mybluehost.me

Certificate chain
  • cpanel.zey.jfk.mybluehost.me
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • cpanel.zey.jfk.mybluehost.me
Alternative Names
  • autodiscover.zey.jfk.mybluehost.me
  • cpanel.zey.jfk.mybluehost.me
  • cpcalendars.zey.jfk.mybluehost.me
  • cpcontacts.zey.jfk.mybluehost.me
  • mail.reckoningz.com
  • mail.zey.jfk.mybluehost.me
  • reckoningz.com
  • webdisk.zey.jfk.mybluehost.me
  • webmail.zey.jfk.mybluehost.me
  • www.reckoningz.com
  • www.zey.jfk.mybluehost.me
  • zey.jfk.mybluehost.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-02-10
Not valid after
2025-05-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F8:4E:9D:3A:AC:AD:CB:AF:D4:06:BE:BE:8E:92:ED:9A:94:90:E1:B7:31:DB:ED:69:BE:43:2D:1B:EE:CF:25:4C
SHA1
11:01:BC:48:62:2B:EC:79:4C:FE:C9:47:AE:95:F0:F8:AE:EE:3E:13
X509v3 extensions
subjectKeyIdentifier
  • CC:04:7C:91:F2:21:2B:7D:BC:70:9C:CA:C5:5E:C1:E1:3B:D5:18:0A
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Feb 10 18:45:55.221 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:85:26:B6:A5:6A:79:0A:43:FC:F5:93:
  • C5:D9:C5:AA:7E:09:12:EA:3C:74:35:F5:9C:22:44:2C:
  • EB:A6:85:77:C5:02:21:00:D9:03:59:12:09:F9:7B:B8:
  • 3B:B0:3F:4C:41:01:9D:F6:CF:22:C6:32:34:C1:90:46:
  • 63:44:EF:20:E2:74:3F:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Feb 10 18:45:55.254 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:66:E1:EC:46:86:CB:CF:12:7A:8E:56:6E:
  • 42:54:FC:EC:E4:F6:8A:0D:82:9D:82:77:7C:B5:4D:98:
  • 48:94:44:27:02:20:79:44:9C:50:36:ED:13:14:39:8D:
  • BA:A1:18:31:2C:FD:24:BE:18:EF:5B:27:7E:E8:FB:3E:
  • FD:98:3C:2F:A3:80