SSL check results of unihostbrasil.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for unihostbrasil.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 Tue, 10 Jun 2025 16:39:12 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.unihostbrasil.com.br
2604:4500:0:4e::6
10
supported
*.unihostbrasil.com.br
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
10 s
mail.unihostbrasil.com.br
96.31.65.182
10
supported
*.unihostbrasil.com.br
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.unihostbrasil.com.br

Certificate chain
  • *.unihostbrasil.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)
  • *.unihostbrasil.com.br
Alternative Names
  • *.unihostbrasil.com.br
  • unihostbrasil.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-09
Not valid after
2025-09-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:D7:A4:40:07:37:CB:51:DC:F7:0E:7F:40:43:8A:B0:0D:EB:DD:F5:FE:A2:CA:6A:A7:0E:9B:BA:0B:80:71:D5
SHA1
0E:6D:B7:5D:27:D8:59:17:6B:A0:20:97:44:95:D3:53:90:77:0D:4A
X509v3 extensions
subjectKeyIdentifier
  • 3E:4E:63:B8:36:03:29:57:F4:3C:34:18:3D:28:89:6C:3A:94:A8:BA
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/72.crl
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 : Jun 9 18:28:20.291 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6D:1B:86:A5:03:3B:D5:FC:15:9D:96:B4:
  • 59:4C:8F:21:2A:11:3E:C4:DD:CA:51:DE:C7:A6:BC:D6:
  • 77:B7:37:59:02:21:00:FD:93:D7:0B:72:EC:D4:CB:A8:
  • 27:B0:E9:A9:93:21:07:69:E5:0A:1D:CE:72:7D:DB:35:
  • 59:B6:9D:B8:B2:81:F4
  • 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 : Jun 9 18:28:26.265 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3F:9D:0A:33:B7:32:DA:4A:18:6B:B4:43:
  • 09:29:2B:41:10:7A:25:D1:41:9A:35:D0:7E:01:5A:2C:
  • FC:46:04:03:02:20:60:47:7F:D5:C1:BB:76:2E:33:EE:
  • 97:99:6F:9C:CD:80:83:7F:9B:39:4E:E0:49:0D:B5:6E:
  • 61:4E:DC:34:72:E9

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.unihostbrasil.com.br
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mail.unihostbrasil.com.br
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid