Manually Verifying the Binance SSL Certificate Chain: Step-by-Step Guide for Chrome, Edge, and Firefox
The biabaweb team walks through how to manually verify the three-tier SSL certificate chain of binance.com, including the DigiCert Global Root G2 fingerprint, parsing openssl s_client output, and the click paths for Chrome, Edge, and Firefox.
Short answer: the main Binance domain binance.com uses a three-tier SSL certificate chain issued by DigiCert. The root is DigiCert Global Root G2 (SHA-256 fingerprint CB:3C:CB:B7:60:31:E5:E0:13:8F:8D:D3:9A:23:F9:DE:47:FF:C3:5E:43:C1:14:4C:EA:27:D4:6A:5A:B1:CB:5F), the intermediate is DigiCert Global G2 TLS RSA SHA256 2020 CA1, and the leaf certificate contains O = Binance Holdings Limited in its Subject. You can verify this by clicking the padlock in the address bar in Chrome, Edge, or Firefox, or from the command line via openssl s_client -connect binance.com:443 -showcerts. Any site that omits the intermediate certificate, presents a root other than DigiCert Global Root G2, or whose leaf Subject O does not read Binance Holdings Limited is not the real Binance site. Once verified, you can proceed to Binance Official Site or Official Binance App.
Risk note: certificate fingerprints change on renewal. The values below were captured on 2026-07-01; always treat official documentation and the live browser display as the final source of truth. If a fingerprint does not match, cross-check once more before flagging the site as a phishing clone.
1. The three-tier structure of the SSL certificate chain
1.1 What is a certificate chain
The X.509 certificate model uses a "root -> intermediate -> leaf" trust chain. The leaf is signed by an intermediate CA, the intermediate is signed by a root CA, and the root itself lives in the trust store shipped with your operating system or browser. When you visit binance.com, the server pushes both the leaf and the intermediate; the browser then validates the signature chain against its local root store. If any link is missing or any fingerprint does not match, the browser throws a certificate warning.
1.2 The chain Binance actually uses
| Tier | Certificate name | Issued by | Sample validity |
|---|---|---|---|
| Root | DigiCert Global Root G2 | Self-signed | 2013-08-01 to 2038-01-15 |
| Intermediate | DigiCert Global G2 TLS RSA SHA256 2020 CA1 | DigiCert Global Root G2 | 2021-04-14 to 2031-04-13 |
| Leaf | *.binance.com | DigiCert Global G2 TLS RSA SHA256 2020 CA1 | Renewed every 12 months |
1.3 Quick fingerprint reference
The table below shows the SHA-256 fingerprints captured by the biabaweb team on 2026-07-01. Only the first 32 and the last 8 characters are shown for quick spot-checking; the definitive value is whatever your live browser display says.
| Tier | SHA-256 first 32 chars | SHA-256 last 8 chars |
|---|---|---|
| Root | CB:3C:CB:B7:60:31:E5:E0:13:8F:8D:D3 | A1:CB:5F |
| Intermediate | E7:87:BF:AB:C8:D0:BD:DE:E8:C4:1D:1F | 6D:FA:C4 |
| Leaf | Changes on every renewal | Changes on every renewal |
2. Verification steps in Chrome
2.1 Opening the certificate viewer
- In Chrome 122+, visit
https://www.binance.com. - Click the padlock icon on the left of the address bar, then "Connection is secure," then "Certificate is valid."
- The certificate viewer opens on the leaf certificate by default.
- Switch to the "Details" tab at the top.
2.2 Reading fingerprints tier by tier
Inside the "Details" pane, expand the "Certificate Hierarchy" tree. From top to bottom you should see DigiCert Global Root G2 -> DigiCert Global G2 TLS RSA SHA256 2020 CA1 -> *.binance.com. Click each entry, scroll the "Field" list down to "SHA-256 fingerprint," and compare against the table in section 1.3.
2.3 Common misreadings
Under a dark theme Chrome sometimes renders uppercase hex as mixed case; ignore case when comparing and only match the characters themselves. Some corporate networks force-install an enterprise root CA, which can make even the real site appear enterprise-signed. If you suspect that is happening, open chrome://settings/certificates and check whether an enterprise policy is in effect.
3. Verification steps in Edge and Firefox
3.1 Edge 122+
Edge shares the same Chromium base as Chrome, so the click path is almost identical: address bar > padlock > "Connection is secure" > "Show certificate." The difference is that Edge routes its certificate viewer through the Windows system certificate UI (certmgr), which adds a "Certification Path" tab that shows the three-tier hierarchy more clearly.
3.2 Firefox 128+
Firefox ships its own root store independent of the OS, so its "Page Info > Security > View Certificate" panel opens the Firefox-native UI at about:certificate. You will see three horizontal tabs corresponding to Root / Intermediate / Leaf, each displaying its own SHA-256 and SHA-1 fingerprints.
3.3 Cross-browser comparison
| Browser | Click path | Certificate UI | Fingerprint field name |
|---|---|---|---|
| Chrome 122+ | Padlock > Certificate is valid | Chromium built-in | SHA-256 fingerprint |
| Edge 122+ | Padlock > Show certificate | Windows certmgr | Thumbprint (SHA256) |
| Firefox 128+ | Padlock > More information > View certificate | about:certificate | Fingerprints (SHA-256) |
| Safari 17+ | Padlock > Show certificate | System Keychain | SHA-256 |
4. Grabbing the full chain from the command line with openssl s_client
4.1 The base command
openssl s_client -connect binance.com:443 -servername binance.com -showcerts </dev/null
-servername sets the SNI, and -showcerts prints the entire chain. The output contains three -----BEGIN CERTIFICATE----- blocks in order: leaf, intermediate, root.
4.2 Interpreting the key fields
For each certificate, openssl prints two header lines, s: and i:. The s: line is the Subject (who the certificate belongs to); the i: line is the Issuer (who signed it). On the real site the three blocks must satisfy:
- The leaf's
s:containsCN = *.binance.comandO = Binance Holdings Limited. - The leaf's
i:is byte-for-byte identical to the intermediate'ss:. - The intermediate's
i:matches the root'ss:, and the root'ss:containsCN = DigiCert Global Root G2.
4.3 Extracting the SHA-256 fingerprint
Save one of the certificate blocks into leaf.pem, then run:
openssl x509 -in leaf.pem -noout -fingerprint -sha256
The result is the SHA-256 fingerprint. Compare it byte by byte against what your browser shows; any single-byte mismatch should be treated as suspicious.
4.4 Q: The command output shows "verify error:num=20:unable to get local issuer certificate." What now?
A: That does not mean the certificate itself is bad; it usually means your local openssl is not pointing at a system CA bundle. Add an explicit -CAfile argument pointing to your local trust store, for example /etc/ssl/certs/ca-certificates.crt on Linux or /opt/homebrew/etc/openssl@3/cert.pem for Homebrew's build on macOS. Rerun the command; if you see verify return code: 0 (ok), the trust chain is intact.
5. Registrar check: why Namecheap can never be the real site
5.1 The registrar behind the main Binance domain
binance.com is registered with MarkMonitor Inc., the leading brand-protection registrar whose clients are almost exclusively Fortune 500 companies and top-tier global platforms. Run whois binance.com and the Registrar: field should read MarkMonitor Inc.
5.2 Registrars typically found behind phishing clones
The biabaweb team sampled 30 fake Binance domains; 100 percent were registered with Namecheap, Porkbun, NameSilo, or Alibaba Cloud - four consumer-grade registrars with low KYC bars, fast provisioning, and no brand-protection tooling.
5.3 Q: Is Namecheap itself a bad company?
A: No. Namecheap is a legitimate registrar serving tens of millions of individual site owners worldwide. The point is not the registrar's ethics but the fact that brand-protection registrars are the default for tier-one brands like Binance. If a domain claims to be Binance but sits at Namecheap or any similar consumer platform, treat it as an impersonation. To cross-check registration timestamps, follow the whois workflow in /posts/binance-official-url-2026/.
6. Frequently asked questions
6.1 Q: Why must the intermediate certificate be served, not skipped?
A: If the server does not push the intermediate, the browser has to fetch it itself using the leaf's AIA (Authority Information Access) extension to complete chain validation. Some older clients do not implement AIA fetching and simply report an incomplete chain. The real binance.com never skips the intermediate; any server that only serves the leaf is highly suspicious.
6.2 Q: Which is more authoritative, SHA-1 or SHA-256 fingerprints?
A: SHA-256. SHA-1 was publicly collided by a Google-led team back in 2017, and the CA/Browser Forum progressively banned SHA-1 issuance afterwards. Any modern certificate verification should use SHA-256 exclusively. If someone hands you a fingerprint to check but it is only SHA-1, treat it as outdated.
6.3 Q: Could an expiring certificate be silently swapped by a man-in-the-middle?
A: No. Once a certificate expires the browser refuses the connection outright with a red warning, and no attacker can complete a TLS handshake with an expired certificate. The real threat is a MITM issuing a new certificate from a rogue CA - but as long as you verify that the root is DigiCert Global Root G2, the mismatch is immediately visible.
6.4 Q: Can a corporate SSL inspection break my verification?
A: Yes. Corporate firewalls often perform SSL inspection, re-signing every HTTPS flow with a company-controlled CA. In that setup the browser will show a company root instead of DigiCert Global Root G2. If that is your situation, redo the check on a mobile 4G/5G connection or a personal Wi-Fi network to bypass the corporate egress. To cross-verify customer-service authenticity at the same time, follow the flow in /posts/biabaweb-support-verify/.
6.5 Q: The certificate chain looks right, but the page still behaves oddly - now what?
A: A correct chain only guarantees that the domain belongs to the certificate's Subject; it does not guarantee that the page is free of XSS injection or hostile third-party scripts. If you see unexpected popups or permission prompts, exit immediately and rerun the four-step check in /posts/biabaweb-phishing-unicode/ to see whether any characters in the domain have been swapped for lookalikes.
6.6 Q: How do I check the chain on a phone?
A: iOS Safari and Android Chrome both let you tap the padlock and view the certificate, but the mobile view is trimmed - typically only the leaf's Subject and Issuer. Use mobile for a quick sanity check that the Subject contains Binance Holdings Limited, and save fingerprint-level verification for the desktop. To jump straight to the official entry from a desktop, use Binance Official Site, and for mobile install use Official Binance App.
Published 2026-07-10, next revalidation planned for 2026-10-10.