SSL-Tools

SSL check results of alphamedhospitalar.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for alphamedhospitalar.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 Fri, 24 May 2024 09:03:20 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=*.alphamedhospitalar.com.br

Certificate chain
  • *.alphamedhospitalar.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)
  • *.alphamedhospitalar.com.br
Alternative Names
  • *.alphamedhospitalar.com.br
  • alphamedhospitalar.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-31
Not valid after
2024-06-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AA:8B:07:25:39:85:B4:7E:99:50:78:C4:E8:8F:9A:1F:3D:F3:C2:ED:3E:06:06:2C:A3:2A:90:F6:4A:20:F2:5D
SHA1
2E:8B:43:7D:89:C8:B6:73:93:BB:2B:83:5F:72:50:AA:9A:78:65:1F
X509v3 extensions
subjectKeyIdentifier
  • 3A:4E:83:AA:1B:1B:15:05:9F:EC:A8:2F:7C:17:24:4A:C6:C8:27:5B
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 31 04:59:09.019 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C8:11:CB:FA:34:D4:AA:FB:F9:D0:91:
  • FB:85:94:B2:69:0F:C7:F4:E6:03:90:4D:FE:64:31:E1:
  • FD:04:8A:72:5A:02:21:00:E7:FB:DC:8E:E2:FA:95:D5:
  • 13:71:DB:51:9F:18:E6:F8:EC:BB:7C:9D:E1:97:FB:4D:
  • A7:89:99:32:74:9C:92:65
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 31 04:59:09.055 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:62:89:82:70:D1:5C:1A:69:36:67:47:C0:
  • 86:D3:E5:1C:BD:9A:32:05:76:CB:8E:F7:CD:A8:F8:E9:
  • 60:FC:92:06:02:21:00:9C:BA:41:48:18:16:74:62:68:
  • 65:25:A4:B6:A6:C4:B2:CF:4A:5B:1C:6D:DB:21:3C:77:
  • DC:1F:E4:6A:03:18:70