Binance SSL Certificate Chain Verification With DigiCert and Certificate Transparency Log Queries

Binance binance.com certificates are issued by DigiCert. This article walks through Chrome certificate inspection, complete chain fields, CT log lookups, OCSP stapling and HSTS preloading.

Published on 2026-07-03 · About 15 min read · Fake Site Detection

Open binance.com, click the padlock in the address bar, and you will see the certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 with subject *.binance.com and a validity window covering the current date. This is the single verifiable trait of the official site. To compare quickly, use the verification page on this site or open the Binance Official Site and inspect it yourself.

Complete Certificate Chain Structure

A TLS certificate is not a single file but a multi-level chain from the root CA down to the leaf certificate. Clients trust the leaf via trust in any node on the chain.

The Three-Level Chain

  • Root CA: DigiCert Global Root G2, preinstalled in every major operating system and browser trust store.
  • Intermediate CA: DigiCert Global G2 TLS RSA SHA256 2020 CA1, issued by the root CA.
  • Leaf certificate: subject *.binance.com, issued by the intermediate CA.

Key Fields at Each Level

Field Root CA Intermediate CA Leaf certificate
Subject DigiCert Global Root G2 DigiCert Global G2 TLS *.binance.com
Issuer Self-signed Root CA Intermediate CA
Valid From 2013-08-01 2021-04-14 2026-01-15
Valid To 2038-01-15 2031-04-13 2027-01-15
Signature algorithm SHA256-RSA SHA256-RSA SHA256-RSA
Key type RSA 2048 RSA 2048 ECDSA P-256

SAN List

Besides *.binance.com, the leaf certificate's Subject Alternative Names field also contains the bare binance.com domain and selected subdomains. Note: the *.binance.com wildcard does not cover second-level wildcards such as api.futures.binance.com, which are protected by separate certificates.

Chrome Certificate Inspection

Since Chrome 93, the certificate viewer has moved to a nested location under the padlock.

GUI Path

  1. Open binance.com and click the padlock icon in the address bar.
  2. In the popover, choose "Connection is secure."
  3. Click "Certificate is valid" to open the details.
  4. The certificate viewer displays the issuer and subject.
  5. Switch to the "Details" tab for the full field list.

Command-Line Verification

Q: How do I verify the certificate from the terminal?

A: Use openssl s_client -connect binance.com:443 -servername binance.com -showcerts, which prints the entire chain in PEM format. Pipe it into openssl x509 -text to inspect each certificate's details.

Fingerprint Comparison

The leaf certificate's SHA-256 fingerprint is a 64-character hex string. Clients can compare it with the fingerprint published on this site's verification page. The fingerprint is updated publicly whenever it changes.

Certificate Transparency (CT)

CT is an open standard led by Google that requires all trusted CAs to publish issued certificates to append-only public logs, making certificate issuance auditable across the web.

CT Log Query Tools

  • crt.sh: query historical certificates for any domain.
  • Censys: enterprise-grade certificate search.
  • Google Transparency Report: Google's official entry point.
  • Facebook CT Monitor: email subscription service from Meta.
  • Cert Spotter: programmable API with automated alerts.

Querying binance.com History

Visit crt.sh/?q=binance.com to see every certificate issued for the domain since 2019, including issuer, validity window and SAN list.

Anomaly Alerting

Q: Why should I care about CT logs?

A: Once a CT log records an unauthorized issuance, administrators can spot it instantly and demand revocation from the CA. Binance's internal security team subscribes to crt.sh alerts, and any anomalous issuance triggers a response within minutes.

OCSP Stapling and HSTS Preload

OCSP Stapling

OCSP (Online Certificate Status Protocol) is used to query certificate revocation status online. Traditional OCSP forces the client to query the CA, which leaks which sites they visit and adds latency.

OCSP Stapling shifts the query to the server, which periodically checks the CA, caches the signed response and ships it alongside the TLS handshake, fixing both the privacy leak and the latency hit.

HSTS Preload

HTTP Strict Transport Security forces browsers to reach a domain over HTTPS only. binance.com is in the HSTS preload lists of Chrome and Firefox, so browsers upgrade to HTTPS from the very first visit.

  • HSTS header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
  • Preload list: https://hstspreload.org can look up current status.
  • Coverage: binance.com and every subdomain.
  • Renewal: rolling one-year window.

Common Error Codes

Error code Meaning Suggested fix
NET::ERR_CERT_AUTHORITY_INVALID Broken chain Check that the intermediate certificate is installed
NET::ERR_CERT_DATE_INVALID Expired or clock skew Sync the system time
NET::ERR_CERT_COMMON_NAME_INVALID Subject name mismatch Check for hijacking
NET::ERR_CERT_REVOKED Certificate revoked Leave the site immediately
ERR_SSL_PROTOCOL_ERROR TLS handshake failure Try updating the browser

Frequently Asked Questions

Q: Why does the browser say the certificate is untrusted?

A: Three possibilities. First, an outdated browser trust store - update the browser. Second, a system clock skew greater than five minutes. Third, you may have hit a phishing site whose certificate was issued by Let's Encrypt or an unknown CA. Warning: any binance.com certificate not issued by DigiCert is likely an attack; leave the site and investigate your network.

Q: What is the difference between Let's Encrypt and DigiCert?

A: Let's Encrypt is a free automated CA offering only domain validation (DV). DigiCert offers extended validation (EV) and organization validation (OV) that verify the legal entity behind the certificate. Binance uses DigiCert to provide stronger identity assurance.

Q: Why can't I see the full certificate on mobile browsers?

A: iOS Safari only shows the issuer name, while Android Chrome exposes more fields. For the full chain use a desktop browser or the SSL Labs mobile test report.

Q: What happens when the certificate is about to expire?

A: Binance completes each certificate rollover 30 days ahead of expiry, so users need to do nothing. If your browser still reports expiry, update the browser or fix your system clock.

Q: How do I monitor binance.com certificate changes?

A: Subscribe to crt.sh or Cert Spotter email alerts. Any new issuance for the domain will be pushed in real time.

Q: Does the Android app verify certificates?

A: The Official Binance App implements certificate pinning, so any certificate other than the pinned one is rejected. Even a compromised system trust store cannot mount a man-in-the-middle attack.

Q: Can HTTPS be forcibly downgraded to HTTP?

A: No. HSTS preload guarantees the browser will never send an HTTP request to binance.com. To Register on Binance, visit the Binance Official Site.

Published 2026-07-01. Next review scheduled for 2026-10-01.