Home / Error Lookup / DNS-PROBE-FINISHED-NXDOMAIN

DNS-PROBE-FINISHED-NXDOMAIN

Network DNS_PROBE_FINISHED_NXDOMAIN Applies to: Windows 7, Windows 10, Windows 11

What it means

The browser couldn't resolve a website's address at all — the DNS lookup found nothing, which usually points to your DNS settings or the site being genuinely down.

Also seen as: DNS_PROBE_FINISHED_NXDOMAIN

Quick fix steps

  1. Check if the site loads on your phone using mobile data — if not, the site itself is likely down.
  2. Flush DNS with "ipconfig /flushdns" from an admin Command Prompt.
  3. Try a public DNS server (8.8.8.8 or 1.1.1.1) in your network adapter settings.
For the full step-by-step walkthrough, see "No Internet Access" With Wi-Fi Connected.

Frequently Asked Questions

Does this mean the website doesn't exist?
It can mean that, but it more often means your DNS lookup specifically failed to resolve the name, even if the site exists and works fine for others — checking your DNS settings is the right first step.
Why does this happen on some sites but not others?
If it's isolated to specific sites, those particular domains may genuinely be down or have DNS issues on their end — if it happens broadly across many sites, the problem is more likely your own DNS configuration.

Other error codes

0X80072EFD — A Connection with the Server Could Not Be Established

A general connectivity failure reaching a Microsoft service — usually your network, a firewall, or a proxy/VPN blocking the connection.

0X80070424 — A Required Service Cannot Be Started

A Windows service the current task depends on (often related to Windows Update, Security Center, or networking) isn't running.

0X80072EE7 — Store/Update Connection Timed Out

A connection to Microsoft's servers timed out — usually a network stability issue or DNS problem.

ERR-CONNECTION-TIMED-OUT — ERR_CONNECTION_TIMED_OUT

Your browser sent a request but got no response in time — could be the site, your firewall, or your connection.