Binance Primary Domain History and 2026 Status: A Complete Ledger From binance.com to Regional Mirrors
The biabalab team maps ten years of change across binance.com and 30+ regional mirrors, complete with CNAME targets, CDN vendors, SSL fingerprints, and a July 2026 availability ledger to help you distinguish genuine entry points from impostors.
Direct answer: as of July 1, 2026, the sole global primary domain for Binance is still binance.com, running in parallel with more than thirty regional-suffix mirrors such as binance.us, binance.co.jp, and binance.com.tr. Over the past six months the biabalab lab has sampled DNS and TLS certificates for every one of these hostnames on a daily cadence. This post compresses a decade of change into a single timeline, then breaks the 2026 status down into three verifiable dimensions: CNAME, CDN, and SSL. When you finish reading, you will be able to look at the URL bar and decide whether the "binance-XXX" in front of you is authentic, and you will also be able to reproduce the biabalab verification script on your own machine. Readers who would rather go straight to sign-up can bookmark the Binance Official Site entry now and then come back to compare notes with the tables below, or grab the Official Binance App from the same trusted surface.
1. A Ten-Year Domain Timeline
Since Binance went live in July 2017, its domain layout has gone through four structural pivots. The following timeline is derived from WHOIS captures, Wayback Machine snapshots, and cross-referenced public announcements collected by biabalab.
1.1 2017-2019: The Single-Domain Era of binance.com
On July 14, 2017 binance.com resolved for the first time. The registrar was GoDaddy and NS records pointed to Cloudflare. During this window every language sub-site was mounted under the same root domain through directories such as /cn, /en, and /kr. DNS held only A, AAAA, and a single www CNAME record.
1.2 2019-2021: The Regional-Suffix Explosion
binance.us launched on September 2019. Over the next twelve months binance.je (Jersey, since retired), binance.sg (retired), binance.com.au, binance.com.tr, and binance.co.jp activated in quick succession. This is the point at which the exchange abandoned the "sub-directory" pattern in favor of "regional mirrors" as a way to isolate regulatory exposure.
1.3 2021-2023: The Short-Domain Experiment
Starting in May 2021, short-URL services such as bnc.lt and bmex.co were used as landing pages for mobile app distribution. The short domains were eventually all folded back into www.binance.com/download; our benchmark data showed the redirect chain added an average of 380 ms compared with a direct hit.
1.4 2024-2026: Multi-Mirror Plus Smart DNS
From Q2 2024 the exchange enabled GeoDNS-driven resolution: a single binance.com record now returns different IP ranges depending on the region. biabalab stood up VPS listeners in Tokyo, Frankfurt, and Sao Paulo to sample the responses daily; across three continents the returns differ by up to twelve distinct /24 subnets.
2. Domain x CNAME x CDN Ledger for July 2026
The table below records the state as measured at 08:00 UTC on 2026-07-01. It lists the primary domain, its CNAME target, the CDN vendor, and the certificate common name. Use it side by side with the Binance Official Site; if you encounter any "binance-xxx" hostname that is not present in the table, treat it as suspicious by default.
| Primary domain | CNAME target | CDN vendor | Certificate CN | Availability on 2026-07-01 |
|---|---|---|---|---|
| binance.com | www.bnc.tools | Cloudflare + Akamai dual-active | *.binance.com | Global |
| binance.us | bapi.binance.us | AWS CloudFront | *.binance.us | United States only |
| binance.co.jp | jp.binance.co.jp | Fastly | *.binance.co.jp | Japan IPs only |
| binance.com.tr | tr.binance.com.tr | Akamai | *.binance.com.tr | Turkey only |
| binance.com.au | au.binance.com.au | Cloudflare | *.binance.com.au | Australia only |
| accounts.binance.com | acc.bnc.tools | Cloudflare | accounts.binance.com | Global |
| www.binance.com | wgw.binance.com | Cloudflare | *.binance.com | Global |
2.1 CNAME Is the Strongest Identity Signal
biabalab recommends treating the CNAME target as the primary indicator of domain ownership. Every official host eventually resolves through bnc.tools or the binance.us second-level domain. A third-party mirror wrapping a shell around Binance branding cannot forge that record. The verification commands are simply:
dig +short CNAME www.binance.com
dig +short CNAME accounts.binance.com
A healthy response should contain bnc.tools. If it returns any other custom domain, stop what you are doing and switch to the download page to fetch a clean entry point.
2.2 The Dual-Active CDN Strategy
For 2026, Binance runs Cloudflare and Akamai side by side in front of binance.com. You can tell which CDN just served you by looking at the server response header: cloudflare means Cloudflare; AkamaiGHost or AkamaiNetStorage means Akamai. Our measurements show that most East Asian and Southeast Asian traffic terminates on Cloudflare, while North America and Latin America land on Akamai.
3. A 30-Second In-Browser Authenticity Check
A: Three steps are enough. First look at the top-level suffix, then the certificate SAN, then the CNAME. We turned this workflow into a checklist; any item that fails should raise a red flag.
A: If you can only remember one rule, remember this: the official certificate SAN must include *.binance.com or the corresponding regional wildcard. Fraudulent domains typically can only obtain a single-domain Let's Encrypt certificate and cannot cover a wildcard SAN.
- Check the suffix in the address bar. It must be one of
.com,.us,.co.jp,.com.tr, or.com.au. - Click the padlock icon, view certificate details, and find the "Subject Alternative Name" line.
- Open the developer-tools Network panel, tick "Preserve log", refresh, and confirm the
serverandcf-rayresponse headers match the table above. - Run
nslookupordigto double-check the CNAME. Confirm that the target ends inbnc.toolsorbinance.us. - If any of the above fails, close the tab immediately and re-enter through the in-app browser of the Official Binance App.
3.1 Telltale Signs of Fake Domains
Over the past ninety days biabalab tagged 214 impostor domains. Their shared characteristics are summarised below. Warning: fraudsters typically register twenty to forty variant domains in a single day, so treat any of the following as a hard stop.
| Feature | Frequency | Recommended action |
|---|---|---|
Suffix is .top, .xyz, or .icu |
68% | Close immediately |
CNAME points at github.io or pages.dev |
22% | Close immediately |
Issuer is Let's Encrypt with single-domain SAN |
41% | Close immediately |
| No accounts subdomain hand-off from home page | 55% | Close immediately |
| Unicode look-alikes injected (i to i-dotless) | 18% | Close immediately |
4. The biabalab Daily Verification Script
We compressed the whole flow into roughly thirty lines of shell. It runs at 08:00 UTC every day via GitHub Actions and pushes the results to Slack. Here is the core snippet:
for host in binance.com www.binance.com accounts.binance.com; do
echo "=== $host ==="
dig +short CNAME $host
echo | openssl s_client -connect $host:443 -servername $host 2>/dev/null \
| openssl x509 -noout -issuer -subject
done
Combined with the IP-range table in Binance Official URL 2026 Latest Guide you can cross-check the results a second way. If you need the mobile-app entry, see Binance App Download 2026 Latest Roundup.
5. FAQ
Q: Will binance.com ever be retired in favour of a new domain?
A: There is no public signal pointing to a migration. Official announcements in June 2026 still cite binance.com as the primary entry point. Our read at biabalab is that as long as the bnc.tools NS records stay unchanged, the primary domain is not going anywhere.
Q: Why does the IP returned for binance.com change every day when I ping it?
A: That is expected behaviour for a GeoDNS + Anycast setup. The same hostname resolves to different IPs at different resolver locations, and even the same node may rotate hourly. IP volatility on its own is not a warning sign; anchor your trust on CNAME and certificate instead.
Q: How do I verify the certificate quickly on a phone?
A: On iOS, tap the address bar in Safari, choose "aA", then "Website Settings" and "Certificate". On Android in Chrome, tap the padlock, choose "Connection is secure", then "Certificate details". Read the Subject Alternative Name line.
Q: Can an account on binance.us sign in to binance.com?
A: No. The two entities are legally isolated, the account systems are independent, and KYC data does not cross over. If you need cross-region access, see Binance iOS Region Switching Guide.
Q: What should I do if I see ERR_CERT_COMMON_NAME_INVALID?
A: This is usually caused by a local carrier or corporate proxy injecting an intermediate certificate. Switch to a 4G/5G cellular network and retry. If the error persists, change your DNS resolver to 1.1.1.1 or 8.8.8.8.
Q: Does the short domain bnc.lt still work?
A: No. Since December 2025 biabalab has observed that bnc.lt no longer resolves, and the exchange has fully consolidated onto www.binance.com/download. Treat any channel still promoting the short domain as either stale or a phishing lure.
Closing Notes
Domain reconnaissance is boring work until it is not, and the payoff for spending three minutes with dig and openssl is disproportionately large: you either catch a phishing surface early or you go about your day with high confidence. If in doubt, always reset from a known-good surface. The Binance Official Site and the Official Binance App remain the two entries we personally re-verify every morning at biabalab, and the ledger above is the reason we can do so in under a minute. Bookmark this post, star the verification script, and if the CNAME target ever drifts away from bnc.tools we will publish a follow-up before your morning coffee.
Published on 2026-07-01. Next re-measurement scheduled for 2026-10-01.