Server Status Checker
This free server status checker requests up to 20 URLs from our server and reports each one's HTTP status code, response time, web server software and redirect target, with a plain verdict: up, redirecting, client error or down. Use it to confirm a site is reachable from outside your network, after a deploy or when visitors report problems.
Server Status Checker
Domain and Server
About this tool
"The site is down" is the most common and least precise alert there is. Sometimes the server is really off, sometimes only your office network cannot reach it, sometimes it answers but with an error page, and sometimes it is merely slow. A check from a server elsewhere on the internet, with the exact status code and timing, turns the guess into a fact you can act on or pass to your host.
Each URL is requested once from the SEO SMO HUB server, the way a browser would but stopping after the first kilobyte so the check stays light. The result shows the status code of the first response and of the final page after redirects, the time the whole chain took, the Server header, and where a redirect leads. Twenty URLs are checked per run inside a one-minute budget, and recent results are reused for five minutes.
One request from one place is a snapshot, not monitoring. A site can be fine for us and blocked for you by a firewall, a DNS cache or a regional outage, and some hosts answer bots differently from browsers. For continuous checks with alerts, use an uptime service that polls every minute from several locations.
Frequently asked questions
What do the HTTP status codes mean?
2xx means the page was served (200 OK). 3xx means a redirect (301 permanent, 302 temporary). 4xx means the request was refused or the page does not exist (403 forbidden, 404 not found, 429 too many requests). 5xx means the server itself failed (500 error, 502 bad gateway, 503 unavailable, 504 timeout).
The site works in my browser but the checker says it is down. Why?
Your browser may be showing a cached copy, or the site may block automated visitors and data-centre addresses with a firewall or bot protection, which answers 403 or drops the connection. Cloudflare challenge pages often return 403 or 503 to non-browser requests. If visitors can load the page, treat the result as a block, not an outage.
What is a good response time?
Under 200 milliseconds for the first response is excellent, under 500 is good, and more than a second means the server or application is struggling. The time shown here includes the DNS lookup, the connection, the TLS handshake and any redirects, measured from our server, so your visitors' numbers will differ.
Why does it only check 20 URLs at a time?
Every URL is a live request to someone else's server, and the free tools share a fair-use allowance per visitor so that nobody can turn them into a crawler. Twenty per run covers a site's key pages or a client list; run larger lists in batches, and results from the last five minutes are reused for free.