HTTP Status Code Checker
Test a public URL and see the response status delivered to browsers, crawlers and command-line clients. Follow redirects to the final page and uncover inconsistent responses.
Read the live response
Check the status returned now rather than relying on a cached index or a browser's simplified error page.
Follow redirects
See whether a 3xx response reaches a healthy final URL or ends in another redirect, client error or server error.
Compare user agents
Reveal cases where Googlebot, mobile Safari, Chrome, Twitter Bot or curl receives a different status.
Understanding HTTP status checks
An HTTP status code is the server's compact description of what happened to a request. It is essential evidence when debugging broken pages, crawling problems, API behavior and migrations.
Status code families
The first digit identifies the broad outcome. The exact code adds context, but the entire redirect chain and final response matter more than a single isolated number.
- 2xx: the request succeeded; 200 is the usual healthy page response.
- 3xx: the resource redirects or has another cache-related instruction.
- 4xx: the request cannot be fulfilled, such as 404 Not Found or 410 Gone.
- 5xx: the server or an upstream service failed to complete the request.
SEO and monitoring uses
Search engines need stable, crawlable responses. A URL that looks fine in a browser can still return a soft error, a bot-specific block or a redirect chain. Check important templates after releases and export larger audits with the bulk checker.
- Verify canonical pages return 200.
- Confirm retired URLs redirect to the closest useful replacement.
- Investigate intermittent 429, 500, 502, 503 and 504 responses.
Frequently asked questions
What HTTP status should a normal page return?
A working, indexable page normally returns 200 OK. Other codes can be correct for redirects, deleted resources, authentication or temporary outages.
Does the tool follow 301 and 302 redirects?
Yes. It follows redirects and shows the sequence so you can see both the initial response and final status.
Why can a browser show a page when the checker reports an error?
Browser cache, cookies, authentication, geography and user-agent rules can change a response. The checker makes fresh server-side requests without your browser session.
Can I check many URLs at once?
Yes. Use the Bulk URL Checker to test up to 50 URLs in one run and export the results.