SSL-Tools

SSL check results of bnb-infosec.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for bnb-infosec.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 Fri, 25 Jul 2025 18:01:12 +0000

The mailservers of bnb-infosec.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @bnb-infosec.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.bnb-infosec.com
2003:a:474:7c00::5
 10
supported
mail.bnb-infosec.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mail.bnb-infosec.com
217.91.116.240
 10
supported
mail.bnb-infosec.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.bnb-infosec.com

Certificate chain
  • mail.bnb-infosec.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.bnb-infosec.com
Alternative Names
  • autoconfig.bnb-infosec.com
  • autodiscover.bnb-infosec.com
  • imap.bnb-infosec.com
  • mail.bnb-infosec.com
  • mta-sts.bnb-infosec.com
  • pop3.bnb-infosec.com
  • smtp.bnb-infosec.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-06-05
Not valid after
2025-09-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:36:75:8C:D5:DC:31:BD:5A:44:AE:B8:2B:4A:42:5D:79:EA:F7:BA:C9:73:2B:F5:E9:59:B9:39:4D:1D:50:09
SHA1
D2:D9:56:4C:0C:7D:F6:1D:93:EE:DE:84:34:C0:CA:78:D8:02:6A:31
X509v3 extensions
subjectKeyIdentifier
  • A4:C3:26:87:EC:28:1C:F6:15:E6:D1:E6:68:A7:94:76:3D:C5:1E:A0
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/95.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 : Jun 5 22:03:56.692 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D8:0D:BA:3A:86:5F:61:06:80:69:1F:
  • D1:7D:D3:F0:08:C7:32:68:30:E7:FE:79:80:77:52:F7:
  • 3A:32:F2:89:CD:02:20:00:DA:39:92:AF:9F:DF:3B:D6:
  • 90:3E:DC:24:8C:3D:A2:73:07:68:0A:74:DD:0F:CF:25:
  • 47:CD:C6:0E:5E:EF:47
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Jun 5 22:03:58.767 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FC:9B:39:73:9C:2C:1A:43:6B:69:29:
  • F3:2E:63:6A:72:7E:6B:9D:83:C3:F1:9D:84:A1:4A:77:
  • AD:16:12:F1:F3:02:20:1C:14:BF:C4:FD:4D:28:CC:56:
  • 60:3E:AA:C1:B1:80:68:99:53:70:22:3C:75:75:A2:B7:
  • 3B:4C:39:5C:6B:24:4E