Is a Website Down or Just Me?
When one website will not open, the failure can be at the website, DNS, your browser, your device, your network, your provider, a regional CDN, or your account. A few controlled comparisons can narrow it down quickly.
Six-step quick check
- Check the domain with the NetworkCheck website checker.
- Reload once, then try a private/incognito window.
- Try another website.
- Try another device on the same network.
- Try cellular data or another Wi-Fi network.
- Read the exact browser error before changing settings.
What the NetworkCheck website checker actually checks
The tool performs a DNS-based lookup to see whether the domain resolves. That is useful because a domain that does not resolve cannot normally be reached by name. But a successful DNS result does not prove that every page, login, API, or regional server is working.
It can help identify
- A domain that currently returns DNS records.
- A domain that does not appear to resolve.
- Basic lookup timing and the time of the check.
It cannot prove
- That the web application is healthy.
- That your account can log in.
- That the service works in every country.
- That a CDN or specific page path is available.
- That your ISP or workplace is not blocking it.
Step-by-step troubleshooting checklist
1. Record the exact error
Do not reduce every failure to “it is down.” A DNS error, timeout, certificate warning, 403, and 503 point in different directions.
2. Test another site
If no websites open, troubleshoot the connection. If everything except one site works, focus on that domain, browser data, DNS, routing, or account.
3. Use a private window
A private window reduces the effect of stored cookies and some extensions. If the site works privately, clear that site’s cookies/cache or disable extensions one at a time.
4. Try another device on the same network
If another device works, the issue is local to the first device or browser. If both fail, the network, DNS, provider route, or site is more likely.
5. Try another network
Turn off Wi-Fi on a phone and try cellular data. If the site works on cellular but not home Wi-Fi, investigate the router, DNS, provider, filtering, or public-IP reputation.
6. Check DNS
Use the site checker. If DNS fails only on your network, restart the router and follow the DNS cache guide.
7. Check official service information
Look for the company’s status page or support channel. Treat social-media reports as supporting evidence, not proof; old posts and unrelated local problems can be misleading.
What common browser and HTTP errors mean
| Error or symptom | What it usually indicates | Useful next step |
|---|---|---|
DNS_PROBE_FINISHED_NXDOMAIN | The name did not resolve | Check spelling, DNS records, cache, router, and resolver. |
ERR_NAME_NOT_RESOLVED | Browser could not obtain an address | Use the DNS checklist and another network. |
ERR_CONNECTION_TIMED_OUT | No timely response from destination/path | Try another network; check server, route, firewall, and provider. |
ERR_CONNECTION_REFUSED | Destination actively rejected the connection | Server service, firewall, port, or local security software may be involved. |
| 401 Unauthorized | Authentication is required or failed | Sign in again; check account and credentials. |
| 403 Forbidden | Server understood but denied the request | Check login, permissions, VPN, region, IP block, or security policy. |
| 404 Not Found | The server is up but that path is missing | Open the home page or correct the URL. |
| 429 Too Many Requests | Rate limit or temporary abuse protection | Wait, stop repeated refreshes, or sign in. |
| 500 Internal Server Error | Application/server failure | Usually wait or contact the site owner. |
| 502 / 503 / 504 | Gateway, overload, maintenance, or upstream timeout | Check official status and retry later. |
| Certificate/privacy warning | TLS certificate, clock, interception, or hostname issue | Check device date/time; do not bypass warnings on sensitive sites. |
Interpret what your comparisons show
- Fails on every device and every network: likely site, DNS, or broad service outage.
- Fails only on home Wi-Fi: router, DNS, ISP route, filter, or public-IP block.
- Fails only on one device: browser cache, extension, device DNS, security software, or clock.
- Fails only when signed in: account, session, permissions, or user-specific application issue.
- Home page works, one page fails: bad link, removed content, API failure, or page-specific permissions.
- Works with VPN but not without it: regional routing, DNS, ISP filtering, or IP reputation may be involved.
- Fails with VPN but works without it: VPN endpoint, geoblocking, or anti-abuse filtering.
Regional outages and CDNs
Large sites often use many data centers and content-delivery locations. A service can work in one city and fail in another. DNS can also direct different users to different regional endpoints. That is why reports from a distant friend do not always match your result.
Work, school, hotel, and public networks
Managed networks can block categories, ports, VPNs, file-sharing services, or newly registered domains. A 403 page or branded block page may be intentional policy rather than an outage. Do not bypass workplace or school controls; contact the network administrator if access is required.
When to wait, contact the site, or contact your provider
- Wait and retry: 429, 500, 502, 503, 504, maintenance notice, or widespread official incident.
- Contact the website: account-specific failure, broken page, incorrect 403, payment issue, or persistent application error.
- Contact your ISP: multiple sites fail, wired connection is unstable, DNS/routing problems affect every device, or failures are specific to the provider.
- Contact your network administrator: failure occurs only on a managed work, school, or guest network.
Frequently asked questions
Can a website be up but still not work for me?
Yes. Your DNS, route, region, browser, account, public IP, or local filter can fail while the service remains available to other users.
Does a successful ping prove the website is up?
No. Many servers block ping, and a server can answer network requests while the web application is broken.
Should I clear all browser data?
Start with a private window and site-specific cookies/cache. Clearing everything can sign you out of many services and is often unnecessary.
Why does the site work on my phone but not my computer?
The phone may be using cellular data, a different DNS resolver, different browser state, or a different route. Compare the phone on the same Wi-Fi to isolate the difference.