DNS_PROBE_FINISHED_NXDOMAIN in Chrome: Check the Address and DNS

Type the website address again, checking the hostname’s spelling and its ending, such as .com. Try another known website. If only one domain fails across devices and networks, send the domain and exact error to the site owner. Avoid following lookalike addresses suggested as a workaround, especially for a sign-in or payment page.

Open the same address in another browser, then try a different network you trust if available. A phone hotspot can use mobile data. If the site works elsewhere, note which combination fails. On public Wi-Fi, finish the network’s sign-in process first. The comparison helps separate a browser setting from a network or website issue.

On desktop Chrome, open Settings > Privacy and security > Security. Under Advanced, find Use secure DNS. If a custom provider is selected, record it before trying the current service provider or another available provider. Reload the affected site after each change. Chrome’s automatic mode can fall back to an unencrypted lookup; a custom provider does not use that fallback. Managed devices and parental controls can restrict this setting, so ask the administrator if it is unavailable.

Update and restart Chrome, then compare the address in an Incognito window. If it works there, investigate extensions rather than deleting all browsing data immediately. If you change operating-system DNS later, record the previous settings so you can restore them. Give support the domain, error code, affected devices, and whether another network works. Do not turn off certificate warnings or your firewall to resolve a domain lookup error.