SSL-Tools

SSL check results of bicotech.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for bicotech.com 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 Wed, 17 Apr 2024 18:22:07 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.bicotech.com
50.87.195.203
 0
supported
cpcontacts.bicotech.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
45 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpcontacts.bicotech.com

Certificate chain
  • cpcontacts.bicotech.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • cpcontacts.bicotech.com
Alternative Names
  • autodiscover.bicotech.com
  • bicotech.com
  • cpanel.bicotech.com
  • cpcalendars.bicotech.com
  • cpcontacts.bicotech.com
  • mail.bicotech.com
  • webdisk.bicotech.com
  • webmail.bicotech.com
  • www.bicotech.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-16
Not valid after
2024-06-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
21:73:03:46:EB:68:69:E1:E5:C1:F2:81:2D:CF:1A:ED:EC:E0:5F:B4:2F:22:88:99:0D:4F:5A:28:AE:4D:84:3C
SHA1
69:66:21:43:60:FF:8E:80:66:52:93:4E:11:8E:B4:ED:4C:E2:E3:78
X509v3 extensions
subjectKeyIdentifier
  • F0:3A:26:90:18:C1:87:24:0B:2D:6B:4F:A4:EC:DB:E8:52:BC:4F:4A
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 16 02:01:27.048 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:95:59:E9:CE:59:D7:99:0F:92:36:05:
  • FA:78:FA:4C:C0:9C:8B:B2:6A:44:41:45:3F:FF:00:F8:
  • 8D:26:13:7F:04:02:20:14:C2:BB:98:1E:F4:D6:B1:57:
  • 7A:80:11:6B:CE:2D:29:47:73:51:96:87:B0:E9:8D:A2:
  • 24:65:F9:D4:82:4C:B7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Mar 16 02:01:27.071 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B8:94:B4:BF:6B:47:BF:9A:F5:FF:B5:
  • E8:42:2A:C4:96:B1:A0:A7:1E:9A:B6:90:AD:45:43:D5:
  • B8:87:81:EC:95:02:20:24:05:64:C9:C6:B6:CE:B8:EC:
  • 20:CA:D1:38:AF:3A:B0:DB:AB:ED:81:90:9F:A7:43:D5:
  • 0B:29:69:A4:16:EE:6F