HTTP Status Code Checker

Check the exact HTTP status code a URL returns right now. Enter an address and this tool fetches it live and shows the final status — 200 OK, 301 Moved Permanently, 404 Not Found, 500 and so on — along with every redirect it followed to get there. It is the quick way to confirm a page is live, a redirect is wired correctly, or a broken link really is broken.

How to use the HTTP Status Code Checker

Enter a URL and press Check status. The tool requests it from our server, follows any redirects, and shows:

• The final status code and its standard reason phrase, colour-coded by class (green 2xx, blue 3xx, amber 4xx, red 5xx).
• The redirect chain if any — each hop's source URL, its status, and where it pointed.
• The final URL, content type and server for context.

A bare host defaults to https://. To test a specific page, paste the full path. The status shown is the one a real browser would land on after following redirects.

What HTTP status codes mean

Every HTTP response starts with a three-digit status code that summarises what happened. The first digit defines the class, and knowing the classes is enough to read almost any response at a glance:

• 1xx informational — rare; the request was received and processing continues.
• 2xx success — the request worked. 200 OK is the normal page load; 204 No Content and 206 Partial Content are common in APIs and media.
• 3xx redirection — the resource is elsewhere. 301 is a permanent move (passes SEO value), 302/307 are temporary, 304 Not Modified means "use your cache".
• 4xx client error — the request was wrong. 404 Not Found, 403 Forbidden, 401 Unauthorized, 429 Too Many Requests.
• 5xx server error — the server failed. 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout.

The distinction that trips people up most is 301 versus 302. A 301 tells browsers and search engines the move is permanent, so they update bookmarks and pass ranking signals to the new URL; a 302 says "temporary, keep using the old address". Using the wrong one is a common SEO mistake. Likewise, a soft 404 — a missing page that returns 200 instead of 404 — confuses crawlers because the status contradicts the content. Checking the actual code is how you catch these.

Common use cases

• Confirming a page is live — a quick 200 check after a deploy or DNS change.
• Verifying redirects — make sure a moved page returns 301 to the right destination, not a 302 or a chain.
• Finding broken links — confirm a suspected dead URL really returns 404 or 410.
• Catching soft 404s — spot missing pages that wrongly return 200 and confuse search engines.
• Monitoring outages — distinguish a 5xx server error from a 4xx client problem when something breaks.

301 vs 302 vs 307 vs 308

The redirect codes look similar but behave differently, and the difference matters for SEO and for non-GET requests:

• 301 Moved Permanently — permanent. Search engines transfer ranking to the target and browsers cache the redirect. Use this for a page that has genuinely moved for good.
• 302 Found — temporary. The original URL keeps its ranking; use it for short-lived redirects like A/B tests or maintenance.
• 307 Temporary Redirect — like 302 but guarantees the method and body are preserved (a POST stays a POST).
• 308 Permanent Redirect — like 301 but also preserves the method and body.

For a simple permanent move of a normal page, 301 is correct. If you redirect form submissions or API calls, prefer 307/308 so the method is not silently changed to GET.