SSL-Tools

SSL check results of plginc.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for plginc.org 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, 21 Jan 2022 01:15:38 +0000

The mailservers of plginc.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @plginc.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
plginc.org
173.254.38.135
 -
supported
cpcontacts.pinnacleleadership.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
45 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpcontacts.pinnacleleadership.com

Certificate chain
  • cpcontacts.pinnacleleadership.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • cpcontacts.pinnacleleadership.com
Alternative Names
  • autodiscover.pinnacleleadership.com
  • cpanel.pinnacleleadership.com
  • cpcalendars.pinnacleleadership.com
  • cpcontacts.pinnacleleadership.com
  • mail.pinnacleleadership.com
  • mail.plginc.org
  • pinnacleleadership.com
  • plginc.org
  • webdisk.pinnacleleadership.com
  • webmail.pinnacleleadership.com
  • www.pinnacleleadership.com
  • www.plginc.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-12-18
Not valid after
2022-03-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2B:EE:FC:0B:BC:68:A8:C0:F3:B1:63:C9:D7:9F:56:AB:4C:AA:58:DA:09:E3:E9:5F:6A:06:15:86:E2:F1:A1:83
SHA1
14:F3:BA:25:29:89:1C:AD:FB:D4:6B:DB:72:F3:88:D0:26:43:21:E3
X509v3 extensions
subjectKeyIdentifier
  • D3:40:DA:DE:E3:72:26:83:2A:FA:88:C3:5C:57:3E:0A:06:FE:A8:94
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
  • 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 : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
  • 4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
  • Timestamp : Dec 18 14:24:36.116 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2D:E4:0A:28:F3:37:0F:FE:D6:DF:7C:5F:
  • D7:F5:EA:49:53:B5:9B:3A:B6:82:3F:E2:F9:B7:B4:5D:
  • 9C:84:D7:17:02:20:4E:62:4A:21:5E:5D:89:D3:62:9A:
  • 3E:ED:3A:1C:92:89:76:27:62:FB:38:85:0B:5C:0D:30:
  • 33:A2:26:F3:E5:B3
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Dec 18 14:24:36.132 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C1:E1:06:6C:6E:BC:D0:AF:4C:24:50:
  • 6A:BF:C7:2C:CB:90:1F:A4:E1:8A:A0:47:06:BD:F0:13:
  • 53:8C:85:A9:58:02:21:00:A3:C6:78:CF:29:42:0A:B3:
  • A1:8C:C8:1D:BA:4D:4B:12:1A:7B:19:66:0F:0A:E6:02:
  • 4D:EA:28:CF:30:61:10:A3