DNS failure vs website outage

Last updated: 1 September 2026

“Site not found” can mean two very different failures. DNS might be broken so the name never maps to a server, or DNS might work fine while the server refuses connections. Confusing the two sends you down the wrong fix path.

DNS failure

DNS translates a hostname like example.com into an IP address. When DNS fails:

Common causes include expired domains, broken nameserver glue, registrar outages, and local resolver cache pointing at stale data. If only your network fails while isitdown.me succeeds, flush local DNS or try another resolver before assuming global DNS breakage.

Website outage (DNS OK)

When DNS resolves but the site still fails, the problem sits further along the path:

On isitdown.me you will see an IP was resolved and usually an HTTP code or timing figure. That pattern confirms DNS worked at check time.

Side-by-side comparison

Practical steps

  1. Run a check on the homepage.
  2. Read whether DNS succeeded and note the status label.
  3. If we say UP and you disagree, test another network or read everyone vs just you.
  4. If we say DOWN with DNS failure, wait for registrar/DNS propagation or verify nameserver records with your provider.

FAQ

Can DNS work for you but fail for me? Yes. Resolvers cache answers for different TTLs. Propagation after DNS edits is a frequent source of “works on my phone, not on Wi-Fi”.

Does a CDN change this? CDNs still rely on DNS. A DNS answer might point at an edge node that is healthy while your resolver serves an old address. External checks help spot that gap.

Check a domain now on isitdown.me.

Check a domain

Run a live reachability check on the isitdown.me homepage, or open a saved status page at /your-domain.com.

All guides · Back to home