SSL check results of mail.breachban.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.breachban.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 Sun, 09 Aug 2026 00:30:55 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.breachban.com
51.83.132.204
-
supported
mail.breachban.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.breachban.com

Certificate chain
  • mail.breachban.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384

          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384

              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384

Subject
Common Name (CN)
  • mail.breachban.com
Alternative Names
  • mail.breachban.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-07-16
Not valid after
2026-10-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
EB:3D:87:F4:7F:01:E5:2E:DB:83:29:25:2A:3A:DE:FF:71:28:27:74:EF:CF:EA:F5:68:3D:A3:10:63:B0:46:1F
SHA1
FC:D8:D3:B5:9D:0F:8C:2C:AA:8E:03:12:C1:E3:98:AD:3D:CA:E6:C0
X509v3 extensions
subjectKeyIdentifier
  • 88:EA:82:C9:1C:82:FD:E0:DA:20:FB:E4:22:7D:3C:9F:12:0D:1A:35
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/30.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Jul 16 15:35:04.485 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C0:B8:0E:3B:CE:97:95:60:D7:30:53:
  • 68:FD:41:33:6D:1A:AA:44:72:53:DD:A4:D6:29:F9:41:
  • 36:D1:B8:BD:E1:02:21:00:84:CF:40:AC:56:61:B9:35:
  • 4B:CB:09:7D:AF:69:55:CF:1D:8F:92:FA:72:D9:D6:01:
  • 2B:D5:9D:47:6F:E6:1C:45
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Jul 16 15:35:05.363 2026 GMT
  • Extensions: 00:00:05:00:15:9F:60:B5
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AB:A8:5E:24:62:4A:8A:7A:02:55:CB:
  • B3:B6:A6:B1:D5:97:08:AE:4B:EF:96:A5:9E:52:F0:E3:
  • CB:39:A7:A3:77:02:20:47:7A:B6:12:3F:91:CA:D9:DF:
  • 96:36:4D:71:9A:76:E9:5C:4F:73:5B:01:FA:C5:92:8C:
  • EA:D2:F6:FD:DD:50:AC