# Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN

**Code:** `DNS_PROBE_FINISHED_NXDOMAIN` · **Category:** Browser · **Seen on:** Chrome, Edge, Windows, macOS

The DNS server answered that the domain name does not exist (NXDOMAIN) — a typo, an expired or unregistered domain, a missing DNS record, or a stale DNS cache.

## Meaning

Unlike a timeout, DNS replied clearly: no such name. Check spelling first, then whether the domain is registered and has A/AAAA/CNAME records. If it works on other devices or networks, flush the local DNS cache or change DNS servers.

## Common causes

- Typo in the domain or a missing `www`/subdomain record
- Domain expired, not yet registered or nameservers not delegated
- DNS records missing or recently changed (propagation)
- Stale local DNS cache or hosts file entry
- ISP/router DNS problem

## Quick fix

1. Check the spelling and test with `nslookup example.com 8.8.8.8`
2. Flush DNS cache: `ipconfig /flushdns` (Windows) / `sudo dscacheutil -flushcache` (macOS)
3. Owners: verify nameservers and records at the registrar

## Detailed fix by platform

### Windows

1. `ipconfig /flushdns` then `netsh winsock reset`; set DNS to 1.1.1.1 / 8.8.8.8 in the adapter settings

### macOS

1. `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`

### Linux

1. `resolvectl flush-caches` and `dig example.com +short`

## Code examples

### Is it DNS?

```bash
nslookup example.com            # your resolver
nslookup example.com 8.8.8.8    # public resolver
dig NS example.com +short       # are the nameservers set?
```

## How to diagnose

1. **Name** — Spelled correctly?
2. **Resolvers** — Does a public DNS resolve it?
3. **Records** — A/AAAA/CNAME present at the DNS host?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/browser/dns-probe-finished-nxdomain)