Seeing Exness blocked in your browser, or watching the page spin forever right when you need to log in, check an open position or request a withdrawal, is a frustrating situation for any trader. In many cases, finding that you cannot access Exness has nothing to do with your trading account or your balance — it comes down to how your internet provider handles domain name lookups.
One simple way to access Exness again is to change Chrome DNS settings so the browser resolves domains through Cloudflare’s public DNS 1.1.1.1 service instead of the resolver your ISP assigns by default. You can do this directly inside Google Chrome, with no extra software, in roughly two minutes.
In this guide, Backcom.io walks through each step of enabling Secure DNS in Chrome, verifying that the new resolver is actually being used, and what to try next if you still cannot reach the site.
Why Is Exness Blocked in Some Countries?

Users typically report that Exness blocked pages fail to load at all, return a connection error, or redirect in a loop. This usually happens in jurisdictions where Exness — an international broker — is not locally licensed, so the domain may be restricted by internet service providers under local regulatory requirements.
One of the most common restriction methods is applied at the ISP’s DNS servers. Think of DNS as the “phone book of the internet”: it turns a domain name such as exness.com into the server address behind it. When your provider’s DNS refuses to return that address, you cannot access Exness even though your internet connection itself is working perfectly.
Before trading with any international broker, it is also worth reviewing the criteria for choosing a reputable forex broker and its regulatory background. Understanding licensing, transparency and access risk up front helps you pick a platform you can actually rely on.
What Does It Mean to Change Chrome DNS, and Why Does It Help?
Google Chrome ships with a built-in Secure DNS feature powered by DNS over HTTPS (DoH). Once it is switched on, your domain lookups are encrypted and sent to the DNS provider you select, rather than depending entirely on the default resolver handed out by your network.
That is why choosing to change Chrome DNS to Cloudflare’s DNS 1.1.1.1 can restore access when the Exness domain is only being filtered at the DNS layer. It is a straightforward way to access Exness because everything happens inside Chrome itself — no VPN subscription, no extension, no system-wide configuration.
Beyond letting you pick a public resolver, Secure DNS also encrypts the lookups themselves, so the domains you request are no longer sent in plain text across the network. That said, this method does not defeat every form of restriction. If Exness blocked access is enforced deeper in the connection rather than at DNS, you may need the fallback options covered further down.
How to Access Exness: Enable DNS 1.1.1.1 in Chrome in 5 Steps
If the site fails to load because of DNS, the fastest way to access Exness again is a five-step change: (1) open Chrome Settings, (2) go to Privacy and security, (3) open Security, (4) turn on Use secure DNS and pick Cloudflare (1.1.1.1), (5) reload the Exness website.

Step 1: Open Google Chrome Settings
Open Google Chrome on your desktop, then:
- Click the three-dot icon in the top-right corner.
- Select Settings.
- Chrome opens the settings page in a new tab.
You can also jump straight there by typing this address into the URL bar:
chrome://settings/security
This takes you directly to the security section without digging through several menus.
Step 2: Go to Privacy and Security
Inside Settings, choose:
Privacy and security → Security
Chrome shows the settings that control safe browsing, certificates, connections and Secure DNS here.
If Exness blocked access is coming from your provider’s DNS lookups, this is the screen you need to change so Chrome uses a different public DNS provider.
Step 3: Turn On “Use Secure DNS”
Scroll down to the section named:
Use secure DNS
Switch the toggle on if Chrome currently has it disabled.
With Secure DNS enabled, Chrome can use DNS over HTTPS (DoH) to encrypt your lookups and send them to the provider you choose.
This is the most important step when you change Chrome DNS, because the browser stops relying entirely on your network’s default resolver.
Step 4: Select Cloudflare (1.1.1.1)
In the DNS provider dropdown, select:
Cloudflare (1.1.1.1)
Cloudflare runs the public DNS 1.1.1.1 resolver and supports DNS over HTTPS in Chrome.
Chrome saves the choice automatically. You do not need to restart the browser or install an add-on.
Step 5: Reload the Exness Website
Once you have finished the steps to change Chrome DNS, do the following:
- Close the Exness tab that is showing the error.
- Open the site again using the official domain.
- Press Ctrl + F5 to force a full reload.
- Check whether the login page now behaves normally.
Where Exness blocked access was applied at the DNS layer, this change usually lets Chrome resolve the domain through Cloudflare instead of your provider’s default resolver.
Check Whether DNS 1.1.1.1 Is Actually Working
After the setup, confirm that Chrome is genuinely using DNS 1.1.1.1 rather than falling back to the old resolver.
Visit Cloudflare’s official diagnostic page at 1.1.1.1/help. Under Using DNS over HTTPS (DoH), a result of Yes means Secure DNS through Cloudflare is active.
You can also consult Cloudflare’s official 1.1.1.1 setup documentation for per-device configuration instructions and further checks.
If the result still reads No, go back to chrome://settings/security and confirm that Secure DNS is switched on and that the provider is set to Cloudflare (1.1.1.1).
Switching to DNS 1.1.1.1 on Mobile (Android and iPhone)
If you trade mostly from a phone, you can also use DNS 1.1.1.1 to help reach the Exness website there. The setup differs between Android and iPhone, so follow the instructions for your operating system.

On Android: Chrome Has Secure DNS Built In
On Android, Google Chrome offers the same Secure DNS option as the desktop version. Here is the sequence:
- Open Google Chrome.
- Tap the three-dot icon.
- Select Settings.
- Go to Privacy and security.
- Tap Use secure DNS.
- Choose the provider Cloudflare (1.1.1.1).
When you are done, close the open tab and load the Exness website again. If the cause was your network’s default DNS, this change can restore access without installing any app.
On iPhone: Use the 1.1.1.1 (WARP) App or Change Wi-Fi DNS
Chrome on iPhone does not expose a Secure DNS setting the way Chrome on Android and desktop does. iOS users therefore have two practical options:
- Install Cloudflare’s 1.1.1.1 app and enable the connection inside the app.
- Change the DNS server of your Wi-Fi network to 1.1.1.1 in the iPhone network settings.
If you regularly find that you cannot access Exness from your phone, the 1.1.1.1 app is more convenient, because you do not have to reconfigure DNS for every Wi-Fi network you join.
That said, if you are already on DNS 1.1.1.1 and the site still refuses to load, DNS may not be the only factor. In that case, move on to the troubleshooting steps below.
Still Cannot Access Exness? 4 Things to Try Next
If DNS 1.1.1.1 is enabled and you still cannot access Exness, the restriction may go beyond simple DNS filtering. Work through the four options below before contacting support.

1. Flush the DNS Cache and Browser Cache
Stale DNS entries or cached browser data can keep serving the same error even after you change Chrome DNS settings.
It helps to:
- Clear Chrome’s cache and cookies.
- Quit the browser completely, then reopen it.
- Reload the site with Ctrl + F5.
- Double-check your Wi-Fi or mobile data connection.
Then try the way to access Exness through the official domain one more time.
2. Use the 1.1.1.1 WARP App
If changing the resolver alone is not enough, try Cloudflare’s 1.1.1.1 WARP application.
Unlike a plain DNS change, WARP mode affects the network connection more broadly. That makes it a reasonable fallback when Exness blocked access is enforced in a way that Chrome’s Secure DNS cannot address on its own.
Download the app only from the official store listing, and check the developer name before installing.
3. Use the Official Exness Trade App
Traders on mobile can try logging in through Exness Trade instead of a web browser.
The app lets you manage your account, review your details and use the functions Exness supports on mobile devices. In some cases, a website that will not load does not mean the app is affected in the same way.
Only download it from the App Store, Google Play or an official source provided by Exness.
4. Contact Exness Support
If none of the above works, reach out to Exness live chat or customer support to:
- Confirm the current access status.
- Check whether the issue is specific to your account.
- Request an official access address if one is needed.
- Verify that the app or domain you are using is the correct one.
This is far safer than hunting for unofficial Exness addresses posted around the internet.
⚠️ Warning: Never Log In on Fake Exness Websites
Do not search for an “Exness login link” or “which link works when Exness is blocked” and then click at random on whatever appears in Google, on social media or in group chats.
Phishing sites can copy almost the entire Exness interface in order to capture:
- Your login email.
- Your account password.
- Verification codes.
- Personal information or payment details.
When you need to sign in, always start from the official Exness website or an address sent to you directly through the broker’s own support channels.
In particular, if a site asks for your login credentials but the domain looks unfamiliar, contains spelling mistakes, adds extra characters, or pairs the Exness brand with words like “login”, “broker” or “trade” from an unknown source, stop and do not sign in.
Account security matters more than getting in quickly. Whenever something looks off, pause and verify the domain before typing any information at all.
Frequently Asked Questions (FAQ)
Is It Legal and Safe to Change Chrome DNS?
The option to change Chrome DNS is a standard technical setting built into the browser, letting you pick a public DNS provider instead of the network default. Cloudflare is a widely used provider and supports DNS over HTTPS to encrypt lookups. Even so, you should consider the legal framework that applies where you live before accessing international brokers.
Does DNS 1.1.1.1 Slow Down My Internet?
Normally, DNS 1.1.1.1 does not slow down your connection, because DNS mainly handles domain resolution rather than the data transfer itself. Real-world speed still depends on your provider, your location and the quality of the connection. In some cases a public resolver actually returns more consistent response times than the default one.
If Exness Is Blocked, Are My Funds and Open Trades Affected?
Within the scope of this guide, Exness blocked access at the website level does not mean your account, balance or open positions on the broker’s servers have been removed. If you cannot access Exness, check your connection, try the official app, or contact Exness support to confirm your account status.
Conclusion
When Exness blocked pages appear in your browser, or you simply cannot access Exness at all, one of the simplest remedies is to change Chrome DNS to Cloudflare’s DNS 1.1.1.1. On desktop Chrome the whole process takes about two minutes and requires no additional software.
In short, work through this order:
- Turn on Secure DNS in Chrome.
- Select Cloudflare (1.1.1.1) as the DNS provider.
- Confirm the setup at 1.1.1.1/help before reloading Exness.
- If it still fails, try WARP, Exness Trade or official support.
- Never log in on an Exness site whose domain you cannot verify.
If you are looking for a more stable way to access Exness day to day, always favour the broker’s official website and app, and check the domain carefully before entering your login details.
Traders already using Exness can look at the Exness cashback programme at Backcom.io to claw back part of their trading costs. Comparing the Standard, Pro, Raw Spread and Zero account types before you commit is also worth the few minutes it takes.
Note: This content is provided purely as technical guidance on DNS and internet access. Backcom.io makes no guarantee that access will be restored in every case. Readers should review the regulations that apply in their own jurisdiction and take responsibility for their own decisions when trading with international brokers.





















