SSL check results of broketto.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for broketto.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

Report created Sat, 15 Jan 2022 01:13:34 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.broketto.com.br
192.185.213.65
0
supported
cpcalendars.broketto.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
43 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpcalendars.broketto.com.br

Certificate chain
  • cpcalendars.broketto.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)
  • cpcalendars.broketto.com.br
Alternative Names
  • autodiscover.broketto.com.br
  • cpanel.broketto.com.br
  • cpcalendars.broketto.com.br
  • cpcontacts.broketto.com.br
  • mail.broketto.com.br
  • webdisk.broketto.com.br
  • webmail.broketto.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-12-23
Not valid after
2022-03-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
05:A6:C4:0B:8E:E4:A6:38:05:3C:0A:42:DC:FC:2F:B2:66:D4:E7:BC:43:A2:64:72:A2:3A:98:AE:51:FB:97:FC
SHA1
FB:E0:FB:A7:4D:22:25:62:C8:BB:EB:3E:57:44:5D:5F:7E:06:C9:44
X509v3 extensions
subjectKeyIdentifier
  • 5B:AE:98:58:1C:3C:A9:F9:C0:CB:CC:BB:C9:3B:DA:1F:8A:F1:E0:08
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 23 18:15:36.678 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:32:93:66:CA:48:3A:B3:38:DF:A1:64:82:
  • A9:C5:F7:BD:D2:39:F3:A5:D1:DA:36:B8:AF:8F:7B:E4:
  • 05:01:BB:07:02:20:00:C6:2A:AA:B4:85:E5:DD:B4:FA:
  • 36:30:C7:1F:3A:CB:0A:E9:65:03:C5:C6:39:84:D7:F5:
  • 6E:82:30:43:DD:5D
  • 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 23 18:15:36.665 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:76:FF:B9:2E:F3:4F:AD:64:00:AF:DE:69:
  • C8:5F:23:F6:5A:8B:32:57:3D:CF:28:CA:29:C4:EB:41:
  • 81:FC:75:FC:02:21:00:A8:7D:CA:7C:E8:3A:79:56:81:
  • 18:5F:E8:B4:0F:CD:51:78:9C:CC:9A:59:9A:FA:BF:87:
  • 14:86:63:0E:51:B1:A8