SSL-Tools

SSL check results of autopecasparana.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for autopecasparana.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 21:13:14 +0000

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

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

/mailservers/autopecasparana.com.br

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx120.comquatro.com.br
189.90.130.245
 10
supported
email-gateway2.com4.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
10 s
mx121.comquatro.com.br
189.90.130.244
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=email-gateway2.com4.com.br

Certificate chain
Subject
Common Name (CN)
  • email-gateway2.com4.com.br
Alternative Names
  • email-gateway2.com4.com.br
Issuer
Country (C)
  • US
Organization (O)
  • (STAGING) Let's Encrypt
Common Name (CN)
  • (STAGING) Wannabe Watercress R11
validity period
Not valid before
2025-02-11
Not valid after
2025-05-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E5:D9:D6:A8:AF:31:33:B0:22:5B:9B:A2:E5:DA:9D:A8:57:DB:35:E2:E0:A4:2E:46:EA:20:63:7E:5A:C9:C0:24
SHA1
02:33:98:1B:F7:41:5B:5D:5F:1B:73:4F:39:36:85:93:9F:85:5C:13
X509v3 extensions
subjectKeyIdentifier
  • 1E:CE:C1:E1:49:89:A6:AC:F0:6E:6A:7C:78:7D:C6:9A:17:BD:04:B2
authorityKeyIdentifier
  • keyid:13:CB:D7:F6:AE:9D:FC:69:42:64:D6:5C:7C:23:CC:85:F9:47:C7:B6
authorityInfoAccess
  • OCSP - URI:http://stg-r11.o.lencr.org
  • CA Issuers - URI:http://stg-r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 21:E5:1A:44:D8:B9:E7:54:0E:A7:FB:E0:BA:D7:77:36:
  • 15:60:66:84:D1:5A:EB:33:E6:45:B4:E9:55:F3:88:83
  • Timestamp : Feb 11 07:51:21.854 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8B:72:39:97:05:28:1E:E2:6C:CE:5A:
  • 38:E1:00:94:7E:21:10:84:6C:0B:E1:70:99:90:53:32:
  • D2:A6:4E:4A:54:02:20:15:C7:FB:6F:92:74:51:DF:40:
  • 45:84:1C:FD:E5:74:01:0F:6B:77:79:EF:89:47:B3:0F:
  • 7C:4D:A8:12:41:A9:00
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 16:E8:69:C1:D1:95:EA:D7:C3:F8:97:1A:E3:F0:76:01:
  • F7:8C:E1:B6:9D:31:A8:52:18:B6:83:7F:31:A8:15:08
  • Timestamp : Feb 11 07:51:21.902 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D8:C4:57:80:A2:5F:A5:EC:71:B3:CC:
  • 19:6B:53:78:41:F0:3C:79:2A:74:BD:7F:E8:B3:DB:C6:
  • 99:F3:92:FB:EC:02:20:45:ED:37:A3:EB:15:C1:CE:95:
  • E5:FC:E2:1D:9A:49:25:8D:C1:18:1F:DC:88:91:93:20:
  • F3:52:C6:EA:0D:63:4A