SSL-Tools

SSL check results of paragonsystems.com.pg

NEW You can also bulk check multiple servers.

Discover if the mail servers for paragonsystems.com.pg 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, 23 Jan 2025 00:48:42 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
paragonsystems.com.pg
172.105.169.254
 -
supported
paragonsystems.com.pg
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s
paragonsystems.com.pg
2400:8907::f03c:94ff:fe35:5588
 -
supported
paragonsystems.com.pg
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s

Outgoing Mails

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

Certificates

First seen at:

CN=paragonsystems.com.pg

Certificate chain
  • paragonsystems.com.pg
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • paragonsystems.com.pg
Alternative Names
  • paragonsystems.com.pg
  • www.paragonsystems.com.pg
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-22
Not valid after
2025-04-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3D:9A:FF:2A:04:B8:03:2D:69:25:12:3F:AA:E8:79:51:8A:18:1C:5A:C0:A6:4D:03:A8:57:17:BC:56:7E:BC:96
SHA1
DA:AF:99:16:CF:C0:51:00:43:7F:75:EA:2A:F7:2B:B5:4F:90:42:7D
X509v3 extensions
subjectKeyIdentifier
  • 2D:8E:79:78:F9:A5:07:87:EA:E6:9E:A4:38:E8:C5:D8:B8:29:C9:06
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 23 00:19:39.115 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:32:3E:11:C8:0A:F3:67:ED:00:11:35:3A:
  • 6F:01:76:E9:8F:15:ED:12:98:70:4D:C9:9E:FB:CA:16:
  • 2E:DA:06:C7:02:21:00:F0:75:CF:9C:5E:D9:E3:D9:9E:
  • 77:69:7C:F4:48:65:E2:7E:51:3C:E0:84:EC:92:BD:43:
  • 56:93:12:18:47:B5:DF
  • 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 : Jan 23 00:19:39.149 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AF:AD:DD:56:58:38:8E:F3:C4:42:42:
  • FE:EE:90:22:40:AF:1E:39:40:AD:24:9A:64:BE:75:58:
  • 3B:21:5B:F8:F5:02:21:00:B5:B9:4B:CE:67:2E:BA:53:
  • 65:E0:DA:4D:E2:8C:E9:B1:5F:22:88:61:FE:2C:73:66:
  • A7:B4:82:DF:10:B7:4E:C1