SSL-Tools

SSL check results of ibdchina.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for ibdchina.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 Sat, 20 Apr 2024 08:07:39 +0000

We can not guarantee a secure connection to the mailservers of ibdchina.com!

Please contact the operator of ibdchina.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/ibdchina.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ibdchina.com
221.4.210.19
Results incomplete
5
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail2.ibdchina.com
169.62.93.69
 15
supported
mail2.ibdchina.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_ECDSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail2.ibdchina.com

Certificate chain
  • mail2.ibdchina.com
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail2.ibdchina.com
Alternative Names
  • mail2.ibdchina.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-19
Not valid after
2024-06-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
64:83:00:AE:3D:D0:5A:BB:E2:49:1C:00:31:4A:95:D2:80:CA:55:0E:C0:38:5B:AF:59:03:EF:73:D3:2D:0E:0C
SHA1
BF:46:95:DD:28:D4:8B:0D:7F:16:19:25:02:E5:0C:90:66:1B:D3:F4
X509v3 extensions
subjectKeyIdentifier
  • CD:C9:E5:30:1E:9D:2F:29:2F:C8:48:E0:84:9A:E6:CF:F8:BA:6F:AE
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 : 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 19 02:22:19.247 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:08:4D:01:C5:40:EF:A0:67:47:9C:C5:67:
  • 59:F5:1E:09:6B:EE:C2:38:28:14:B2:FE:C8:EC:24:CD:
  • 1F:02:BD:AB:02:20:56:78:E7:98:CD:C0:D0:25:C1:7D:
  • 69:1F:FB:A3:AD:E3:20:4F:E8:8B:5B:01:3C:44:1E:28:
  • D0:E8:41:BA:D9:DD
  • 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 19 02:22:19.264 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E6:FF:FF:AC:F8:34:8C:BC:FE:45:58:
  • CA:3C:D2:C8:3D:D3:DE:BE:F5:D3:D6:70:37:6A:B8:8A:
  • 34:08:01:F2:B4:02:21:00:87:73:04:04:44:28:47:A7:
  • 31:A6:0D:3D:2E:41:6D:A2:23:9D:D7:D6:62:6F:12:FD:
  • 0F:D9:F8:47:BA:2C:33:15