Website Status
Check whether a site is up, its HTTP status and response time.
No results yet
Enter a host above and press Run to start the check.
About the Website Status
Website Status checks whether a site is online by requesting it and reporting the HTTP status code together with the response time. A 200 confirms the site is serving normally, while 4xx or 5xx codes flag client or server errors. It is a quick uptime and health check for any URL, useful before reporting an outage or after a deployment.
How to use
- Enter the website URL you want to check.
- Click Check to send the request.
- Read the returned HTTP status code and response time.
Status codes that mean something different than they look
The distinction between 301 and 302 has real consequences, because browsers cache a 301 aggressively and often indefinitely. Ship a permanent redirect by mistake and visitors who saw it once keep following it after you remove it server-side, with no way for you to clear their cache. For anything you might reverse — maintenance, an A/B test, a temporary campaign URL — use 302 or 307. Search engines also treat the two differently: a 301 consolidates ranking signals onto the target, a 302 does not.
307 and 308 exist because 301 and 302 were widely implemented wrong. Browsers historically converted a redirected POST into a GET, dropping the request body. 307 and 308 are the strict equivalents that preserve the method and body — which matters the moment you redirect an API endpoint that clients POST to.
A 200 on a page that says 'not found' is the failure this tool is most useful for catching. Search engines call it a soft 404: the response says success, so the page gets crawled and indexed as real content, while users hit a dead end. Any status in the 200 range on a URL you expect to be gone is worth investigating — the fix is to return an actual 404 or 410.
429 and 503 both mean 'try later' but carry different obligations. Both should ship a `Retry-After` header; if you are writing a client, honour it rather than backing off on a schedule of your own invention, and if you are writing a server, sending 429 without `Retry-After` leaves well-behaved clients guessing.
Frequently asked questions
- What does a 200 status mean?
- A 200 OK means the server received the request and returned the page successfully, so the site is up and serving content.
- What do 4xx and 5xx codes indicate?
- 4xx codes signal a client-side problem such as a missing page (404), while 5xx codes indicate a server error like an overloaded or misconfigured backend (500, 503).
- Why does the response time matter?
- Response time shows how long the server took to reply. Rising times can warn of performance issues before the site fails outright.