Google Chrome Archives

BROWSER ADMINISTRATION · REVISED JULY 2026 · 25 MIN READ HOW-TO GUIDE · CHROME How to Fix "TLD Is Not Supported" Error in Google Chrome: Step-by-Step Chrome has its own hidden DNS resolver, HSTS preload list, and Secure DNS (DoH) engine. When Chrome rejects a TLD, standard Windows fixes won't work. Learn the exact internal settings to modify to restore access. JOY DUTTA · JULY 2026 Key Takeaways 1 Independent DNS: Google Chrome does not always use the Windows DNS client. It has its own internal asynchronous DNS resolver and cache. 2 Secure DNS (DoH): If "Use Secure DNS" is enabled, Chrome encrypts requests directly to Google or Cloudflare, bypassing your corporate firewall/DNS. 3 The .dev / .app Problem: Google owns these TLDs and forces them onto the HSTS preload list. If the site lacks a valid SSL cert, Chrome will block it instantly. 4 Internal Tools: You can clear Chrome's specific DNS cache by visiting the hidden diagnostic page at `chrome://net-internals/#dns`. Quick Navigation Introduction What Is The TLD Error in Chrome? Why Does Chrome Block Certain TLDs? How TLD Validation Works in Chrome Core Components (Secure DNS, HSTS) Workflow / Diagram Step-by-Step Fixes Advantages of Fixing Locally Best Practices for Chrome DNS Common Mistakes Admins Make FAQs Summary Introduction You have flushed your Windows DNS, checked your HOSTS file, and verified that your router is working perfectly. Yet, Google Chrome still adamantly refuses to load a .app or .dev website, displaying an error stating the site cannot be reached. Unlike older browsers, Google Chrome operates almost like its own miniature operating system. It bypasses many of the standard Windows networking layers to optimize speed and enforce strict security. To fix a TLD error in Chrome, you have to look under Chrome's hood. New to this error? Read our complete guide: What Is TLD Is Not Supported Error? (Complete Guide) 💡 REAL-WORLD ADMIN TIP Don't confuse clearing your browsing history (cache and cookies) with clearing Chrome's DNS cache. Pressing Ctrl+Shift+Del and wiping history will NOT fix a TLD resolution error. You must use the specific `chrome://net-internals` diagnostic page. What Is The TLD Error in Chrome? In Chrome, the "TLD Is Not Supported" error rarely says those exact words. Instead, it masks itself behind specific network error codes. If Chrome's internal validation rejects the TLD or cannot securely verify it, it will usually throw one of the following codes. TABLE 1: CHROME ERROR CODES FOR TLD FAILURES Chrome Error Code What Chrome is Actually Saying ERR_NAME_NOT_RESOLVED Chrome's internal DNS or Secure DNS failed to find the TLD in the root zone. ERR_CERT_AUTHORITY_INVALID The TLD mandates HTTPS (like .dev), but the site presented a self-signed or invalid cert. ERR_CONNECTION_REFUSED The TLD resolved, but a proxy extension (like a VPN/Adblocker) forcibly blocked it. Why Does Chrome Block Certain TLDs? Chrome is the most aggressive browser on the market regarding security. If an enterprise uses an internal domain like server.local, Chrome may block it or redirect it to a Google search. Chrome assumes that standard words without a recognized ICANN TLD are search queries, not domains. ❌ COMMON MISTAKE If you type an internal domain like `intranet` or `hr-portal` and Chrome redirects to Google Search, do not change your DNS settings. Chrome just didn't recognize it as a TLD. To force Chrome to treat it as a domain, you must append a trailing slash: `http://intranet/`. How TLD Validation Works in Chrome When you press Enter, Chrome performs a parallel resolution race. It checks its internal memory cache, consults its HSTS preload list to see if the TLD requires encryption, and simultaneously queries the DNS server. If Secure DNS (DoH) is enabled, it completely bypasses your Windows network adapter settings. Core Components TABLE 2: CRITICAL CHROME DIAGNOSTIC PAGES Internal URL Purpose for Troubleshooting TLDs chrome://net-internals/#dns Shows you Chrome's secret DNS cache and provides a button to clear it. chrome://net-internals/#hsts Allows you to query if a domain is on the strict HTTPS preload list, and delete local HSTS policies. chrome://policy Shows if your IT department is enforcing Group Policies that break specific TLDs. Workflow / Diagram The flowchart below illustrates how Chrome can fail to resolve a TLD even if Windows is configured correctly. Diagram: Chrome's Independent DNS Path graph TD Type --> DoH{Is Secure DNS Enabled?} DoH -->|Yes| Google DoH -->|No| Windows Google -->|Corporate Firewall blocks DoH| Err1 Google -->|Success| Load Windows -->|Standard Resolution| Load style Type fill:#e1d5c9,stroke:#0f0e0c style DoH fill:#1d3557,stroke:#0f0e0c,color:#fff style Google fill:#ede7d6,stroke:#0f0e0c style Windows fill:#ede7d6,stroke:#0f0e0c style Err1 fill:#c8392b,stroke:#0f0e0c,color:#fff style Load fill:#1a6b4a,stroke:#0f0e0c,color:#fff Step-by-Step Fixes Step 1: Clear Chrome's Internal DNS Cache Chrome caches negative DNS lookups for a very long time to save processing power. In the Chrome address bar, type: chrome://net-internals/#dns and press Enter. Click the Clear host cache button. (There is no confirmation prompt; clicking it once is enough). Next, click on Sockets in the left-hand menu (or navigate to chrome://net-internals/#sockets). Click Flush socket pools. 💡 REAL-WORLD ADMIN TIP Before digging into complex settings, open an Incognito Window (Ctrl+Shift+N). Incognito disables most extensions. If the TLD loads perfectly in Incognito, an extension (usually an Adblocker or Privacy Badger) is aggressively blocking the TLD. Step 2: Disable Secure DNS (DoH) Secure DNS (DNS over HTTPS) encrypts your DNS traffic. However, if your corporate network uses a custom internal DNS server to route traffic, Chrome's Secure DNS will bypass it entirely, resulting in resolution failures for internal TLDs. Click the three dots in the top right and select Settings. Click Privacy and security on the left, then click Security. Scroll down to the Advanced section and find Use secure DNS. Toggle it OFF, or switch the provider from "Custom" to "With your current service provider". TABLE 3: SECURE DNS (DoH) COMPARISON DNS Mode in Chrome How it routes TLDs Impact on Enterprise Off (Current Provider) Uses Windows Network Adapter Settings Ideal for office networks. Resolves internal domains correctly. On (Cloudflare/Google) Direct encrypted tunnel to public DNS Breaks internal portals. High privacy, low enterprise compatibility. Step 3: Clear Local HSTS Security Policies If a site was previously enforcing strict HTTPS, and that configuration broke, Chrome will aggressively block the domain without giving you the "Proceed Anyway" button. Go to chrome://net-internals/#hsts. Scroll to the bottom where it says Delete domain security policies. Enter the exact domain name (e.g., portal.dev) and click Delete. ⚠️ SECURITY NOTE You cannot delete HSTS policies for domains that are on Google's hardcoded preload list (like .dev and .app). If the site owner does not install a valid SSL certificate on those TLDs, Chrome will never load them. Period. Common Mistakes Admins Make Reinstalling Chrome is almost never the correct solution for a TLD error. Because Chrome syncs settings via your Google Account, if you uninstall Chrome and reinstall it, the moment you log back in, Google Sync will pull down the exact same corrupted DNS settings and extensions, and the error will return immediately. Focus on the internal network diagnostics instead. FAQs Why does it work in Edge but not Chrome? Even though Edge is based on Chromium, Microsoft and Google enforce different default policies for Secure DNS and HSTS preload lists. A site might fail in Chrome but pass Edge's slightly different validation engine. Summary When Chrome refuses to support a TLD, standard Windows network troubleshooting will rarely solve the problem. You must operate within Chrome's ecosystem by clearing its dedicated net-internals DNS cache, verifying Secure DNS routing rules, and ensuring HSTS security policies aren't forcibly dropping the connection. © 2026 · ALL RIGHTS RESERVED GOOGLE CHROME HOW-TO FIX DNS DIAGNOSTICS

How to Fix “TLD Is Not Supported” Error in Google Chrome

Categories