SSL-Tools

SSL check results of joaonetoadvogado.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for joaonetoadvogado.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, 29 Mar 2025 08:13:46 +0000

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

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

/mailservers/joaonetoadvogado.com.br

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
joaonetoadvogado.com.br
2804:2a88:8::5
Results incomplete
0
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
joaonetoadvogado.com.br
143.208.8.5
 0
supported
*.joaonetoadvogado.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
44 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.joaonetoadvogado.com.br

Certificate chain
  • *.joaonetoadvogado.com.br
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.joaonetoadvogado.com.br
Alternative Names
  • *.joaonetoadvogado.com.br
  • joaonetoadvogado.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-28
Not valid after
2025-04-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
64:8D:4B:66:C4:37:BD:2D:E7:56:7E:C0:B1:32:C8:02:C5:76:93:E6:64:7E:6F:02:9C:32:7E:52:8A:B2:6B:3C
SHA1
5A:14:C7:CC:14:F4:98:B4:1D:7E:4F:64:D1:4D:C2:C4:17:68:06:06
X509v3 extensions
subjectKeyIdentifier
  • 4D:BB:F3:73:22:69:5F:F1:AB:90:DB:8A:70:0C:CF:07:5A:8C:F7:AE
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 : Jan 28 03:05:02.225 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E7:E8:9D:92:1F:40:70:C9:6B:9A:B4:
  • 4B:0E:BD:BD:EE:76:A8:9D:D5:4A:9B:08:56:C8:86:2E:
  • 90:05:5C:14:4C:02:20:3A:4E:8D:94:CF:68:3C:6C:B3:
  • A7:A7:04:66:EB:BB:55:01:FF:C1:B5:48:6D:82:DD:F9:
  • 34:A6:55:8C:84:62:D3
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DE:85:81:D7:50:24:7C:6B:CD:CB:AF:56:37:C5:E7:81:
  • C6:4C:E4:6E:D6:17:63:9F:8F:34:A7:26:C9:E2:BD:37
  • Timestamp : Jan 28 03:05:02.213 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:58:B1:1A:E1:BA:2C:F0:0B:4B:A3:A1:A4:
  • C7:DF:34:77:0B:D3:CE:72:A2:E5:B2:E8:A4:F0:05:E9:
  • 20:18:FC:B5:02:20:3E:CA:79:5C:27:8A:11:EE:1B:92:
  • 2C:DC:AD:8B:F9:1D:96:B5:56:B0:3C:A1:C4:2A:6A:20:
  • B5:28:61:75:3E:C0