SSL check results of bpx.com.mx

NEW You can also bulk check multiple servers.

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

Report created Wed, 14 Apr 2021 08:14:10 +0000

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

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

/mailservers/bpx.com.mx

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
bpx.com.mx
2806:107e:18:2455:94f2:bc28:a8bc:c678
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
bpx.com.mx
2806:107e:18:2455:e58e:f567:27:fdfb
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
bpx.com.mx
189.146.159.15
10
supported
bpx.com.mx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s
bpx.com.mx
189.146.159.15
10
supported
bpx.com.mx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=bpx.com.mx

Certificate chain
  • bpx.com.mx
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
    • Unknown Authority

      R3
Subject
Common Name (CN)
  • bpx.com.mx
Alternative Names
  • *.bluephoenix.com.mx
  • *.bpx.com.mx
  • *.bpxradio.me
  • bluephoenix.com.mx
  • bpx.com.mx
  • bpxradio.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-14
Not valid after
2021-07-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
04:CB:90:A0:CE:C2:3B:E2:20:51:29:86:AF:0D:3D:A7:86:E6:B4:BE:02:2F:B6:8A:62:AC:95:31:75:9B:96:EF
SHA1
CA:F5:F7:19:26:44:A6:B8:90:02:E1:E1:8F:DE:26:A4:C5:54:CC:84
X509v3 extensions
subjectKeyIdentifier
  • E9:D8:01:61:E0:52:D2:0A:F2:4C:4C:77:71:B5:20:E3:89:D4:9E:06
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Apr 14 07:47:05.988 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5B:0B:A5:7A:6E:73:E3:CF:7D:0D:76:44:
  • 71:87:1D:5B:14:3F:29:E5:D0:9C:A1:F9:8D:FF:6F:5B:
  • D0:1C:2F:A6:02:21:00:D1:62:38:E9:2B:50:A0:7C:13:
  • 28:79:F8:B8:1C:48:30:97:CC:C2:D3:4D:DE:DA:26:5A:
  • DC:8E:CC:3F:B2:3C:4B
  • 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 : Apr 14 07:47:06.067 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FC:6E:F3:96:71:3C:5D:32:BD:79:E4:
  • 9A:94:9B:1E:3F:2C:04:57:6C:C2:5F:F5:B9:8D:3B:B7:
  • 49:37:D6:90:37:02:20:73:10:69:D4:5F:7A:82:F1:38:
  • A1:4E:90:C2:F2:03:1D:48:D2:E0:9F:4A:B6:BD:E5:6D:
  • 72:9D:AD:2D:54:FD:E2
tlsfeature
  • status_request