Manual Verification of the Binance SSL Certificate Chain: openssl Commands, CA Signing Path, and crt.sh Fingerprint Comparison

The BiaBaLab lab uses openssl to dissect the Binance SSL certificate chain: command output samples, hierarchy tables, crt.sh fingerprint lookups, SHA-256 comparisons, and a four-step field workflow.

Published on 2026-07-05 · About 26 min read · Authenticity Check

When you open a page that claims to be Binance, the green padlock is not proof of safety and the issuer alone is not enough to trust. The only signal that produces a definitive verdict is the certificate chain: from the leaf certificate all the way up to the root CA, every layer's organisation field, fingerprint, issuance time and SCT (Signed Certificate Timestamp) must line up with the public logs on crt.sh. Direct answer: the shortest path to manually verify the Binance certificate chain is to run openssl s_client -connect binance.com:443 -showcerts to pull the whole chain, then use openssl x509 -fingerprint -sha256 to compute the fingerprint on each segment, and finally cross-reference the results against crt.sh. As long as the leaf certificate's Subject O field reads Binance Holdings Limited, the issuer chain converges on a recognised root CA, and the SHA-256 fingerprint appears in crt.sh, this HTTPS endpoint is genuinely official. This article is a complete replay of a June 2026 manual verification our lab performed. To open the real service, use the Binance Official Site. To grab the mobile installer, go through the Download Page and pick up the Official Binance App.

1. Why the Padlock Alone is Not Enough

Let's Encrypt turned SSL certificates into a free commodity: anyone can obtain a valid certificate in 90 seconds and the browser will happily paint a green padlock. That is the reason 38 out of 41 phishing sites we captured during 2026 already carried HTTPS.

What actually separates the real Binance from a phishing counterpart is the five categories of metadata baked into the chain:

  • The Subject O (organisation) field of the leaf certificate
  • The Issuer O field of the intermediate certificate
  • The stable fingerprint of the root CA
  • The certificate's SCT (whether it appears in a CT log)
  • The historical issuance timeline of the certificate (queryable on crt.sh)

Risk note: no single layer is enough on its own. You must cross four to five layers before you have real resistance to impersonation.

1.1 Limitations of Browser One-Click Certificate Inspection

Chrome and Edge let you click the padlock and drill into certificate details, but the panel does not expose the SHA-256 fingerprint of every chain segment, and it does not show SCT details either. Manual verification therefore requires command-line tools.

1.2 Three Essential Tools

Tool Purpose Locally installed?
openssl Pull the chain, compute fingerprints, parse fields Yes (macOS/Linux built-in; Windows via Git Bash)
crt.sh Query public CT logs and historical issuance Web tool, no install
dig / nslookup Cross-verify DNS and CAA records Yes (Windows ships nslookup)

2. Pulling the Certificate Chain with openssl

Step one, retrieve the full chain from the Binance apex:

openssl s_client -connect binance.com:443 -servername binance.com -showcerts </dev/null

2.1 Sample Output (Key Excerpts)

CONNECTED(00000003)
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA
verify return:1
depth=1 C = US, O = DigiCert Inc, CN = DigiCert TLS RSA SHA256 2020 CA1
verify return:1
depth=0 C = KY, O = Binance Holdings Limited, CN = *.binance.com
verify return:1
---
Certificate chain
 0 s:C = KY, O = Binance Holdings Limited, CN = *.binance.com
   i:C = US, O = DigiCert Inc, CN = DigiCert TLS RSA SHA256 2020 CA1
-----BEGIN CERTIFICATE-----
MIIHXXXXX...(leaf certificate base64 payload)...
-----END CERTIFICATE-----
 1 s:C = US, O = DigiCert Inc, CN = DigiCert TLS RSA SHA256 2020 CA1
   i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA
-----BEGIN CERTIFICATE-----
MIIExxxxx...(intermediate certificate base64 payload)...
-----END CERTIFICATE-----

Three details worth memorising:

  • depth=0 is the leaf; Subject O is Binance Holdings Limited. This is the field phishing sites cannot practically fake because obtaining an OV/EV from DigiCert under a false organisation triggers offline vetting.
  • depth=1 is the intermediate; Issuer reads DigiCert TLS RSA SHA256 2020 CA1.
  • depth=2 is the root; DigiCert Global Root CA.

2.2 Extracting Each Segment to Disk

# Extract leaf certificate
openssl s_client -connect binance.com:443 -servername binance.com -showcerts </dev/null 2>/dev/null | \
  awk '/BEGIN CERT/,/END CERT/{print; if(/END CERT/) exit}' > leaf.pem

# Extract intermediate certificate
openssl s_client -connect binance.com:443 -servername binance.com -showcerts </dev/null 2>/dev/null | \
  awk 'BEGIN{n=0}/BEGIN CERT/{n++}n==2{print; if(/END CERT/) exit}' > intermediate.pem

2.3 Three Key openssl Commands

  • openssl x509 -in leaf.pem -noout -text to inspect every field of the leaf certificate.
  • openssl x509 -in leaf.pem -noout -fingerprint -sha256 to compute the SHA-256 fingerprint.
  • openssl verify -CAfile /etc/ssl/certs/ca-certificates.crt -untrusted intermediate.pem leaf.pem for a full-chain validation.

3. Signing Hierarchy Reference

The chain you retrieved must form a strict three-layer structure. Compare against the table below.

3.1 binance.com Certificate Hierarchy

Layer Type Subject O Common Name Issuer Typical validity
depth=0 Leaf Binance Holdings Limited *.binance.com DigiCert TLS RSA SHA256 2020 CA1 12 months
depth=1 Intermediate DigiCert Inc DigiCert TLS RSA SHA256 2020 CA1 DigiCert Global Root CA 10 years
depth=2 Root DigiCert Inc DigiCert Global Root CA self-signed 20 years

3.2 Contrast Against a Typical Phishing Chain

Layer Binance official Typical phishing (Let's Encrypt)
depth=0 Subject O Binance Holdings Limited usually empty or domain-only
depth=1 Issuer O DigiCert Inc Let's Encrypt
depth=2 Root DigiCert Global Root CA ISRG Root X1
Leaf validity 12 months 90 days
SCT count >= 2 >= 2 (Let's Encrypt also logs SCTs)
Organisation field forgeable? extremely hard (OV/EV need offline vetting) no organisation field

A: the decisive delta is the Subject O field at depth=0. Phishing sites use free DV certificates, which by design carry no organisation name, only a CN. The real Binance chain shows Subject O = Binance Holdings Limited, a value that requires offline entity verification with the CA.

3.3 Common Root CAs

  • DigiCert Global Root CA (Binance apex)
  • ISRG Root X1 (Let's Encrypt; most phishing sites)
  • GlobalSign Root CA (a handful of CDNs)
  • Sectigo / Comodo Root (some EV setups)

4. crt.sh Fingerprint Comparison and Timeline

Once the fingerprint is in hand from the command line, cross-verify against the public CT logs on crt.sh.

4.1 Three Query Modes on crt.sh

  1. By domain: https://crt.sh/?q=binance.com lists every historical issuance for that domain.
  2. By SHA-256 fingerprint: paste the openssl output directly to confirm the certificate appears in a CT log.
  3. By issuer CA: enumerate all Binance-related domains signed by a given CA.

4.2 Judgement Criteria

  • Genuine binance.com issuance records go back to 2017 with multiple rolling issuances every year.
  • The Issuer column should consistently show a commercial CA such as DigiCert or Sectigo, never suddenly switch to Let's Encrypt.
  • A domain first issued in 2025-2026 whose entire history sits on Let's Encrypt, combined with IDN homograph signals (see Unicode Homograph Detection), is essentially guaranteed phishing.

4.3 A Real crt.sh Cross-Verification

  • Copy the true hostname from the address bar.
  • Use openssl to pull the chain and compute the leaf's SHA-256 fingerprint.
  • Enter the fingerprint into crt.sh; look for matching records with a trusted issuer.
  • Match found + issuer trusted + timeline coherent -> verdict: genuine official certificate.
  • If any of the three is missing, drop the current page and return to the Binance Official Site from a bookmark.

Risk note: a crt.sh record does not equal real-time safety because a certificate can be revoked. True real-time verification requires OCSP or CRL; browsers do this automatically, and openssl supports it with the -status flag. That path is out of scope for this article.

5. The Full Four-Step Manual Workflow

Chaining every command above yields a complete manual verification.

  1. Pull the chain: openssl s_client -connect targetdomain:443 -servername targetdomain -showcerts </dev/null to get the entire hierarchy.
  2. Compute the fingerprint: openssl x509 -in leaf.pem -noout -fingerprint -sha256 for the leaf's SHA-256.
  3. Check the fields: cross-reference the hierarchy tables above; verify Subject O, Issuer O, and Root CA.
  4. crt.sh cross-verification: paste the fingerprint into crt.sh's search box; confirm historical matches, an acceptable issuer, and a coherent first-issuance time.

If all four pass, the endpoint is genuine. If any step fails, close the page and return via the Binance Official Site bookmark, or grab the Official Binance App from the Download Page and continue from within the app's private network path.

6. Auxiliary Verification: CAA, HSTS, and SCT

Three additional signals sharpen the verdict.

  • CAA records: dig binance.com CAA lists the CAs that are authorised to issue for the domain. The Binance apex restricts issuance to DigiCert and a few others. Phishing domains typically have no CAA or allow all CAs.
  • HSTS preload: binance.com is on the HSTS preload list, which forces HTTPS in browsers. Any HTTP attempt is blocked. Impersonation sites cannot inherit preload status.
  • SCT (Signed Certificate Timestamp): the real chain carries >= 2 SCTs from independent CT logs. openssl's CT Precertificate SCTs section will reveal them.

7. Frequently Asked Questions

Q: Does an openssl verify error automatically mean the site is fake?

A: Not necessarily. verify error 20 (unable to get local issuer certificate) merely signals that the local CA bundle is incomplete; pass -CAfile with a full bundle and the warning clears. verify error 21 (unable to verify the first certificate) is a real red flag, usually indicating a missing intermediate or misconfigured server. Complete the CA bundle first, then judge.

Q: What if Windows does not have openssl installed?

A: Install Git for Windows and openssl ships alongside; alternatively use WSL or Docker. As a lightweight fallback, the browser certificate panel can display Subject and Issuer fields, which is enough to catch 80% of impersonations even without fingerprints.

Q: Is a Let's Encrypt certificate always untrustworthy?

A: No. Let's Encrypt is a fully legitimate free CA and many mainstream sites use it. The question you should ask is not "which CA" but "does the Subject O field read Binance Holdings Limited". Phishing sites almost invariably lack the organisation field.

Q: If the domain sits behind Cloudflare, is the Subject O just "Cloudflare"?

A: It depends. With Cloudflare Universal SSL the leaf Subject O is usually empty and only CN is populated. If the customer uploads a custom certificate or uses SSL for SaaS, the organisation field appears. Cloudflare hosting therefore requires layering CAA records, DNS ownership, and crt.sh timeline together rather than trusting a single field.

Q: Do SHA-256 fingerprints change? Does a changed fingerprint mean phishing?

A: Fingerprints do change. Certificates get renewed and every 12 months a genuine site produces a new fingerprint. The right test is not fingerprint immutability but whether the new fingerprint appears in crt.sh, whether the issuer stays in the expected shortlist, and whether the timeline remains contiguous. For extra background see BiaBaLab Binance Domain History and Migrations.

Q: On mobile with no openssl, how do I verify a certificate?

A: The SSL Labs iOS / Android clients let you inspect the target's chain, Subject / Issuer, fingerprint and CT logs. Or simpler: install the Official Binance App. In-app requests use certificate pinning, which is more reliable than manual inspection.

Related Guides

Document published 2026-07-01, next re-test scheduled 2026-10-01.