SSL-Tools

SSL check results of bcdtravelmexico.com.mx

NEW You can also bulk check multiple servers.

Discover if the mail servers for bcdtravelmexico.com.mx 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 Tue, 06 Dec 2022 20:25:19 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.bcdtravelmexico.com.mx
201.134.2.51
 10
supported
bcdtravelmexico.com.mx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
19 s

Outgoing Mails

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

Certificates

First seen at:

CN=bcdtravelmexico.com.mx

Certificate chain
  • bcdtravelmexico.com.mx
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • bcdtravelmexico.com.mx
Alternative Names
  • bcdtravelmexico.com.mx
  • mail.bcdtravelmexico.com.mx
  • www.bcdtravelmexico.com.mx
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-10-21
Not valid after
2023-01-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F0:33:11:06:2F:ED:7C:0D:E2:0E:19:38:D7:B4:6F:35:1A:46:42:87:E9:A4:EC:ED:0D:7C:04:BF:C9:2C:8A:A0
SHA1
D9:E6:C3:28:DE:64:BB:1C:3C:87:33:7E:96:BB:15:12:03:D2:E7:A7
X509v3 extensions
subjectKeyIdentifier
  • 78:C5:52:4D:C5:6A:02:B4:9F:A0:D3:8E:78:A0:05:C8:C5:9A:12:B4
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 : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : Oct 21 22:32:23.088 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C5:D3:37:30:E2:77:44:3A:0B:BA:98:
  • 46:48:85:56:3C:C9:71:E0:FE:BA:D4:CC:FF:2F:84:8C:
  • DB:4D:3D:55:3D:02:21:00:8C:3D:F9:84:29:29:B7:0A:
  • 8F:A5:0B:B6:29:74:8C:23:83:39:91:74:68:6D:C1:01:
  • EE:41:8C:10:16:D5:D0:AC
  • 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 : Oct 21 22:32:23.225 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4F:DD:BE:6F:8F:DF:A2:FC:B4:FA:D7:89:
  • 99:A6:11:0F:F7:04:17:08:86:CA:71:2E:95:FF:5A:E9:
  • 95:85:84:D5:02:21:00:DE:1C:06:04:64:BE:28:E2:D5:
  • 6A:14:33:00:0F:60:6E:9A:98:0A:33:9E:A6:CC:4B:50:
  • 69:F5:3A:71:66:0D:0A