When the Binance official site can't be accessed, it doesn't mean your account has a problem. Most likely it's just local network-level DNS poisoning or ISP SNI interception. The simplest approach is to switch your local DNS to 1.1.1.1 or 8.8.8.8 and retry. If it still won't open, switch to the binance.info or binance.bz backup domain. If that doesn't work either, use the mobile APP to directly complete trades and check market data. The temporary unavailability of the desktop entrance doesn't affect asset safety at all—account status, open orders, and deposit/withdrawal records are all preserved on the backend, and you'll see them once access to the Binance Official Site is restored. Having the Binance Official App on hand is the most stable backup plan. New users should first install the APP according to the iOS Install Guide, so you don't get stuck with no fallback when the web side is disconnected. Below we break down common failures by symptom and give actionable methods one by one.
Common "Cannot Open" Symptoms and Their Causes
| Symptom | Common Cause | Primary Action |
|---|---|---|
| This site can't be reached / ERR_CONNECTION_RESET | SNI interception | Switch DNS + backup domain |
| Long spinning wheel then blank page | DNS poisoning | Switch to 1.1.1.1 / 8.8.8.8 |
| Homepage loads but login button doesn't respond | CDN node anomaly | Clear cache, switch browser |
| Stuck at "slider verification" on login | Human-machine identification risk control | Disable ad blocker extensions |
| Constant 502 / 504 | Regional CDN congestion | Change time slots or use APP |
| Constant 403 | Regional policy restriction | Confirm whether you're in a banned country |
Make a first-round judgment based on symptom, then decide whether to escalate the troubleshooting.
Switch DNS to a Public Resolver
Step 1: Windows PC
Click the network icon in the bottom right → "Open Network & Internet Settings" → "Change adapter options" → right-click the active adapter → "Properties" → double-click "Internet Protocol Version 4 (TCP/IPv4)" → select "Use the following DNS server addresses". Fill in 1.1.1.1 as primary and 1.0.0.1 as alternate (or Google's 8.8.8.8 / 8.8.4.4). After saving, run ipconfig /flushdns in the command line to clear the cache.
Step 2: macOS
"System Settings" → "Network" → select your current network → "Details" → "DNS" → click the "+" in the bottom left to add 1.1.1.1 and 8.8.8.8. After confirming, run sudo dscacheutil -flushcache in Terminal.
Step 3: Mobile
On iPhone: "Settings → Wi-Fi → tap the i icon next to the connected Wi-Fi → Configure DNS → Manual" to add public DNS. On Android, in the Wi-Fi advanced settings change "Private DNS" to 1dot1dot1dot1.cloudflare-dns.com, which is Cloudflare's DoH (encrypted DNS) address that further avoids DNS poisoning.
Step 4: Enable DoH / DoT
Mainstream browsers all support DNS over HTTPS: Chrome → Settings → Privacy and Security → Security → "Use secure DNS" → select Cloudflare (1.1.1.1). Firefox → Settings → General → Network Settings → "Enable DNS over HTTPS". Once enabled, even if your ISP's DNS is poisoned, you can bypass it.
Switching to Backup Domains
When the main site binance.com can't be resolved or times out on connection, Binance has prepared several parallel entrances:
- binance.info: Information and announcement site, where you can view the latest announcements and download APKs
- binance.bz: Lightweight entrance, with the homepage compressed to around 520KB
- accounts.binance.com: Login subdomain that sometimes still works when the main site doesn't
- www.binance.me: Regional mirror, accessible on some routes
Bookmark these domains in your browser in advance, and when the main site fails, cycle through them. Usually at least one will work.
Use the Mobile APP to Complete Trades
The APP Is Usually More Stable Than the Web
The Binance mobile APP uses a proprietary protocol to connect directly to the CDN, bypassing the web traffic path of standard HTTPS port 443. When network fluctuations are severe, it often still maintains a connection. Web-side order placement, futures positions, and deposit addresses can all be handled inside the APP.
APP Scan to Assist Web Login
If you insist on using the web for multi-screen trading, in the APP go to "My → Settings → Security → Device Management". There is a "Scan Login QR Code" feature. Scan the QR code on the web login page, and the APP will authorize PC web login. Even if the web side runs into a risk-control slider, you can skip it this way.
APP Network Switching
Inside the APP, go to "More → Settings → Network Diagnostics" at the bottom to check the latency of various Binance server nodes with one tap. If you see that a node's latency exceeds 500ms or times out, you can switch to "Global Acceleration" mode on the same page, and the APP will select a backup CDN.
Compliance Note on VPNs
Many people default to using a VPN when they can't access the site. Three points must be clear here:
- Mainland China has clear legal restrictions on unapproved cross-border VPNs. Personal use carries legal risk—please evaluate carefully.
- Binance officials have never required any user to use a VPN for access. Compliance-licensed countries and regions all have direct-connect entrances.
- Logging in after using a VPN will trigger foreign-location risk control, which may require email verification or KYC facial re-check.
A safer approach is to prioritize DNS switching, backup domains, and the APP. When cross-border access is truly needed, first complete KYC in the APP and bind commonly used devices to reduce risk-control friction.
5-Step Thorough Troubleshooting Process
Step 1: Test Basic Network
Run ping baidu.com from the command line. If it times out on its own, the network isn't working at all—first restart your router or switch to a 4G hotspot.
Step 2: Test DNS
Run nslookup binance.com. Normally it should return AWS CloudFront IPs starting with 13.x or 54.x. If it returns 127.0.0.1 or some unfamiliar domestic IP, it's DNS poisoning—switch DNS using the method from the previous section.
Step 3: Test TLS Handshake
Enter https://binance.com in the browser address bar. If you see "SSL_ERROR" or "ERR_SSL_PROTOCOL_ERROR", it means SNI is being intercepted—switch to DoH or a backup domain.
Step 4: Cross-Verify with Another Device
Use mobile 4G (with Wi-Fi off) to open the APP or m.binance.com. If 4G works and home Wi-Fi doesn't, it's an ISP routing issue. You can switch to another ISP's network or use the APP.
Step 5: Contact Customer Support
Go to "Customer Service" in the bottom right of the APP. Even when the web won't open, in-APP chat support usually still connects. Support will give you the currently recommended accessible domain based on your region.
FAQ
Does inaccessibility affect my assets?
No. Account data is stored server-side. A web page not opening is only a client-side connection issue. All asset records you see after logging in are real-time.
What if the APP can't connect either?
First check whether the APP has been denied "Background Data" permission by the system. On iPhone, go to "Settings → Binance → Wireless Data" and allow WLAN and cellular. On Android, go to "Settings → Apps → Binance → Mobile Data & WLAN" and allow background traffic. If it still doesn't work, switch to 4G or change Wi-Fi.
What could cause binance.info to also be unreachable?
If multiple domains are unreachable simultaneously, it's most likely that your local DNS is completely poisoned. Retry after switching to DoH or 1.1.1.1 public DNS.
Computer works, but I can't access the site on mobile?
It's most likely that the ISP has deployed SNI filtering on the mobile network. Switch to Wi-Fi, or fill in the Cloudflare DoH address under "Private DNS" on your phone.
I still can't open it even in browser incognito mode?
Incognito mode doesn't affect the network layer, only cookies. What really makes a difference is the configuration at the DNS and TLS layers. Switching DNS and domains as described above is the key.
Is it normal for results to differ by time slot?
Yes. Large numbers of users check prices at 8 AM and 10 PM, and CDN nodes may experience short-term congestion, causing slow page loads or localized 502s in some regions. You can avoid these two peak periods, or migrate common operations (order placement, K-line viewing) to the APP. Additionally, some routes undergo maintenance from 0-2 AM daily, usually lasting 5-15 minutes, and will recover after a short wait.