SSL-Tools

SSL check results of rzladvocacia.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for rzladvocacia.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 16:31:42 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
rzladvocacia.com.br
2804:3744:0:202::2
 0
supported
*.rzladvocacia.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
rzladvocacia.com.br
45.224.128.202
 0
supported
*.rzladvocacia.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.rzladvocacia.com.br

Certificate chain
  • *.rzladvocacia.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)
  • *.rzladvocacia.com.br
Alternative Names
  • *.rzladvocacia.com.br
  • rzladvocacia.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-03-07
Not valid after
2025-06-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6A:E6:2C:FD:C0:4C:72:0B:CC:4D:94:D9:46:B2:B8:2D:06:7F:D4:52:73:63:81:C3:91:BD:7A:92:E3:E9:97:94
SHA1
51:3F:F4:01:B8:CA:39:A7:EE:00:93:17:1C:37:13:96:0C:20:9A:CA
X509v3 extensions
subjectKeyIdentifier
  • C5:EC:02:B9:97:9A:47:E5:3C:84:15:57:2B:8E:E3:E0:6B:4D:AE:91
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 : 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 : Mar 7 02:19:17.799 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C3:B3:C3:C7:2A:74:09:4B:1C:37:05:
  • 46:6C:CB:F1:44:F9:1C:3F:E8:52:60:CE:90:3C:5A:16:
  • 54:8A:B9:E3:5F:02:21:00:FE:2B:65:3F:7F:54:0A:E8:
  • BA:32:64:10:9F:6B:42:5E:99:DF:67:32:6C:9F:16:94:
  • AD:5B:39:B8:00:AC:FC:D2
  • 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 : Mar 7 02:19:17.987 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:52:8A:18:D4:57:A3:B2:D8:2A:14:0A:94:
  • 1B:85:8F:82:EC:56:47:49:E9:D9:26:03:34:6D:08:F6:
  • 7C:37:25:A9:02:21:00:FD:91:EB:FE:61:6C:4A:77:D3:
  • 3E:92:81:00:7F:05:51:22:B4:01:7A:11:4C:7A:4C:6F:
  • 09:49:88:DB:7C:7C:3D