SSL-Tools

SSL check results of itechsolutions.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for itechsolutions.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, 27 Jan 2025 01:30:30 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=*.itechsolutions.com.br

Certificate chain
  • *.itechsolutions.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)
  • *.itechsolutions.com.br
Alternative Names
  • *.itechsolutions.com.br
  • itechsolutions.com.br
  • www.loja.itechsolutions.com.br
  • www.noc.itechsolutions.com.br
  • www.noc3.itechsolutions.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-01
Not valid after
2025-04-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AB:01:28:26:9F:6E:BA:A7:48:CC:3F:F8:1E:66:E9:50:70:E0:2E:5C:0E:98:BD:7D:AF:57:90:DE:F6:27:82:82
SHA1
78:BD:C1:C4:43:AA:BD:00:DB:2A:4E:93:62:80:BF:02:FD:11:55:8B
X509v3 extensions
subjectKeyIdentifier
  • 24:22:96:EA:EF:A4:0C:FE:11:16:84:89:CD:AF:C9:98:C5:77:E8:B2
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 1 21:10:16.581 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:18:0B:E6:1C:3A:59:AD:37:A8:5A:8A:6D:
  • B9:E5:AE:AF:8F:6A:84:2A:A3:F0:B5:79:02:8D:CD:E1:
  • EA:6D:BE:8F:02:21:00:BD:1D:55:C5:EE:F9:15:E6:E5:
  • 6B:D1:53:8D:C3:4D:BB:B0:88:9A:46:9C:B3:65:9E:AE:
  • 28:D7:CF:03:06:68:A1
  • 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 : Jan 1 21:10:16.592 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BE:BC:FC:0E:B3:2C:85:6F:B8:55:9F:
  • BC:3B:47:CE:23:32:EB:35:19:1B:EB:87:BF:7D:B9:B9:
  • BE:0C:77:01:FD:02:20:66:0B:69:12:AF:57:F5:DC:FD:
  • 12:D9:28:CA:88:D8:A2:3B:77:70:9C:66:D2:7E:7B:44:
  • CD:FF:4E:5F:9E:F1:C9