SSL-Tools

SSL check results of progressdesign.pro

NEW You can also bulk check multiple servers.

Discover if the mail servers for progressdesign.pro 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, 05 Nov 2024 08:52:53 +0000

The mailservers of progressdesign.pro can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @progressdesign.pro addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.progressdesign.pro
62.109.22.10
 10
supported
progressdesign.pro
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=progressdesign.pro

Certificate chain
  • progressdesign.pro
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • progressdesign.pro
Alternative Names
  • mail.progressdesign.pro
  • progressdesign.pro
  • smtp.progressdesign.pro
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-11-04
Not valid after
2025-02-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F5:61:C3:D5:E8:0B:BE:66:47:F1:47:37:53:10:3A:93:E9:AE:27:11:E0:77:DD:23:4D:82:DC:A3:6F:D2:41:CC
SHA1
E1:38:50:CA:E8:AF:DA:F4:B6:62:C1:F1:2C:68:5C:67:0B:E2:D0:1F
X509v3 extensions
subjectKeyIdentifier
  • 2C:6E:71:93:47:9C:61:B0:20:CF:94:A8:F9:A2:3D:99:AF:2E:45:7D
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 : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Nov 4 15:51:08.130 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FC:68:F4:1C:FB:1E:6C:64:95:06:F5:
  • FC:7F:92:AA:AE:66:F6:5A:70:CD:6D:AF:F0:88:9C:9E:
  • 6E:BF:E6:52:88:02:20:49:DD:27:B6:FB:32:F7:12:7A:
  • FB:CC:EC:36:9C:1E:26:99:62:64:51:57:6D:57:57:86:
  • F5:9E:D3:86:7F:A3:A1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Nov 4 15:51:08.251 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:68:15:92:2E:9A:C3:A7:FF:26:79:6A:EB:
  • 7B:DB:86:13:E5:77:E5:A8:12:47:FD:B5:D1:FC:F1:6C:
  • 3F:A0:57:5C:02:20:5E:87:8A:CB:49:47:64:B3:DD:3A:
  • EB:1B:B8:80:14:58:AF:8C:96:78:F8:28:66:AE:41:45:
  • 3D:D2:0E:83:73:05