SSL-Tools

SSL check results of mercaante.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for mercaante.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 Sat, 15 Jan 2022 05:57:05 +0000

The mailservers of mercaante.com.br can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.a.locaweb.com.br
186.202.4.42
 10
supported
*.locaweb.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.0
  • SSLv3
20 s
mx.b.locaweb.com.br
177.153.23.242
 10
supported
*.locaweb.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
11 s
mx.jk.locaweb.com.br
200.234.204.130
 20
supported
*.locaweb.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
10 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.locaweb.com.br

Certificate chain
Subject
Common Name (CN)
  • *.locaweb.com.br
Alternative Names
  • *.locaweb.com.br
  • locaweb.com.br
Issuer
Country (C)
  • BE
Organization (O)
  • GlobalSign nv-sa
Common Name (CN)
  • AlphaSSL CA - SHA256 - G2
validity period
Not valid before
2021-01-15
Not valid after
2022-02-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3D:46:C8:7A:BC:D2:DF:C2:E6:C5:A2:3F:6D:B8:F0:7B:7E:49:47:2E:9E:90:DC:01:48:4D:20:C1:50:61:02:8E
SHA1
57:0D:72:D3:A6:9D:21:E4:77:F7:A4:B2:50:00:ED:F8:32:32:D9:0F
X509v3 extensions
authorityInfoAccess
  • CA Issuers - URI:http://secure2.alphassl.com/cacert/gsalphasha2g2r1.crt
  • OCSP - URI:http://ocsp2.globalsign.com/gsalphasha2g2
certificatePolicies
  • Policy: 1.3.6.1.4.1.4146.1.10.10
  • CPS: https://www.globalsign.com/repository/
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://crl2.alphassl.com/gs/gsalphasha2g2.crl
authorityKeyIdentifier
  • keyid:F5:CD:D5:3C:08:50:F9:6A:4F:3A:B7:97:DA:56:83:E6:69:D2:68:F7
subjectKeyIdentifier
  • B7:ED:00:F5:A8:3F:37:61:68:0D:66:15:1E:D3:79:7E:13:1B:E4:F5
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Jan 15 18:36:24.510 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:CF:F9:11:C8:BF:97:38:6B:09:DB:0A:
  • 10:7E:F6:80:0E:0A:E9:83:E7:CA:7F:34:8E:6D:F1:43:
  • F3:23:5D:C1:DB:02:20:68:98:88:F4:CB:CB:D1:0F:46:
  • 24:45:79:E5:C4:4A:DB:EC:76:15:3D:1A:88:D2:55:01:
  • 24:B6:21:B3:03:11:0B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
  • C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
  • Timestamp : Jan 15 18:36:24.546 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C0:8B:1A:D4:2F:C5:57:03:85:65:D3:
  • 4B:08:DC:36:F1:6F:B4:EB:84:67:C4:C3:B4:B1:68:02:
  • 33:E5:32:F8:95:02:21:00:D3:ED:3A:09:06:92:63:9B:
  • 32:89:7B:15:58:EF:C8:64:8F:77:8D:E0:B2:B3:F5:94:
  • 6D:3A:DA:54:34:A8:06:9D