Official Gateway

What are Binance Mirror Domains? 2026 Latest List & Connectivity Testing

Binance maintains 20+ backup mirror domains globally for switching when the main site is restricted. This article organizes the latest available mirror list for April 2026 and provides 3 methods to batch-detect if domains have expired.

Binance currently maintains over 20 official mirror domains on the public web, with approximately 8–12 entries regularly available to general users. When the main binance.com site experiences resolution issues or returns 451 or 403 status codes, you can switch to another available domain via a mirror. Regardless of which mirror you access, you will ultimately log into the same account system (with the exception of binance.us). This article compiles the list of mirrors verified as accessible as of April 2026, along with methods to detect if a domain has expired. If you prefer to jump straight to a stable entry, you can visit the Binance Official page for currently verified domains, or download the local installer directly via the Binance Official App to bypass browser-level channel issues.

1. What are Binance Mirror Domains?

Relationship Between Mirror and Main Domains

A mirror domain is a backup domain that points to the same account system and the same fund custody entity as the main binance.com site. Their backend services, trade matching, and fund settlement are all completed in the same Binance data center. When a user logs in from binance.info, their account, assets, and orders are identical to those accessed from binance.com.

Technically, these mirrors are resolved to Binance's CDN edge nodes via different CNAME or A records. Most mirrors use Cloudflare, CloudFront, or Binance's self-built WAF frontends, which reverse-proxy to the same set of application servers.

Why So Many Mirrors are Needed

There are three main categories of reasons:

  1. Regional Blocking: ISPs in certain countries may apply DNS poisoning, SNI blocking, or BGP blackholing to binance.com.
  2. Regulatory Redirection: Some jurisdictions require users to access local compliant versions (e.g., binance.us, binance.co.jp).
  3. Emergency Backup: During DDoS attacks or large-scale CDN failures, Binance temporarily enables backup subdomains for load switching.

2. April 2026 Latest Available Mirror List

Global General Mirrors

Domain Purpose Certificate Issuer HTTP/2
binance.com Main Domain DigiCert EV Supported
binance.info Global Backup DigiCert Supported
binance.bz Global Backup Cloudflare Supported
binance.org BNB Chain & DEX Entry Cloudflare Supported
accounts.binance.com Unified Authentication DigiCert EV Supported
api.binance.com Public API Entry DigiCert Supported
www.binance.com 301 to Main Domain DigiCert EV Supported

Regional Compliant Entities (Independent Account Systems)

Domain Country/Region Independent Account Independent Fund Pool
binance.us United States Yes Yes
binance.co.jp Japan Yes Yes
binance.com.au Australia Yes (Some features frozen) Yes
binance.je Jersey Yes (EUR deposits) Partially Shared
binance.sg Singapore Closed in 2021 -

Functional Subdomains

These domains are functional sub-sites that typically redirect from the main site:

  • c2c.binance.com — C2C Fiat Trading
  • futures.binance.com — Futures Trading
  • fan-token.binance.com — Fan Tokens
  • academy.binance.com — Binance Academy
  • research.binance.com — Market Research Reports
  • labs.binance.com — Binance Labs Venture Capital

3. How to Detect if a Mirror Has Expired

Method 1: Direct Browser Access

The most straightforward but basic method. Enter the full domain (with the https:// prefix) in the address bar and observe these 4 indicators:

  1. Whether the first screen loads within 5 seconds;
  2. Whether your login status is displayed (if you are already logged in);
  3. Click the 🔒 icon in the address bar to see if the certificate "Subject" contains binance;
  4. Whether the console shows a large number of red 4xx / 5xx requests.

If the first screen takes over 10 seconds to load or an ERR_CONNECTION_TIMED_OUT / ERR_NAME_NOT_RESOLVED error appears, the domain is unavailable on your network.

Method 2: Command Line DNS + TLS Dual Testing

Execute the following in Windows PowerShell or macOS/Linux Terminal:

# 1. Query DNS Resolution
nslookup binance.info 8.8.8.8

# 2. Verify TLS Handshake
curl -I -v --connect-timeout 5 https://binance.info

# 3. View Certificate Expiration
openssl s_client -connect binance.info:443 -servername binance.info < /dev/null 2>/dev/null | openssl x509 -noout -dates

If nslookup returns an IP belonging to reserved segments like 198.51.100.x / 203.0.113.x / 10.x.x.x, it is likely DNS poisoning. Try switching to a different DNS server (e.g., Cloudflare 1.1.1.1 or Quad9 9.9.9.9).

Method 3: Using Third-party Monitoring Tools

  • DownDetector: Search for "Binance" to see global user reports of outages;
  • Cloudflare Radar: Displays real-time traffic distribution for binance.com;
  • isitdownrightnow.com: Enter any domain to check the reachability of global CDN nodes;
  • MXToolbox: Batch-query DNS record types (A/AAAA/CNAME/MX/TXT).

Cross-referencing multiple tools can help rule out local network issues.

4. What is (and Isn't) Lost After Switching Mirrors

What You Won't Lose

  • Account Credentials and Login Status (OAuth tokens are cross-mirror compatible);
  • Asset Balances and Positions (Shared backend database);
  • Trade History and Orders (Full synchronization);
  • 2FA, Anti-phishing Code, and API Keys (Account-level configurations that apply across mirrors).

What You May Need to Redo

  • Browser Bookmarks: Original bookmarks will fail after a domain change and need to be re-saved;
  • Local Cookies: Browsers isolate cookies by domain; you must log in again on a new mirror;
  • Certificate Pinning: If you use certificate pinning in enterprise proxies or plugins, you must update the rules;
  • Device Authentication: Logging in for the first time on a new domain may require email or phone secondary confirmation.

5. Identifying Fake "Mirror" Phishing Sites

Common Phishing Tactics

Phishing sites often use the following methods:

  1. Look-alike Spellings: binanca.com, bineance.com, bInance.com (using uppercase I to look like l);
  2. Adding vip/pro/cn Suffixes: binance-vip.com, binance-pro.net, binancecn.top;
  3. Disguising as Mirrors: mirror.binance-free.com, binance-mirror.site;
  4. Short Link Redirects: Using bit.ly or tinyurl to hide the final phishing destination.

The real Binance never uses these formats. All official domains start with the plain word binance, followed by a standard top-level domain (.com/.us/.info/.bz/.org/.co.jp), without hyphens or marketing terms like vip/pro/cn.

Three Hard Standards for Judgment

  • WHOIS Registrar: Real Binance domains are typically registered through MarkMonitor, Inc. (a professional corporate domain protector), while phishing sites often use GoDaddy, NameCheap, or Gandi;
  • Certificate Authority: Real Binance domains use DigiCert EV certificates on the main site; phishing sites often use free Let's Encrypt or ZeroSSL certificates;
  • Creation Date: binance.com was created in April 2017. Phishing sites are often only a few months old. Check the Creation Date field via whois binance-xxx.com.

6. Practical Tip: Batch Detection Script Logic

If you maintain a list of mirrors, you can put the following logic into a Shell script or scheduled task:

domains=("binance.com" "binance.info" "binance.bz" "binance.org" "accounts.binance.com")
for d in "${domains[@]}"; do
  status=$(curl -s -o /dev/null -w "%{http_code}" --connect-timeout 5 "https://$d")
  echo "$d => $status"
done

Expected output: Each available domain returns 200 or 301; failed domains return 000 (timeout) or 5xx. You can push the results to Telegram or email for monitoring alerts.

For more robust toolchains, use open-source monitoring like uptime-kuma or statping, which support HTTPS keyword detection, TLS certificate expiration alerts, and response time trend charts.

7. Emergency Path When Mirrors Fail

When all browser mirrors are inaccessible, try the following in order of priority:

  1. Switch DNS to 1.1.1.1 or 9.9.9.9;
  2. Switch network channels (4G/5G ↔ Wi-Fi);
  3. Clear local DNS cache (ipconfig /flushdns or sudo dscacheutil -flushcache);
  4. Launch the Binance Official App, as apps use independent channels usually unaffected by browser DNS poisoning;
  5. Use the desktop client (Mac/Windows version) instead of the web browser;
  6. Only as a last resort, use API clients or third-party aggregators.

The core advantage of the App channel is its own domain resolver and SNI handling, bypassing browser-level interception strategies.

FAQ

Q1: Exactly how many mirror domains does Binance have?

A: While over 20 official domains are publicly discoverable, there are 6–8 entries commonly used by general users (binance.com, binance.info, binance.bz, binance.org, accounts.binance.com, etc.). The rest are functional subdomains or regional compliant entities.

Q2: Are mirror domains slower than the main site?

A: Not necessarily. binance.info and binance.bz use Cloudflare CDN, which can have lower latency than binance.com (using Binance's self-built edge) in some East Asian nodes. Test the lowest latency domain on your network using ping or mtr.

Q3: Can I log into a mirror domain with my own account?

A: All mirrors of the global main site (binance.info, binance.bz, etc.) share the same account system. However, binance.us and binance.co.jp are independent entities; their accounts, KYC, and funds are not interoperable, and cross-site login is not possible.

Q4: How do I know which mirror is currently the most stable?

A: Our Binance Official page automatically tests the reachability of all official domains weekly and publishes the rankings. You can also run the script provided in this article to record availability rates over a week. Typically, binance.info is the most stable backup.

Q5: What if all mirrors fail?

A: This extreme situation is rare. If it happens, first check if it's an issue with your local network (test with 4G, different DNS, or another device). If a global failure is confirmed, follow official announcements on X (formerly Twitter) via @binance; emergency mirrors are usually published within 1–2 hours. The Binance Official App can typically continue trading as its channel is independent of the web.

Want to keep track of Binance domain updates? Return to Categories and select the "Official Gateway" category, or view All Tutorials for the latest updates.

Keep reading

Still have Binance questions? Head back to the category page for more tutorials on the same topic.

Categories

Related tutorials

Binance PC Web vs. Mobile H5: What are the Differences? A Feature Comparison 2026-04-10 How to Identify Binance Phishing Sites? 5 Features + Real Fake Cases 2026-04-11 What's the Difference Between binance.com/.us/.jp? Detailed Comparison of National Sites 2026-04-12 Available Ways to Access the Binance Official Website from Mainland China (Tested April 2026) 2026-04-12