SSL-Tools

SSL check results of mail.solvesecuritizadora.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.solvesecuritizadora.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 Fri, 18 Apr 2025 00:30:29 +0000

The mailservers of mail.solvesecuritizadora.com.br can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.solvesecuritizadora.com.br
201.47.1.170
 -
supported
mail.solvesecuritizadora.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
23 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.solvesecuritizadora.com.br

Certificate chain
  • mail.solvesecuritizadora.com.br
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.solvesecuritizadora.com.br
Alternative Names
  • mail.solvesecuritizadora.com.br
  • solvesecuritizadora.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-04-15
Not valid after
2025-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
69:96:6B:07:A2:7E:70:96:5B:A4:FC:A0:DA:39:06:7C:6D:8D:70:3D:32:08:12:19:85:3C:BC:25:E1:9C:72:70
SHA1
B4:69:86:F3:6F:3D:58:38:5D:35:ED:9A:0F:F3:73:69:D5:CD:F2:38
X509v3 extensions
subjectKeyIdentifier
  • EE:1B:BF:CE:81:0E:FD:88:5D:FF:07:70:90:24:26:53:CB:63:25:0E
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/103.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Apr 15 11:39:36.613 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:34:45:16:18:6B:90:37:8B:2F:10:23:CD:
  • 53:F0:28:7A:73:EA:78:E0:C4:E6:C5:49:0C:E6:0C:84:
  • 2F:28:76:AF:02:20:47:35:B1:1F:AA:89:88:12:A1:E0:
  • 6B:EC:6C:A1:D6:22:CF:87:2D:82:8C:A2:51:F1:08:80:
  • 77:DF:28:63:DB:7D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Apr 15 11:39:36.643 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D2:02:5D:51:8E:F0:89:B6:03:46:2D:
  • 7A:F3:FE:D5:8D:4E:9C:D8:D4:3A:B9:68:EE:D6:87:A4:
  • C7:78:21:3A:C6:02:20:50:9E:92:A2:0F:74:9C:3B:85:
  • 55:7E:7C:14:95:7D:8D:8A:06:59:1B:5F:50:76:52:FA:
  • D9:1E:DE:7A:6F:8E:B9