Home › Web & HTTP

ERR_NAME_NOT_RESOLVED — how to fix

This site can't be reached
Check if there is a typo in example.com.
DNS_PROBE_FINISHED_NXDOMAIN
net::ERR_NAME_NOT_RESOLVED

Quick fix: Check the hostname for typos, then test with nslookup example.com 1.1.1.1. If public DNS resolves it, flush your local cache (ipconfig /flushdns on Windows, sudo resolvectl flush-caches on Linux, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS) and fix your DNS server. If nobody resolves it, add or fix the DNS record.

What it means

Before connecting, the browser asks DNS for the IP of the hostname. ERR_NAME_NOT_RESOLVED (often shown with DNS_PROBE_FINISHED_NXDOMAIN) means that lookup returned "no such domain" or nothing at all. No connection to the server was ever attempted, so it's not a server/firewall problem.

In the console of a web app you may see it as GET https://api.example.com/... net::ERR_NAME_NOT_RESOLVED for a single request; the same causes apply to that API hostname.

Step 1: is it only you?

nslookup example.com            # your configured DNS
nslookup example.com 1.1.1.1    # Cloudflare public DNS
dig +short example.com @8.8.8.8 # Google public DNS

Cause 1: typo or wrong hostname

Check spelling, the TLD (.com vs .co), and for apps the config: an env var like API_URL=https://api.exmple.com or a leftover localhost-style internal hostname (e.g. a Docker service name like http://backend:8000 used from the browser, which only resolves inside the Docker network - use the public URL or a dev-server proxy).

Cause 2: the DNS record doesn't exist (yet)

For your own domain:

Cause 3: stale local DNS cache

Flush it, then restart the browser:

# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux (systemd-resolved)
sudo resolvectl flush-caches

Chrome has its own cache: open chrome://net-internals/#dns and click Clear host cache.

Cause 4: broken or blocking DNS server

Your router/ISP resolver may be down or filtering. Switch to a public resolver (1.1.1.1, 8.8.8.8):

Also check:

Cause 5: hosts file entries

A wrong or leftover entry overrides DNS:

Remove lines for the hostname you're trying to reach.

Cause 6: no network at all

If every site fails with this, you're probably offline or connected to a captive portal (hotel/airport Wi-Fi). Open http://neverssl.com to trigger the login page.

Last updated 2026-11-17.