SSL-Tools

SSL check results of 4synergy.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for 4synergy.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 Thu, 28 Mar 2024 14:26:48 +0000

The mailservers of 4synergy.com can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mta02.zh01.4synergy.com
217.71.88.113
 10
supported
mta02.zh01.4synergy.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mta01.rma01.4synergy.com
62.2.185.143
 20
supported
mta01.rma01.4synergy.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @4synergy.com sender addresses. Test mail delivery

Host TLS Version & Cipher
mua01.zh01.4synergy.com (217.71.88.121)
TLSv1.2 DHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mta02.zh01.4synergy.com

Certificate chain
  • mta02.zh01.4synergy.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)
  • mta02.zh01.4synergy.com
Alternative Names
  • mta02.zh01.4synergy.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-22
Not valid after
2024-06-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C2:77:A1:F9:77:59:74:40:1B:11:16:04:38:20:96:BB:0C:E1:33:5D:53:28:4F:3F:9E:13:4A:5E:52:0F:18:5A
SHA1
62:71:85:E8:C3:B0:F5:BD:6A:2C:99:35:FE:B8:79:D3:30:19:B1:11
X509v3 extensions
subjectKeyIdentifier
  • DE:97:78:3B:76:27:A9:0B:16:32:86:17:2A:D5:6A:2E:8D:B3:5C:84
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Mar 22 13:23:47.888 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:13:9D:55:3D:FC:05:EA:BA:2B:2B:ED:FE:
  • F6:83:38:B3:53:2F:48:2E:7F:59:8A:85:6B:8E:4B:B4:
  • AC:49:4C:8D:02:21:00:BC:CD:78:B3:43:62:E5:5A:39:
  • 51:72:E6:BF:5F:9C:86:BB:6E:72:19:F8:D7:04:68:65:
  • E5:13:D1:ED:8A:35:E0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 22 13:23:49.897 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4E:3A:02:DB:FC:52:E0:F9:E4:18:D5:9C:
  • EB:2B:0B:C1:71:7E:4E:B2:43:04:F0:46:5A:E1:2F:F4:
  • A0:51:57:BA:02:20:39:85:5F:56:18:67:26:45:C1:75:
  • 20:BB:80:08:A5:8C:95:21:76:3E:0E:94:C5:C7:E7:FC:
  • 29:15:11:42:8C:64
First seen at:

CN=mta01.rma01.4synergy.com

Certificate chain
  • mta01.rma01.4synergy.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)
  • mta01.rma01.4synergy.com
Alternative Names
  • mta01.rma01.4synergy.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-04
Not valid after
2024-06-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
64:34:D5:20:86:13:92:56:4E:0F:0C:4A:08:6A:D5:12:31:FD:78:95:45:72:B9:80:0C:6D:4A:06:B6:46:80:04
SHA1
62:ED:9E:23:AD:D3:C6:A5:DA:87:7C:B3:17:22:CA:77:C5:33:30:7A
X509v3 extensions
subjectKeyIdentifier
  • 75:A6:BE:E7:03:0F:76:64:C3:0B:B8:CF:76:74:30:12:92:1E:F8:DA
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 4 12:51:02.199 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B0:15:91:5D:09:23:53:0F:C6:9C:88:
  • EF:91:09:FA:93:7C:C9:AB:D0:29:E7:EF:38:16:18:25:
  • EF:AC:B2:7C:9D:02:21:00:9F:BF:F7:FE:8E:1F:9B:4D:
  • B5:C2:FA:1A:09:6E:71:E0:9D:41:7E:72:3F:49:4D:53:
  • C8:E2:A0:14:B8:AF:F8:6C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 4 12:51:02.200 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FE:4F:46:5A:A6:87:AB:AE:59:7E:C5:
  • 22:6C:1E:CC:A6:BE:6D:45:9E:95:93:8B:14:A6:A1:2A:
  • 14:91:78:63:BF:02:21:00:DF:DB:63:F6:6F:94:FB:94:
  • EF:C3:07:00:78:18:0C:B2:28:D1:F8:58:BF:7B:F2:D6:
  • 8D:B2:97:4C:04:78:8C:EB

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mta02.zh01.4synergy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mta01.rma01.4synergy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid