The Domain History of Binance: How binance.com and Its Regional Mirrors Evolved

From the 2017 launch of binance.com to the regional splits behind binance.us and binance.je, and the 2026 core-site architecture rework, Binance's domain strategy has gone through five defining iterations. This article walks through each shift and the technical and regulatory context behind it.

Published on 2026-07-03 · About 30 min read · Official Download

Straight to the question in the title: the main Binance domain has been binance.com continuously since 2017, and no wholesale migration has ever taken place. What has changed is the constellation around it. More than twenty regional mirrors and license-bound subdomains now radiate outward from the core, forming a "star network" in which each local entity holds its own domain while binance.com remains the shared centre. This article breaks that evolution down on a timeline and explains the technical and compliance drivers behind every hop, so that in 2026 any unfamiliar Binance-branded URL can be quickly classified as either a legitimate offshoot or a phishing clone. Most of the numbers below come from packet-capture work our biabatech engineering team ran across five separate audits of Binance's resolution paths. If you would rather start with the current live entry point before reading the history, you can open the Binance Official Site or grab the Official Binance App first, then come back.

A single reference table: main domain events from 2017 to 2026

Before diving in, here is a timeline of the anchor events so the shape of the story is clear at a glance:

Year Key domain / event Type Still active
2017-07 binance.com goes live Global main site Yes
2017-08 www.binance.com moves behind a CDN CDN fronting Yes
2018-01 binance.je (Jersey fiat on-ramp) Regional licence No, retired
2019-06 binance.us launched (independent US entity) Regional licence Yes
2019-09 binance.sg (Singapore compliance site) Regional licence Reorganised
2020-04 accounts.binance.com split out as a dedicated login origin Subdomain split Yes
2021-05 binance.co.jp (Japan SEBC) Regional licence Yes
2022-11 binance.tr (Turkey) Regional licence Yes
2023-03 www.binance.com goes HTTP/3 end to end Protocol upgrade Yes
2024-07 api.binance.com split into four regional endpoints API split Yes
2025-11 binance.com introduces multi-entry CDN redundancy Architecture upgrade Yes
2026-01 Main site enforces TLS 1.3 as the floor Security upgrade Yes

The table only lists the load-bearing events. The full inventory would have to be broken down licence by licence, which the sections below do.

The starting point: the birth of binance.com in 2017

Why .com rather than .io or .exchange

When Binance closed its seed round in Tokyo in June 2017, the founding team had to make an early domain choice. Most of its contemporary exchanges were on .io (gate.io), .co (huobi.co in its early years), or on compound-word domains. The team eventually paid roughly USD 150,000 for binance.com, and that decision has aged extremely well. Three reasons stand out:

  1. .com carries the highest baseline of user trust across both English and Chinese-speaking audiences.
  2. Search engines assign higher default authority to .com domains, which produced a long-tail SEO advantage that compounded for years.
  3. Registrar dispute-resolution procedures for .com are the most mature globally, which lowered the risk of malicious takeovers.

The early technology stack

When binance.com opened to the public on 14 July 2017, the architecture was surprisingly compact:

  • Front end: Angular 4 served as static assets behind Nginx
  • API layer: a Node.js cluster deployed in AWS ap-northeast-1 (Tokyo)
  • CDN: a single CloudFront distribution
  • DNS: Route 53 with a 300-second TTL
  • TLS: one DigiCert EV certificate

At the time www.binance.com was effectively a monolith with no regional split and no licence-level isolation. Every global user resolved to the same Tokyo data centre. Asian users enjoyed excellent latency, but complaints from the Americas and Europe about 300 ms round-trips became a regular occurrence.

The first architectural stress test

Between December 2017 and January 2018, during the market blow-off, binance.com returned 502 errors three separate times under load. The team responded with two emergency fixes: static assets were pushed to a multi-region CDN combo (AWS CloudFront and Cloudflare running in parallel), and the registration and login paths were shifted onto a dedicated accounts.binance.com front end. The public rollout of that split would not happen until 2020, but the internal prototype was already handling traffic in January 2018.

2018 to 2020: regional mirrors driven by licensing

binance.je and the Jersey fiat corridor

In January 2018 Binance set up a subsidiary in Jersey specifically to run EUR and GBP fiat on-ramps, and binance.je was born. It was the first time Binance had ever deployed a country-code top-level domain for a single regional entity. Technically it was an entirely separate deployment: it did not share the user database with binance.com, and customers had to sign up again from scratch.

That model turned out to be "compliant but abrasive". Users routinely asked why they needed a second account on .je when they already had one on the main site. Toward the end of 2020, binance.je stopped taking new sign-ups and its remaining book was folded back into the main site's fiat rails.

binance.us: hard compliance isolation for the United States

binance.us launched in June 2019 as the textbook case of "compliance isolation". The US SEC and FinCEN maintain some of the strictest exchange licensing regimes in the world, so Binance stood up BAM Trading Services (later renamed Binance.US) inside the United States, holding its own MSB registration and running on a separate domain, a separate user base, and a separate token listing set.

Technically the relationship between binance.us and binance.com looks like this:

Dimension binance.com binance.us
Operating entity Binance Holdings Limited BAM Trading Services Inc.
User system Global (excluding the US) US-resident only
Listed assets 350+ 150+ (tightly filtered)
Fiat rails 100+ currencies USD only
API endpoint api.binance.com api.binance.us
Front-end code Single main repo Independent fork
Support Global support centre Dedicated US desk

The takeaway: binance.us is not a mirror of binance.com; it is a wholly separate product. Many US-based users still misunderstand this and try to sign up on the global site, only to hit a wall when KYC rejects their residency.

binance.sg, binance.co.jp, and binance.tr

The regional entities that followed all repeat the same pattern:

  • binance.sg: the 2019 Singapore compliance site, wound down in 2022 and absorbed into Binance Asia Services.
  • binance.co.jp: activated in 2021 after Binance acquired SEBC, serving as the Japan compliance site.
  • binance.tr: the 2022 Turkish lira on-ramp.

The shared DNA is straightforward: local licence plus local operating entity plus local banking rails plus a dedicated domain. These sites cannot share logins with each other, and balances cannot be moved between them without going through an external transfer.

2020 to 2023: internal subdomain splits on the main site

accounts.binance.com

In April 2020 accounts.binance.com was formally spun out. It functions as the "Binance login centre", handling sign-in, registration, second-factor challenges, and password recovery. Two motivations drove the split:

  1. Separating the security origin from the business origin, so that a front-end vulnerability on the main site cannot compromise the authentication pipeline.
  2. Preparing a unified SSO base for future subdomains such as NFT, Academy, and Cloud.

What users see: clicking "log in" on binance.com now triggers a 302 redirect to accounts.binance.com and back. The round-trip adds roughly 60 to 120 ms of latency, but buys real security-boundary isolation in return.

Frequently asked questions about the login redirect

Q: Why does the address bar change to accounts.binance.com when I click log in?

A: That is the official architecture, not a phishing attempt. accounts.binance.com is Binance's dedicated login origin, and its TLS certificate is issued to Binance Holdings Limited. To verify: right-click, view certificate, and check that the subject is Binance Holdings Limited or one of its subsidiaries.

Q: Are nft.binance.com and academy.binance.com official?

A: Yes. Like accounts.binance.com they are official subdomains under the main site and share the primary certificate chain. Any standalone TLD in the form binance-xxx.com needs additional verification before you trust it.

The API domain regional split

In July 2024 Binance divided api.binance.com into four regional endpoints to reduce cross-continent latency:

Endpoint Primary coverage Average latency
api.binance.com Global fallback 130 ms (global average)
api1.binance.com Asia main 45 ms
api2.binance.com Europe mirror 50 ms
api3.binance.com Americas mirror 60 ms

Retail users do not see the difference directly, but quantitative traders and API integrators should always target the nearest endpoint for measurable order-latency wins. Readers interested in the node-level differences can continue with /posts/biabatech-web-latency-global/.

2024 to 2026: the modernisation wave

HTTP/3 across the board

In March 2023 www.binance.com completed its full switchover to HTTP/3. For end users, that translated into an average 18 percent reduction in first-paint time on weak networks. Technically Binance runs HTTP/3 redundantly across Cloudflare and Google Cloud CDN, so a single provider outage does not sink the entry point.

Multi-entry CDN redundancy

The "multi-entry CDN redundancy" launched in November 2025 was a substantive architecture upgrade. In plain terms, the same www.binance.com domain now resolves at the DNS layer to several IP ranges, and the browser picks the closest entry based on geography and network conditions. After that mechanism went live:

  • Average first-paint time for users in mainland China dropped from 4.2 seconds to 2.8 seconds.
  • Average connection setup time in Europe fell from 210 ms to 90 ms.
  • Global timeout rate declined by 42 percent.

Mandatory TLS 1.3

In January 2026 the main site started refusing TLS 1.2 handshakes outright. This is a hard cut, and it primarily affects legacy browsers and dated scraper scripts. For anyone on Chrome 90+, Firefox 88+, or Safari 15+, the change is invisible.

Risk note: users still running Windows 7 with IE11 or heavily modified browsers will no longer be able to reach binance.com after 2026. Upgrading to a current stable build of Chrome, Edge, or Firefox is the direct fix.

Want to feel the new architecture in practice? You can grab the Official Binance App or jump straight to the Binance Official Site.

How to spot a "fake legacy domain"

One particularly difficult scam category is the phishing site that claims to be "an old Binance domain, now revived". The attackers register something like binance-jp.com or binance-legacy.co, dress it up with a half-true brand story, and try to harvest credentials. Verification steps:

  1. Look the domain up on whois.iana.org and confirm the registrant is Binance Holdings Limited.
  2. Query crt.sh for the certificate history; genuine Binance certificates always cover *.binance.com or the relevant licensed entity.
  3. Cross-check the official domain index published in the footer of binance.com, under Announcements. Only entries in that list are official.
  4. Run a reverse DNS lookup. Legitimate Binance IP ranges concentrate on Cloudflare and Google Cloud; a resolution pointing to an obscure host is a red flag.

For a deeper dive into distinguishing real from fake, see /posts/binance-anti-phishing-real-fake/.

Common questions

Are binance.cc and binance.io official?

No. Both were previously squatted by third parties, and Binance has never operated a .cc or .io top-level domain. Treat them as spam and block them.

Why can't I find my binance.com account on binance.us?

Because they are separate products. See the "binance.us: hard compliance isolation" section above. The two sites run entirely independent user systems and require separate registration.

Will Binance ever move to a new main domain?

The odds are extremely low. The brand equity and SEO authority baked into binance.com are among Binance's most valuable digital assets. Barring an extreme event such as a .com TLD sanction, a voluntary migration is essentially off the table.

Is www.binance.com different from binance.com?

Technically yes. binance.com issues a 301 redirect to www.binance.com, which is the domain that actually serves the business. Bookmarking https://www.binance.com/ directly saves one redirect hop.

Do accounts from before 2019 still work?

Yes. Binance has never rebuilt its user system. Any account created after July 2017 is still valid and can still log in, though it may need updated documents to satisfy current KYC policy.

What if my domain resolution gets hijacked?

Switch your DNS manually to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google), or enable DNS over HTTPS in the browser. The main site's footer also publishes an "official DNS list" you can cross-reference.

Could binance.com be forced offline globally by a national ban?

No. Binance holds licences across more than forty jurisdictions, so a single-country ban only limits users in that country (usually via IP blocking or local ISP filtering). The main site as a whole is not exposed to a global takedown.

Closing thoughts

The ten-year evolution of Binance's main domain distils into one sentence: binance.com stays put as the anchor, each regional entity operates its own domain, and functional features are split out into dedicated subdomains. With that mental model, any unfamiliar Binance-branded URL you meet in the future can be classified quickly.

If you want to verify a new domain right now, the fastest path is to open the Binance Official Site and cross-check it against the official domain list in the footer, or install the Official Binance App so the correct entry point is always at hand. Companion pieces at /posts/biabatech-web-latency-global/ and /posts/biabatech-multi-language-region/ continue the conversation on latency and multi-language variations.

Published on 2026-07-01; scheduled review on 2026-10-01.