SSL-Tools

SSL check results of robertoantonioimoveis.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for robertoantonioimoveis.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 00:54:08 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.robertoantonioimoveis.com.br
216.172.161.53
 0
supported
*.robertoantonioimoveis.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
41 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.robertoantonioimoveis.com.br

Certificate chain
  • *.robertoantonioimoveis.com.br
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.robertoantonioimoveis.com.br
Alternative Names
  • *.robertoantonioimoveis.com.br
  • robertoantonioimoveis.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-12-28
Not valid after
2022-03-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
88:74:8C:0B:17:52:1B:67:3E:95:59:72:51:B9:49:F7:2E:85:16:7F:46:ED:F2:BC:36:7C:11:E7:A8:BE:2A:CA
SHA1
CA:E2:36:23:76:F4:40:15:B5:90:7F:8F:3C:49:46:83:A5:E1:4A:96
X509v3 extensions
subjectKeyIdentifier
  • 39:98:7C:CF:EE:D4:73:9D:F9:E6:8B:BC:C3:B6:FE:14:AF:DC:C8:76
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Dec 28 17:37:55.159 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A2:42:B3:73:85:B8:E4:5C:BB:14:25:
  • C0:B1:C9:E3:3B:18:FF:47:E0:E3:B5:F2:39:2D:51:BA:
  • FB:36:84:EB:AC:02:20:2D:2C:5F:48:74:00:94:58:7C:
  • B0:D0:7A:B6:BC:29:F2:32:E3:AA:AA:FF:C7:8E:43:BE:
  • 83:D4:03:CA:26:DF:96
  • 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 : Dec 28 17:37:55.143 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:13:23:7C:85:CB:D1:2B:B6:AE:99:BC:E3:
  • 84:1E:97:CB:C8:6C:37:19:5C:AA:1A:DD:FB:BB:D0:6A:
  • 08:CF:CF:C7:02:20:35:5F:0B:C7:CE:CC:C9:1E:8F:80:
  • 94:92:E9:B2:34:D7:8A:23:18:68:61:91:E6:63:94:12:
  • 67:CA:9E:69:9E:D1