SEOLivly
Menu
Home Tools Blog Services Contact Run the free scan

Server Status Checker - one answer from one place

Check whether a host answers from one location, read the HTTP status properly, and learn why one 200 is not a guarantee that the site is up everywhere.

A server status check tells you whether the host is responding right now. It does not explain why a site is slow, broken, or ranking poorly.

Captcha

A 200 from one location is not a guarantee that the site is up everywhere, and a timeout here is not proof that the site is down. This tool checks whether a host answers and what status it returns. That is useful when a site is down and you need a second opinion. It is not a pager.

Real uptime needs a monitor that checks from several regions and alerts you. This is a spot check from one machine. I built it because when a client calls and says "the site is down," you need one clean answer fast, not a dashboard with forty graphs and no verdict.

What it checks

One HTTP request, from one location, right now. That is the whole scope. It resolves DNS, opens a connection, sends the request, and reports back the HTTP status code and how long the round trip took.

That gives you four pieces of information: did DNS resolve, did the connection succeed, what status did the server return, and how slow was it. For a quick sanity check during an incident, that is usually enough to point you in the right direction.

If DNS is the part that fails, check the DNS before you blame the server. A missing A record looks exactly like a dead host from the outside, and it is a five-minute fix instead of a hosting ticket.

The status codes that matter

The status code is the server telling you what it thinks happened. Learn to read it and half your incident diagnosis is done before you open a terminal.

Code / result What it means What to do
200 The host answered and returned a page. Site is reachable from here. If users still complain, the problem is elsewhere: cache, region, or the page content itself.
301 / 302 Redirect. The host is alive but the URL moved. Follow the redirect. A loop here is a real outage for users even though the server is fine.
403 Forbidden. The server is up and refusing you. Usually a firewall, WAF, or bot rule. Your users may be fine. Check from a second location.
404 / 410 Not found / gone. Server is up, page is not. Not an outage. A broken link or a deleted page. Fix the link or restore the content.
429 Too many requests. Rate limited. The server is alive and protecting itself. Back off and retry slower.
5xx Server error. The host is telling you it failed. Capture the exact code. 500, 502, 503, and 504 point at different layers. Send it to your host.
Timeout No answer within the window. Could be the host, could be the network between here and there. Retry, then check from elsewhere.

MDN has the full reference if you want the exact definition of every code: HTTP response status codes. Bookmark it. You will use it more than you think.

Why it can lie in both directions

A 200 does not mean the site is healthy. A CDN can serve a cached copy of a page while the origin server is on fire. The cache answers, the tool reports 200, and your users get stale content or broken checkout.

A timeout does not mean the site is down either. A firewall might be blocking this specific request. A bot rule might be silently dropping it. The network path between this machine and the host might be the thing that failed, not the host itself.

Region matters too. A host can be up in one country and unreachable in another because of a routing problem or a DNS propagation issue. One request from one place cannot see that. It only sees its own path.

When a 5xx is the answer

A 5xx is the most useful result you can get, because the server is admitting fault. It is not ambiguous like a timeout. The host received your request, tried to handle it, and failed.

Write down the exact code before you do anything else. A 502 usually means a bad gateway, often the app server behind the web server is down. A 503 means the service is unavailable, frequently overloaded or in maintenance. A 504 means the gateway timed out waiting for the upstream.

Those are different problems with different owners. Handing your host "the site is down" gets you a shrug. Handing them "502 from three checks over ten minutes" gets you a ticket that actually moves.

Uptime vs a spot check

A spot check answers "is it up right now, from here." An uptime monitor answers "was it up all month, from everywhere, and who got paged when it wasn't." Those are different products and you should not confuse them.

A real monitor checks every minute or so from multiple regions, records the history, and fires an alert when something breaks. That is what you need if downtime costs you money. It is also what this tool is not.

  • Spot check: one request, one location, one moment. Free, instant, no history.
  • Uptime monitor: many requests, many regions, stored history, alerts. Paid, usually per check or per site.
  • What you actually need: a monitor for the sites that pay the bills, a spot check for the "is it just me" moments.

If you want to rule out a network-level block before you blame the host, run the ICMP check, and why a failed ping proves little. It is another data point, not a verdict.

What this tool cannot do

Honest limits: this is one HTTP request from one location. It cannot prove uptime, see region-specific failures, or diagnose a server. A 200 does not mean the page is correct, and a timeout may be the network between here and the host, not the host itself. Use it as a second opinion during an incident, not as your monitoring.

I would rather tell you what it does not do than let you trust it for something it was never built for. If you need real uptime history, get a monitor. If you need to know whether the host is answering right now, this is the tool.

The incident checklist

When someone says the site is down, work through this in order. It takes two minutes and it stops you from fixing the wrong thing.

  • Get the status. Run the check. Note the code and the response time.
  • Check from a second location. A different network or a phone on cellular. If one passes and one fails, it is regional or a block, not a dead host.
  • Capture the error code. Screenshot it. Send it to your host with timestamps.
  • Check the hosting status page. Most hosts post incidents. If they already know, stop debugging and wait.
  • Then act. Fix what the evidence points at, not what you assume.

Most "the site is down" calls are one of three things: a DNS change that has not propagated, a firewall blocking one network, or a host having a bad ten minutes. The checklist sorts those out fast.

FAQs

Is my site down?

Run the check. If you get a 5xx or a timeout, get a second opinion from another location before you panic. If one check passes and another fails, the site is probably up and something between you and it is the problem.

Why does one check fail and another pass?

Region, firewall, CDN cache, or bot blocking. A request from one network can be refused while another sails through. That pattern usually means the host is fine and a rule or a route is the culprit.

Can this monitor uptime?

No. It is a single request with no history and no alerts. For real uptime you need a monitor that checks from several regions on a schedule and pages you when something breaks.

If the check turns up a 200 but your traffic is still falling, the server is not your problem. Run the free 40-point scan at /website-auditor to see what the page is actually doing wrong, or read the fix service at /page/seoservices if you want someone to just handle it. And if you want the rest of the small tools, they are all at all the tools on this site.

More free tools that return a result

All the tools, sorted by what works · Have the fixes done for you