What this HTTP status code checker returns
We send a GET and follow redirects ourselves, up to five hops. The code you see is the final response: a 301 that lands on 200 is reported as 200. You still see a 3xx code when the chain stops early — no Location header, a loop, more than five hops, or a redirect to a private address that we block.
Codes group by the first digit. 2xx is success, 3xx is redirection, 4xx means this request was rejected or the URL is missing, and 5xx means the server failed while handling it. This checker treats 200–399 as up and 400–599 as down. That is a monitoring rule, not a claim that a 404 took the whole site offline.
How to read the code you got
Read the class first. The reason phrase next to the number is optional; the number is the contract.
- 200: this URL returned success. It does not prove the body is the page you intended.
- 301 or 302 as the final code: the redirect did not finish. Check the target for a loop.
- 401 or 403: the host is up and is refusing this request. We send no cookies.
- 404: this path is not there. Test the site root before you blame the server.
- 429: the application is up and rate-limiting.
- 500, 502, 503, 504: the app or a gateway failed. 503 is often overload or maintenance. 504 means a gateway stopped waiting.
Why your browser and this checker can disagree
Browsers send cookies and may show a cached copy. This checker sends a fresh GET with a plain user agent and no cookies, from a datacenter. A page that fails only for logged-in users can look healthy here. A firewall that blocks datacenter addresses can return 403 to us and 200 to you.
If there is no status code, the failure is below HTTP. DNS, connection refused, timeout, and TLS errors never produce a 4xx or 5xx, because no status line arrived. Fix the connection before you hunt through application code.
Watch the code, not only this tab
A status you look up by hand goes stale immediately. ismysiteup repeats the check every 10 minutes on the free plan (5 monitors), every 5 minutes on Pro, and every minute on Business. Alerts go to WhatsApp, Telegram, Slack, or email after a failure is confirmed, so one 503 during a deploy does not page you. A 200 can still hide a bad body. The status is the first fact, not the last one.