SSL check results of mail.zbcair.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.zbcair.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

Report created Sat, 08 May 2021 02:33:20 +0000

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

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

/mailservers/mail.zbcair.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.zbcair.com
172.104.68.86
-
supported
*.zbcair.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
20 s
mail.zbcair.com
2400:8902::f03c:92ff:fe7d:cd91
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.zbcair.com

Certificate chain
  • *.zbcair.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Expired

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • *.zbcair.com
Alternative Names
  • *.zbcair.com
  • zbcair.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-26
Not valid after
2021-04-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
75:91:0E:B0:A4:F0:32:AC:5D:00:B6:20:8A:29:FC:34:89:47:95:9A:DC:6C:EE:4A:DB:AD:94:92:3F:0E:76:95
SHA1
10:D2:86:60:13:1F:8F:EF:40:EF:14:FF:3F:2C:35:A0:9C:8B:A8:EC
X509v3 extensions
subjectKeyIdentifier
  • D9:11:8C:1D:5A:AC:02:35:D3:1A:7C:76:45:91:FB:C7:26:64:87:77
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Jan 26 09:42:43.568 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FA:2A:0D:42:AA:26:F7:55:70:85:C4:
  • 56:C3:AE:9E:5B:74:6E:4E:C9:E1:A6:33:B4:00:75:31:
  • DD:3B:FF:0C:7E:02:20:44:6E:98:82:6B:3C:E7:AB:8D:
  • 1D:0E:89:71:CF:F1:4B:3A:C0:5B:FB:F9:7B:DE:08:ED:
  • 55:B8:AA:FD:5A:DD:CF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jan 26 09:42:43.912 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1F:27:E1:76:61:6F:DA:5A:E4:BE:C4:A7:
  • 62:8D:37:92:96:E4:18:FD:42:C1:52:68:5F:21:A2:01:
  • 99:B8:82:E8:02:21:00:BF:70:3E:B3:4C:A3:26:61:86:
  • 65:43:D6:78:97:74:A9:DA:41:54:14:B4:B0:FF:3E:69:
  • F0:56:9D:D4:41:9D:D8