SSL-Tools

SSL check results of percom.ch

NEW You can also bulk check multiple servers.

Discover if the mail servers for percom.ch 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 Sat, 16 Aug 2025 00:30:09 +0000

The mailservers of percom.ch can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @percom.ch addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.percloud.ch
2a01:4f8:1c1a:c553::1
 10
supported
mail.percloud.ch
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mail.percloud.ch
138.199.211.180
 10
supported
mail.percloud.ch
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.percloud.ch

Certificate chain
  • mail.percloud.ch
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.percloud.ch
Alternative Names
  • autoconfig.percloud.ch
  • autoconfig.percom.ch
  • autodiscover.percloud.ch
  • autodiscover.percom.ch
  • mail.percloud.ch
  • mta-sts.percloud.ch
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-08-12
Not valid after
2025-11-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F9:6F:A0:C9:C7:1B:55:B4:41:EB:07:30:E5:66:BE:95:09:64:32:CE:32:21:A1:9C:DB:B7:2D:DA:EA:23:A5:34
SHA1
26:03:EF:6E:BE:D2:DC:B3:A1:15:C9:40:3A:1C:5A:A9:77:F4:5E:91
X509v3 extensions
subjectKeyIdentifier
  • EA:B2:AE:A3:E6:5E:B0:EF:21:C6:CE:47:16:B7:77:2E:B6:97:E8:16
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/99.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Aug 12 03:46:35.432 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:70:18:32:C6:DA:51:74:30:16:26:9E:EE:
  • 33:4F:22:16:ED:52:44:CB:79:8E:31:65:97:BA:1A:30:
  • 86:91:D5:0A:02:20:69:15:A9:4E:A6:E2:AE:4F:0D:50:
  • A7:2F:4E:54:49:73:D0:54:B4:20:43:75:E4:00:92:EC:
  • A3:04:0F:36:D6:D0
  • 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 : Aug 12 03:46:35.440 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:37:BD:4A:BB:3B:11:0D:DA:27:51:30:3E:
  • EC:0B:68:30:A9:FD:C9:4B:5E:1F:20:EE:F5:68:F8:E1:
  • 40:E0:F8:F0:02:20:1E:BB:C6:EF:AA:D0:6D:33:CF:5B:
  • F6:9B:73:DD:EF:B0:6C:73:38:DE:E3:CF:EE:40:F7:EC:
  • 1D:45:26:C2:F8:62