{"id":15846,"date":"2026-10-01T11:06:04","date_gmt":"2026-10-01T11:06:04","guid":{"rendered":"https:\/\/backcom.io\/?p=15846"},"modified":"2026-10-01T11:06:05","modified_gmt":"2026-10-01T11:06:05","slug":"xm-blocked-access-dns-1-1-1-1-chrome","status":"publish","type":"post","link":"https:\/\/backcom.io\/en\/xm-blocked-access-dns-1-1-1-1-chrome","title":{"rendered":"XM Blocked? How to Access XM Using DNS 1.1.1.1 on Google Chrome"},"content":{"rendered":"\n\n<div class=\"kk-star-ratings kksr-auto kksr-align-left kksr-valign-top\"\n    data-payload='{&quot;align&quot;:&quot;left&quot;,&quot;id&quot;:&quot;15846&quot;,&quot;slug&quot;:&quot;default&quot;,&quot;valign&quot;:&quot;top&quot;,&quot;ignore&quot;:&quot;&quot;,&quot;reference&quot;:&quot;auto&quot;,&quot;class&quot;:&quot;&quot;,&quot;count&quot;:&quot;0&quot;,&quot;legendonly&quot;:&quot;&quot;,&quot;readonly&quot;:&quot;&quot;,&quot;score&quot;:&quot;0&quot;,&quot;starsonly&quot;:&quot;&quot;,&quot;best&quot;:&quot;5&quot;,&quot;gap&quot;:&quot;5&quot;,&quot;greet&quot;:&quot;Rate this post&quot;,&quot;legend&quot;:&quot;0\\\/5 - (0 votes)&quot;,&quot;size&quot;:&quot;24&quot;,&quot;title&quot;:&quot;XM Blocked? How to Access XM Using DNS 1.1.1.1 on Google Chrome&quot;,&quot;width&quot;:&quot;0&quot;,&quot;_legend&quot;:&quot;{score}\\\/{best} - ({count} {votes})&quot;,&quot;font_factor&quot;:&quot;1.25&quot;}'>\n            \n<div class=\"kksr-stars\">\n    \n<div class=\"kksr-stars-inactive\">\n            <div class=\"kksr-star\" data-star=\"1\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" data-star=\"2\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" data-star=\"3\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" data-star=\"4\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" data-star=\"5\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n    <\/div>\n    \n<div class=\"kksr-stars-active\" style=\"width: 0px;\">\n            <div class=\"kksr-star\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n            <div class=\"kksr-star\" style=\"padding-right: 5px\">\n            \n\n<div class=\"kksr-icon\" style=\"width: 24px; height: 24px;\"><\/div>\n        <\/div>\n    <\/div>\n<\/div>\n                \n\n<div class=\"kksr-legend\" style=\"font-size: 19.2px;\">\n            <span class=\"kksr-muted\">Rate this post<\/span>\n    <\/div>\n    <\/div>\n\n<p class=\"wp-block-paragraph\"><strong>Last updated: 1 October 2026<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You type <code>xm.com<\/code> into Google Chrome and the page spins forever or reports that the server cannot be found \u2014 right when you need to check a position or withdraw. In most cases <strong>XM blocked<\/strong> comes down to how your ISP handles the domain lookup, not to anything wrong with your account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The fastest way to <strong>access XM<\/strong> again is to <strong>change Chrome DNS<\/strong> to Cloudflare&#8217;s <strong>DNS 1.1.1.1<\/strong>: done inside the browser, no software to install, about two minutes. This guide covers 5 steps on desktop, how to change DNS on mobile, and what to do if you still <strong>cannot access XM<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Table of contents<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"#why-blocked\">Why is XM blocked in some countries?<\/a><\/li>\n\n\n\n<li><a href=\"#what-is-dns\">What does change Chrome DNS mean, and why does DNS 1.1.1.1 restore access?<\/a><\/li>\n\n\n\n<li><a href=\"#five-steps\">How to access XM: enable DNS 1.1.1.1 in Chrome in 5 steps<\/a><\/li>\n\n\n\n<li><a href=\"#on-mobile\">Change DNS 1.1.1.1 on Android and iPhone<\/a><\/li>\n\n\n\n<li><a href=\"#still-blocked\">Still cannot access XM? 5 things to try next<\/a><\/li>\n\n\n\n<li><a href=\"#fake-sites\">Warning: never log in on fake XM websites<\/a><\/li>\n\n\n\n<li><a href=\"#faq\">Frequently asked questions about XM blocked<\/a><\/li>\n\n\n\n<li><a href=\"#conclusion\">Conclusion<\/a><\/li>\n<\/ul>\n\n\n\n<h2 id=\"why-blocked\" class=\"wp-block-heading\">Why Is XM Blocked In Some Countries?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>XM blocked<\/strong> is usually the result of an ISP intervening at the DNS resolution layer. When you enter <code>xm.com<\/code>, your provider&#8217;s DNS server can return an empty address instead of the real IP, so the browser reports that it cannot find the server \u2014 which does not mean XM&#8217;s trading systems have stopped.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How aggressively this is applied varies by provider and by the day, so a domain may refuse to open on Wi-Fi yet load normally over mobile data. The members area at <code>my.xmglobal.com<\/code> can be affected too, because it sits on the same delivery infrastructure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How To Tell You Are Being Blocked At The DNS Layer<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can check this on Windows without installing anything: press <strong>Windows + R<\/strong>, type <code>cmd<\/code>, then run <code>nslookup xm.com<\/code> followed by <code>nslookup xm.com 1.1.1.1<\/code>. A typical result on an affected network looks like this:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Check<\/th><th>Result<\/th><\/tr><\/thead><tbody><tr><td><code>nslookup xm.com<\/code> through the ISP DNS<\/td><td>Returns <code>127.0.0.1<\/code> or <code>::1<\/code> \u2014 the query is redirected to a local address<\/td><\/tr><tr><td><code>nslookup xm.com 1.1.1.1<\/code><\/td><td>Returns a real public IP such as <code>23.15.140.102<\/code> at the time of testing<\/td><\/tr><tr><td>Conclusion<\/td><td>The domain is blocked at the DNS layer while XM&#8217;s servers are still running<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The real IP can change because XM uses content delivery infrastructure; what matters is whether your ISP&#8217;s DNS returns an empty address. If Cloudflare returns a public IP and your default DNS does not, you have identified why you <strong>cannot access XM<\/strong> in about ten seconds.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Your funds and open positions are normally unaffected<\/strong>, because MT4, MT5 and the XM app connect straight to the trading servers rather than through the web domain. If you need to manage a position urgently, see how to <a href=\"https:\/\/backcom.io\/en\/how-to-log-in-to-xm-mt4-mt5\">log in to XM on MT4\/MT5<\/a>.<\/p>\n\n\n\n<h2 id=\"what-is-dns\" class=\"wp-block-heading\">What Does Change Chrome DNS Mean, And Why Does DNS 1.1.1.1 Restore Access?<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/changing-chrome-dns-why-dns-1-1-1-1-restores-access-1024x576.png\" alt=\"What it means to change Chrome DNS and why DNS 1.1.1.1 restores access when the ISP DNS returns the wrong address\" class=\"wp-image-15911\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/changing-chrome-dns-why-dns-1-1-1-1-restores-access-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/changing-chrome-dns-why-dns-1-1-1-1-restores-access-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/changing-chrome-dns-why-dns-1-1-1-1-restores-access-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/changing-chrome-dns-why-dns-1-1-1-1-restores-access-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/changing-chrome-dns-why-dns-1-1-1-1-restores-access.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>An ISP resolver returning the wrong address causes ERR_NAME_NOT_RESOLVED; DNS 1.1.1.1 returns the right one and the connection opens again.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">DNS is the phone book of the internet: when you type <code>xm.com<\/code>, DNS finds the matching IP address so the browser can connect. Chrome uses your ISP&#8217;s resolver by default, so if that lookup is interfered with, the page will not open even though XM&#8217;s servers are running normally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To <strong>change Chrome DNS<\/strong> is simply to tell the browser to use a different resolver. Switch to Cloudflare&#8217;s <strong>DNS 1.1.1.1<\/strong> and Chrome receives the real IP instead of a tampered answer \u2014 which is why this one setting usually fixes <strong>XM blocked<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How Is Secure DNS Different From Ordinary DNS?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ordinary DNS sends queries unencrypted, so a provider can observe or modify them. Secure DNS (DNS over HTTPS, or DoH) encrypts the query, making it much harder to read or rewrite in transit. This is built into Chrome, not an extension \u2014 see the <a href=\"https:\/\/support.google.com\/chrome\/answer\/10468685\" target=\"_blank\" rel=\"noopener\">official Google Chrome documentation<\/a>. It only changes where Chrome looks up domain names; it does not touch your account, password or open orders.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is Changing DNS The Same As Using A VPN?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>No \u2014 change Chrome DNS is not the same as using a VPN.<\/strong> The two work in different ways:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Criteria<\/th><th>Changing DNS<\/th><th>VPN<\/th><\/tr><\/thead><tbody><tr><td>Main function<\/td><td>Changes the domain name resolver<\/td><td>Routes all traffic through an intermediate server<\/td><\/tr><tr><td>Changes your public IP?<\/td><td>No<\/td><td>Usually yes<\/td><\/tr><tr><td>Encrypts all traffic?<\/td><td>No \u2014 only the query, when using DoH<\/td><td>Yes<\/td><\/tr><tr><td>Effect on speed<\/td><td>Normally negligible<\/td><td>Can add latency<\/td><\/tr><tr><td>Software needed?<\/td><td>No, enabled inside Chrome<\/td><td>Usually an app<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For a failure at the domain layer, secure DNS is usually the more sensible tool than a VPN: it does not change your trading IP and you can toggle it in Chrome. Cloudflare publishes <a href=\"https:\/\/developers.cloudflare.com\/1.1.1.1\/setup\/\" target=\"_blank\" rel=\"noopener\">setup guides<\/a> for every device. Changing DNS is a common network setting, but you remain responsible for complying with the rules that apply where you are.<\/p>\n\n\n\n<h2 id=\"five-steps\" class=\"wp-block-heading\">How To Access XM: Enable DNS 1.1.1.1 In Chrome In 5 Steps<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/how-to-access-xm-enable-dns-1-1-1-1-chrome-1024x576.png\" alt=\"How to access XM by enabling Cloudflare DNS 1.1.1.1 in Chrome in 5 steps\" class=\"wp-image-15914\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/how-to-access-xm-enable-dns-1-1-1-1-chrome-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/how-to-access-xm-enable-dns-1-1-1-1-chrome-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/how-to-access-xm-enable-dns-1-1-1-1-chrome-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/how-to-access-xm-enable-dns-1-1-1-1-chrome-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/how-to-access-xm-enable-dns-1-1-1-1-chrome.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>How to access XM: turn on secure DNS and pick Cloudflare 1.1.1.1 inside Chrome settings.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If <strong>XM blocked<\/strong> is caused by your ISP&#8217;s resolver returning the wrong address, you switch to Cloudflare inside Chrome settings in about two minutes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you would rather watch it done first, the video below walks through how to reach a website when the connection is being blocked:<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"H\u01b0\u01a1\u0301\u0301ng D\u00e2\u0303n Truy C\u00e2\u0323p Website Khi Bi\u0323 Ch\u0103\u0323n K\u00ea\u0301t N\u00f4\u0301i | Backcom Insight | Backcom.io\" width=\"800\" height=\"450\" src=\"https:\/\/www.youtube.com\/embed\/33YdMP0W4WE?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><figcaption class=\"wp-element-caption\"><em>How to reach a website when the connection is blocked \u2014 Backcom Insight.<\/em><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Open Chrome Settings<\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-1-open-settings-1024x576.png\" alt=\"Change Chrome DNS step 1: open the three-dot menu in the top right and choose Settings\" class=\"wp-image-15917\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-1-open-settings-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-1-open-settings-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-1-open-settings-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-1-open-settings-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-1-open-settings.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Step 1: click the three-dot menu in the top right, then choose Settings.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Click the <strong>three-dot<\/strong> icon in the top right and choose <strong>Settings<\/strong>. Faster: type <code>chrome:\/\/settings<\/code> straight into the address bar and press <strong>Enter<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Go To Privacy And Security<\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-2-open-security-1024x576.png\" alt=\"Change Chrome DNS step 2: choose Privacy and security, then click Security\" class=\"wp-image-15920\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-2-open-security-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-2-open-security-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-2-open-security-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-2-open-security-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-2-open-security.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Step 2: open Privacy and security in the left menu, then click Security.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In the left-hand menu, select <strong>Privacy and security<\/strong>, then click <strong>Security<\/strong>. This is where Chrome&#8217;s DNS provider is managed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Turn On Use Secure DNS<\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-3-enable-secure-dns-1024x576.png\" alt=\"Change Chrome DNS step 3: switch on Use secure DNS under the Advanced section\" class=\"wp-image-15923\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-3-enable-secure-dns-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-3-enable-secure-dns-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-3-enable-secure-dns-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-3-enable-secure-dns-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/change-chrome-dns-step-3-enable-secure-dns.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Step 3: scroll to Advanced and switch on Use secure DNS.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Scroll down to <strong>Advanced<\/strong>, find <strong>Use secure DNS<\/strong> and turn the toggle on if it is off. With it enabled, Chrome encrypts domain lookups instead of sending them straight through your ISP&#8217;s default resolver.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Select Cloudflare (1.1.1.1)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Click <strong>With<\/strong> or <strong>Choose another provider<\/strong> depending on your Chrome version, then pick <strong>Cloudflare (1.1.1.1)<\/strong>. If Chrome asks for a custom entry, use <code>https:\/\/cloudflare-dns.com\/dns-query<\/code>. The setting saves automatically.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Close Settings And Reload The XM Website<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Open a new tab and type XM&#8217;s official domain. If you still see the old error, close every Chrome window and reopen it to drop the cached DNS result, or press <strong>Ctrl + Shift + R<\/strong> to reload the page without cache.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Check Whether DNS 1.1.1.1 Is Actually Working<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Check online:<\/strong> open <a href=\"https:\/\/one.one.one.one\/help\/\" target=\"_blank\" rel=\"noopener\">Cloudflare&#8217;s connection test page<\/a>. If <strong>Connected to 1.1.1.1<\/strong> shows <strong>Yes<\/strong>, you are on Cloudflare; <strong>No<\/strong> means Chrome has not applied the setting or a network policy is overriding it. <strong>Using DNS over HTTPS (DoH): Yes<\/strong> confirms the query is encrypted.<\/li>\n\n\n\n<li><strong>Check in Command Prompt:<\/strong> run <code>nslookup xm.com 1.1.1.1<\/code>. A public IP instead of <code>127.0.0.1<\/code> means Cloudflare resolved the domain successfully.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">On a machine managed by an employer or a school, the secure DNS option may be locked. Do not try to override the system policy \u2014 use a personal device, switch to mobile data, or ask your administrator to look into it.<\/p>\n\n\n\n<h2 id=\"on-mobile\" class=\"wp-block-heading\">Change DNS 1.1.1.1 On Android And iPhone<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/switch-to-dns-1-1-1-1-android-iphone-1024x576.png\" alt=\"Change DNS 1.1.1.1 on Android and iPhone to access XM more reliably\" class=\"wp-image-15926\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/switch-to-dns-1-1-1-1-android-iphone-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/switch-to-dns-1-1-1-1-android-iphone-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/switch-to-dns-1-1-1-1-android-iphone-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/switch-to-dns-1-1-1-1-android-iphone-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/switch-to-dns-1-1-1-1-android-iphone.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Android has a Private DNS setting; on iPhone you configure DNS manually under Wi-Fi.<\/em><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">On Android<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In Chrome for Android the steps to <strong>change Chrome DNS<\/strong> mirror the desktop version: <strong>three dots<\/strong> \u2192 <strong>Settings<\/strong> \u2192 <strong>Privacy and security<\/strong> \u2192 <strong>Use secure DNS<\/strong> \u2192 <strong>Choose another provider<\/strong> \u2192 <strong>Cloudflare (1.1.1.1)<\/strong>. Then close Chrome, reopen it and load XM&#8217;s official domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That setting applies to Chrome only. To put the whole device on Cloudflare, go to <strong>Settings \u2192 Network and internet<\/strong> (or <strong>Connections<\/strong>) \u2192 <strong>Private DNS<\/strong> \u2192 <strong>Private DNS provider hostname<\/strong>, enter <code>one.one.one.one<\/code> and tap <strong>Save<\/strong>. Menu names vary by manufacturer. This covers other apps too, which helps when <strong>XM blocked<\/strong> is not limited to the browser.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">On iPhone<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">iPhone does not let you pick Cloudflare directly inside Chrome. You have two options:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The Cloudflare app:<\/strong> install the <a href=\"https:\/\/one.one.one.one\/\" target=\"_blank\" rel=\"noopener\">1.1.1.1 app<\/a> from the App Store and switch the connection on. It may ask permission to add a VPN configuration \u2014 that is the technical mechanism for routing DNS traffic through Cloudflare. Download only from the App Store and check the publisher.<\/li>\n\n\n\n<li><strong>Set Wi-Fi DNS manually:<\/strong> <strong>Settings \u2192 Wi-Fi<\/strong> \u2192 the <strong>(i)<\/strong> icon next to your network \u2192 <strong>Configure DNS<\/strong> \u2192 switch to <strong>Manual<\/strong> \u2192 add <code>1.1.1.1<\/code> and <code>1.0.0.1<\/code> \u2192 <strong>Save<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A manual configuration applies only to the Wi-Fi network you just edited, not to mobile data, and has to be repeated on every new network. If you still <strong>cannot access XM<\/strong>, try switching to mobile data: if the page opens over 4G, the problem is the Wi-Fi network you were on.<\/p>\n\n\n\n<h2 id=\"still-blocked\" class=\"wp-block-heading\">Still Cannot Access XM? 5 Things To Try Next<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If <strong>DNS 1.1.1.1<\/strong> is on and you still <strong>cannot access XM<\/strong>, the cause may be a cache, a network configuration, or the account itself. Work through these in order, from the simplest \u2014 do not rush to install a VPN or click an unverified XM link.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Flush The DNS Cache And The Browser Cache<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Windows and Chrome may still be using an old DNS answer. Open <strong>Command Prompt<\/strong>, run <code>ipconfig \/flushdns<\/code>, then close every Chrome window and reopen it. Next, try XM in an incognito window (<strong>Ctrl + Shift + N<\/strong>): if that works, the cause is a cookie, the cache or an extension.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Use Cloudflare&#8217;s 1.1.1.1 App<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">To <strong>change Chrome DNS<\/strong> affects the browser only. If Firefox, Edge or the XM app fail too, use the 1.1.1.1 app to apply Cloudflare device-wide: try the plain <strong>1.1.1.1<\/strong> mode first, and only then <strong>WARP<\/strong>. WARP handles a wider range of traffic, so it can alter your route and latency \u2014 do not toggle it while an order is being placed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Change DNS At The Operating System Or Router Level<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When every device on the same network fails, a Chrome-only setting is not enough. On Windows 11: <strong>Settings \u2192 Network and internet<\/strong> \u2192 select the <strong>Wi-Fi<\/strong> or <strong>Ethernet<\/strong> connection \u2192 <strong>DNS server assignment<\/strong> \u2192 <strong>Edit<\/strong> \u2192 <strong>Manual<\/strong> \u2192 preferred DNS <code>1.1.1.1<\/code>, alternate DNS <code>1.0.0.1<\/code> \u2192 save and reconnect.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Changing DNS on the router suits a whole household or office, but it needs admin access and you should write down the old configuration first. If the router is managed by your ISP, contact their technical support rather than editing it yourself.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Use MT4, MT5 Or The XM App In The Meantime<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A website that will not open does not mean the trading servers are down. MT4, MT5 and the XM app still connect while <strong>XM blocked<\/strong> applies only to the web domain, so you can watch prices, adjust Stop Loss and Take Profit, and close positions. Deposits, withdrawals and identity verification still need the members area.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Other brokers run into the same thing \u2014 see <a href=\"https:\/\/backcom.io\/en\/exness-blocked-access-dns-1-1-1-1-chrome\">Exness blocked and how to access it with DNS 1.1.1.1<\/a> for another worked example of diagnosing a domain-layer failure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Contact XM Support<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the XM site opens on another device but your account will not sign in, the cause may be a wrong password, a verification requirement or scheduled maintenance. Contact support through official channels and include a screenshot of the error, the ISP you are on, and the output of <code>nslookup xm.com<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Never send your password, two-factor code or an OTP to anyone \u2014 legitimate support staff do not need any of those to investigate why you <strong>cannot access XM<\/strong>.<\/p>\n\n\n\n<h2 id=\"fake-sites\" class=\"wp-block-heading\">Warning: Never Log In On Fake XM Websites<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/fake-xm-websites-warning-1024x576.png\" alt=\"Warning about fake XM websites while XM is blocked: comparing the official xm.com domain with lookalike domains\" class=\"wp-image-15929\" srcset=\"https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/fake-xm-websites-warning-1024x576.png 1024w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/fake-xm-websites-warning-300x169.png 300w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/fake-xm-websites-warning-768x432.png 768w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/fake-xm-websites-warning-1536x864.png 1536w, https:\/\/backcom.io\/wp-content\/uploads\/2026\/10\/fake-xm-websites-warning.png 1672w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>While XM is blocked, fake sites surface quickly \u2014 always check the domain before you log in.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">When <strong>XM blocked<\/strong> hits, a lot of people search for a \u201cnew XM link\u201d or click something shared in a Telegram, WhatsApp or Facebook group. That is exactly when fake sites reach the most users: attackers register a lookalike domain, copy the login screen, and harvest credentials.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Signs Of A Fake XM Website<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A domain with extra characters, a misspelling or an unusual extension.<\/li>\n\n\n\n<li>A page claiming to be a \u201cbackup XM link\u201d that appears nowhere on official channels, or that asks you to re-enter your password and OTP repeatedly.<\/li>\n\n\n\n<li>Someone claiming to be XM staff or an IB who sends a login link, asks for remote control of your computer, or wants a transfer to a personal account.<\/li>\n\n\n\n<li>An XM app delivered as an installer file from outside the App Store or Google Play.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A polished design and an HTTPS certificate prove nothing \u2014 a fake can display the padlock and the XM logo too. Cross-check the licence and the support channels as well; our <a href=\"https:\/\/backcom.io\/en\/reputable-forex-broker-7-criteria\">criteria for choosing a reputable forex broker<\/a> cover the signals that expose a lack of transparency.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Rules For Accessing XM Safely<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once you have changed DNS and can <strong>access XM<\/strong> again: type the official domain yourself rather than clicking links in ads or messages, bookmark it after you have confirmed the site, read the full address up to the first slash, enable two-factor authentication, and install apps only from the official stores.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you suspect you have just logged in on a fake site, close the page immediately, change the password on your members area and the linked email, reset two-factor authentication, review your login history and withdrawal requests, then report it to XM support. If you downloaded a file from that site, run a malware scan and change the password anywhere you reused it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For background on the broker&#8217;s regulation and safety record, read <a href=\"https:\/\/backcom.io\/en\/is-xm-legit\">Is XM legit?<\/a> before you go any further.<\/p>\n\n\n\n<h2 id=\"faq\" class=\"wp-block-heading\">Frequently Asked Questions About XM Blocked<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is It Legal And Safe To Change Chrome DNS?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Changing DNS is a built-in Chrome setting that only swaps the domain name resolver; it does not hide your IP the way a VPN does. To stay safe, pick a reputable provider such as Cloudflare, avoid DNS servers of unknown origin, and make sure you comply with the rules that apply where you live.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does DNS 1.1.1.1 Slow Down My Internet?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Normally no, because DNS is only used during the address lookup; in some cases pages even open faster thanks to a nearby Cloudflare server. If the connection behaves oddly, try the backup resolver <code>1.0.0.1<\/code> or revert to the default configuration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does XM Blocked Affect My Funds And Open Positions?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Normally not. When <strong>XM blocked<\/strong> happens at the DNS layer, it mainly affects opening the website and the members area. MT4, MT5 and the trading apps connect to separate servers, so open positions, Stop Loss, Take Profit and your balance continue to be handled as usual.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">I Changed DNS And Still Cannot Access XM \u2014 What Now?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Close Chrome completely, run <code>ipconfig \/flushdns<\/code> and try again in an incognito window. Then switch from Wi-Fi to mobile data, or use the 1.1.1.1 app, to work out whether the problem is your device or your ISP. If the website opens but your account will not sign in, contact XM support.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I Have To Change DNS Every Time I Open XM?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Once you <strong>change Chrome DNS<\/strong>, the browser stores the configuration and keeps using the provider you selected. You only need to set it again after a fresh install or a Chrome reset, or when you move to a different computer. The manual iPhone method is the exception: it applies per Wi-Fi network, so it has to be redone on each new network.<\/p>\n\n\n\n<h2 id=\"conclusion\" class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>XM blocked<\/strong> is usually an ISP intervening at the domain resolution layer, not a problem with your account or the trading servers. The quickest way to <strong>access XM<\/strong> again is to enable Cloudflare&#8217;s <strong>DNS 1.1.1.1<\/strong> in Chrome using the 5 steps above, then flush the DNS cache if the browser is still holding the old answer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">While you are fixing it, only ever log in through the official domain and the official apps \u2014 never through an \u201cunblocked XM link\u201d from an unverified source. If you already trade with XM, you can look at <a href=\"https:\/\/backcom.io\/en\/broker\/xm\">XM cashback through Backcom<\/a> to cut part of the cost of every trade. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>XM blocked and the site will not load? The cause is usually the DNS layer. Here is how to access XM with Cloudflare DNS 1.1.1.1 on Chrome, Android and iPhone, plus how to spot a fake XM site.<\/p>\n","protected":false},"author":8,"featured_media":15908,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_eb_attr":"","footnotes":""},"categories":[178,205],"tags":[765,766],"class_list":["post-15846","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-insight","category-xm","tag-dns-1-1-1-1-en","tag-xm-blocked"],"acf":[],"views":2,"_links":{"self":[{"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/posts\/15846","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/comments?post=15846"}],"version-history":[{"count":2,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/posts\/15846\/revisions"}],"predecessor-version":[{"id":15933,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/posts\/15846\/revisions\/15933"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/media\/15908"}],"wp:attachment":[{"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/media?parent=15846"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/categories?post=15846"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/backcom.io\/en\/wp-json\/wp\/v2\/tags?post=15846"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}