SSL-Tools

SSL check results of mail.bzphost.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.bzphost.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, 09 Jul 2025 00:30:13 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.bzphost.com
191.9.123.202
 -
supported
mail.bzphost.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
14 s
mail.bzphost.com
2804:7f0:b84e:b000:59fc:218f:d79d:df87
 -
supported
mail.bzphost.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
17 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.bzphost.com

Certificate chain
  • mail.bzphost.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.bzphost.com
Alternative Names
  • mail.bzphost.com
  • webmail.bzphost.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-07-08
Not valid after
2025-10-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B1:BC:48:42:63:1B:24:00:5E:07:BB:71:33:5E:C9:24:08:53:12:C2:70:44:07:A8:23:10:EA:14:1E:A3:70:0F
SHA1
5B:73:6B:27:56:D7:B2:BA:51:3C:73:9B:36:C6:EB:A6:72:47:0C:19
X509v3 extensions
subjectKeyIdentifier
  • 7E:F9:F2:2E:21:41:D0:98:6B:08:2F:F1:96:59:2D:AB:8F:9D:F8:0B
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/84.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jul 8 13:41:00.780 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:93:A9:83:05:E1:0C:92:FD:CC:73:86:
  • 40:D7:C6:E4:25:08:DA:61:75:29:E5:8F:75:67:B3:69:
  • BB:AE:CD:80:0B:02:21:00:A3:FB:82:8F:46:DF:8B:87:
  • 01:9A:28:36:38:DE:36:19:BA:7A:5B:1D:71:66:9E:DD:
  • 26:15:11:67:62:05:0C:19
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jul 8 13:41:02.801 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:41:A9:57:1F:B4:D5:FE:E1:ED:D4:F1:2B:
  • 6D:E6:CB:A0:34:38:2F:0A:06:F4:E3:4C:8D:02:99:DE:
  • DB:04:1A:14:02:20:19:1E:01:05:32:18:6E:D9:AE:0A:
  • BE:AA:9E:57:1F:F8:AE:66:85:CA:10:0E:DD:09:08:24:
  • 3E:E7:F5:AF:8C:FB