SSL-Tools

SSL check results of systechmedical.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for systechmedical.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 Mon, 20 Nov 2023 21:15:58 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.systechmedical.com.br
177.85.99.55
 10
supported
ftp.systechmedical.com.br
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=ftp.systechmedical.com.br

Certificate chain
  • ftp.systechmedical.com.br
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • ftp.systechmedical.com.br
Alternative Names
  • ftp.systechmedical.com.br
  • mail.systechmedical.com.br
  • pop.systechmedical.com.br
  • smtp.systechmedical.com.br
  • systechmedical.com.br
  • www.systechmedical.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-09-26
Not valid after
2023-12-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5B:E7:EE:9F:88:9B:7A:DE:7B:4F:38:54:EF:8F:63:BC:3A:BB:55:50:D1:B4:B7:75:F8:D3:54:CF:08:76:66:DF
SHA1
A4:E8:B1:39:6E:73:F9:A8:D7:12:AC:D9:D6:97:4A:38:B9:85:68:BE
X509v3 extensions
subjectKeyIdentifier
  • 65:6B:1A:D3:28:E4:A2:72:07:D3:8E:AE:75:91:6B:7E:A1:EE:79:D6
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 : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Sep 26 06:26:06.879 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DA:F4:9E:AD:BE:75:ED:8A:34:F7:B8:
  • BE:17:A7:2B:6C:00:99:64:5D:DB:57:C0:59:E8:3E:80:
  • A3:42:14:0D:43:02:20:63:A9:0C:42:EC:6B:AF:89:A3:
  • F5:B2:C2:6A:24:6E:EE:91:68:83:FF:B8:DC:3A:A1:BC:
  • 8A:9C:80:43:15:0A:08
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
  • 03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
  • Timestamp : Sep 26 06:26:06.880 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:63:A2:92:86:99:36:AF:03:BF:AF:78:F6:
  • 47:F9:EA:B5:F0:B3:B8:CC:7E:CA:7A:F5:2F:5F:8A:87:
  • 0B:29:F4:A0:02:20:7C:69:A5:0B:B6:D2:35:D7:C7:6C:
  • 31:03:C7:D6:B5:81:0F:D9:1D:E4:E4:37:34:C1:A6:7A:
  • 9A:C2:9B:AB:EC:07