New

The new HostCloud is live. Web Hosting for ₹1 for your first month.

Web Hosting for ₹1 · first month

Claim offerClaim
Hosting & Performance

Is your website down for everyone or just you? How to check in two minutes

A site that will not load is not always a site that is down. Here is a quick way to tell whether the problem is your device, your network, DNS or the server, and what to do next in each case.

2 November 2026 · 8 min read
Is your website down for everyone or just you? How to check in two minutes

Is your website down for everyone or just you? How to check in two minutes

TL;DR: When a site will not load, test from somewhere else before you panic. Try it on mobile data, try an independent status checker, and read the error: a timeout, a DNS error and a 5xx error point to different problems. If other networks also fail, the problem is on the server side, so check DNS first and then contact your host with the exact error and time. If only your connection fails, flush your DNS cache, try another resolver and check for a firewall or VPN.

Step 1: test from outside your own network

The fastest test is the cheapest one. Turn off Wi-Fi on your phone and load the site on mobile data. If it opens, the problem is your home or office network or device. If it fails, ask a colleague or friend in another city to try, or use an independent status checker, such as the website status tools in our free tools section.

One check can mislead you, so run two or three. A checker tests from its own location, and a regional routing problem can make a site look down from one place and fine from another.

Step 2: read the error

The message tells you where to look. Common ones:

What you see What it usually means
"This site can't be reached" or DNS_PROBE_FINISHED_NXDOMAIN DNS cannot find the domain
Connection timed out (ERR_CONNECTION_TIMED_OUT) The server is not answering, or a firewall is dropping traffic
Connection refused The server answers but nothing is listening, often a stopped web server
500 Internal Server Error The server ran your code and it failed
502 Bad Gateway or 504 Gateway Timeout A proxy or web server could not get a reply from the application behind it
503 Service Unavailable The server is overloaded or in maintenance
"Your connection is not private" A certificate problem, not an outage

Write the exact message and the time. You will need both if you contact support. For the common server errors, see our guides on fixing 500 errors, 502 bad gateway and certificate warnings.

Decision chart showing four layers where a website can fail: your device, your network, DNS and the server, with the check that isolates each

Step 3: check DNS

DNS translates your domain into an IP address. If that fails, nobody can reach the site even though the server is fine. Check it from a command line:

nslookup example.com
dig example.com +short

If these return nothing or the wrong IP, the problem is DNS: an expired domain, wrong nameservers, a deleted record or a change that has not finished spreading. Two quick checks help here.

Step 4: check the server response

If DNS looks right, test the server directly:

curl -I https://example.com

This shows the HTTP status code and headers without a browser. A 200 means the server is answering, and your browser problem is local or cached. A 5xx code confirms a server-side failure. No response at all suggests a network or firewall block, or a server that is down.

To test whether the server itself is up regardless of DNS, you can request it by IP and send the domain as a header:

curl -I -H "Host: example.com" http://203.0.113.10

Replace the address with your server's IP. If this works while the domain does not, DNS is the problem.

If it is only you

When the site loads for others but not for you:

  • Clear your browser cache or try a private window
  • Flush your DNS cache: ipconfig /flushdns on Windows, or restart the network service on Linux and macOS
  • Switch DNS resolvers, for example to a public resolver, in case your provider's resolver has a stale or bad record
  • Turn off a VPN or proxy that might block the site
  • Check whether a firewall, antivirus tool or office filter blocks it
  • Try another browser or device

If it is everyone

When it fails from every network, the fault is on the hosting side or in DNS. Work through this order:

  1. Confirm DNS resolves to the right address.
  2. Check your hosting dashboard for notices or resource limit warnings.
  3. Log in to the control panel or server and confirm the web server and database are running.
  4. Look at the error log for the first error after the outage began.
  5. Check for a recent change: plugin update, configuration edit, new firewall rule or expired certificate.
  6. Contact your host with the details below.

Common causes and fixes

  • Expired domain or certificate. Renew and wait for the change to apply.
  • Resource limits hit. CPU, memory or process limits can return 503 or 508 errors. Reduce load or upgrade the plan.
  • Database down or full. WordPress shows a database connection error. See fixing the database connection error.
  • A bad plugin or update. Disable plugins by renaming the plugin folder, then test.
  • Web server stopped. Restart it and read the logs to find why it stopped.
  • DDoS or traffic spike. Rate limiting, a CDN and a firewall help. See do you need a CDN.

What to tell your host

The best support request is specific. Include:

  • Your domain name and the exact URL
  • The error message and screenshot
  • The time the problem started, with time zone
  • What you tested, such as other networks and curl results
  • Any change made just before it happened

A request that says "my site is down" costs several round trips. One that includes the test results often gets a fix in the first reply.

Stop finding out from customers

Manual checks only work once you know there is a problem. Automatic monitoring tells you first. Set up an uptime check that tests from several locations and alerts you by email or messaging. Our guides to uptime monitoring that alerts you before customers notice and to why a status page is not enough show how to do it, and what 99.9% uptime means in hours helps you judge what your host promises.

FAQs

How do I know if a website is down for everyone?

Test it from another network, such as mobile data, and run it through an independent status checker. If both fail, it is down for others too.

Why does my site load for me but not for customers?

Usually DNS, regional routing, a certificate problem or a firewall blocking some locations. Test from other networks and look at the exact error.

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

Your resolver could not find the domain. Check it has not expired, the nameservers are correct and any recent DNS change has propagated.

Is a 503 error my fault or my host's?

It can be either. It often means the server is overloaded or in maintenance. Check your resource usage and recent changes, then ask your host.

How long should I wait before contacting my host?

If other networks also fail, contact them straight away. Do not wait. Include the error, time and what you tested.

Can a slow site look like a down site?

Yes. A server under heavy load may time out. That is a capacity problem rather than an outage, and monitoring response times will show it.

Does a status checker prove my site is up?

It proves the checker could load it from its location at that moment. Use two or more checkers and continuous monitoring for confidence.

What if only my admin area is down?

That points to the application, a plugin or a security rule blocking the admin path, not the whole server.

Conclusion

Most "site down" panic is solved by testing from a second network, reading the exact error and checking DNS before the server. Once you know which layer failed, the fix is usually quick. Then set up monitoring so the next time you hear about it before your customers do.

HostCloud monitors and supports your hosting so outages get attention fast. See the plans at https://hostcloud.in.

Sources:

Related posts