SSL-Tools

SSL check results of presys.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for presys.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 Tue, 26 Mar 2024 21:01:59 +0000

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

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

/mailservers/presys.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
s1.mail.pciwest.net
2604:2400:a::425
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
s1.mail.pciwest.net
64.5.1.149
 10
supported
s1.mail.pciwest.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_EXPORT_WITH_RC4_40_MD5
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
20 s

Outgoing Mails

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

Certificates

First seen at:

CN=s1.mail.pciwest.net

Certificate chain
  • s1.mail.pciwest.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • s1.mail.pciwest.net
Alternative Names
  • s1.mail.pciwest.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-20
Not valid after
2024-06-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
69:0B:94:5F:BC:D0:02:B9:82:8C:2C:C6:1D:EB:8C:97:C2:36:F4:44:58:4C:96:F2:62:31:70:5E:B2:F3:F8:92
SHA1
E5:D2:55:9E:33:56:1C:1D:5C:72:C0:5A:DB:AA:1E:87:64:FE:56:F8
X509v3 extensions
subjectKeyIdentifier
  • 4F:92:AA:24:0E:3D:48:18:73:F2:9D:83:E8:97:A5:05:A9:52:3D:72
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 : Mar 20 19:43:20.129 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:23:11:69:DC:7B:75:97:4A:C4:84:DD:40:
  • 7C:63:44:5C:F8:EE:6F:32:B6:C9:EE:9E:FE:86:1F:3E:
  • 84:ED:6D:A6:02:21:00:CB:DF:BD:02:16:5E:A5:DE:A1:
  • 3E:3D:89:F8:48:00:94:10:AD:F6:50:6D:AB:18:A0:E2:
  • 6C:0B:8B:33:8C:3E:90
  • 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 : Mar 20 19:43:20.151 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:50:FB:7B:CC:79:6B:0C:FF:9B:43:9F:AF:
  • B6:99:0F:E1:1F:FA:56:60:FC:6F:36:3A:C0:AB:AC:BE:
  • AC:A2:5F:C6:02:21:00:C5:37:77:0E:96:6C:BA:DA:AE:
  • 66:75:8B:1C:D3:15:9B:D0:FC:7E:79:37:AB:A6:48:DE:
  • 35:36:F6:33:74:94:FF