SSL-Tools

SSL check results of acoglobal.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for acoglobal.com.br 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, 25 Mar 2025 19:07:16 +0000

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

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

/mailservers/acoglobal.com.br

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.evolutionweb.com.br
194.87.164.6
 1
supported
gateway.idc2br.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s
mx2.evolutionweb.com.br
51.89.195.180
Results incomplete
5 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx3.evolutionweb.com.br
194.87.164.28
 10
supported
gateway.idc2br.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s

Outgoing Mails

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

Certificates

First seen at:

CN=gateway.idc2br.com

Certificate chain
  • gateway.idc2br.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • gateway.idc2br.com
Alternative Names
  • gateway.idc2br.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-02-01
Not valid after
2025-05-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
22:4A:26:3F:40:B8:E2:34:83:8A:C6:FA:7D:B8:99:E7:ED:60:9B:38:9B:F7:8D:62:2C:5D:C2:CD:7A:38:B5:BE
SHA1
3A:80:68:A0:78:B5:F8:E8:80:84:51:19:90:D8:B4:8E:C0:0A:20:F3
X509v3 extensions
subjectKeyIdentifier
  • 83:EB:58:87:BC:87:56:E4:53:7A:18:86:35:1B:B9:35:85:34:B8:A2
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 : 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 : Feb 1 07:52:07.119 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EA:70:57:6E:4E:0D:78:62:53:F7:EA:
  • C4:2E:95:63:C7:B5:ED:20:A5:FE:7C:AE:84:90:C6:C1:
  • A6:A3:6E:E7:23:02:21:00:F8:2E:09:7A:48:30:71:BE:
  • 25:67:95:A0:18:64:96:EA:4E:29:7C:52:C8:B6:99:2E:
  • 4F:F7:E0:D6:ED:A8:EF:FA
  • 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 : Feb 1 07:52:07.122 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FB:CB:CF:0B:40:71:F0:16:FD:B6:0E:
  • BC:B4:18:28:02:F7:4D:47:4E:78:77:E8:44:C7:65:21:
  • 12:FE:3D:92:B9:02:20:35:8F:0D:A6:4F:58:37:F0:6E:
  • C0:D5:66:F0:9E:28:F4:98:00:36:F4:F4:69:4C:36:F7:
  • 79:DA:88:A4:EE:9A:52