HTTP Status Code Checker
Complete HTTP status code reference with search and filtering. Browse all status codes (1xx-5xx) with descriptions, causes, and examples.
35 HTTP status codes
1xx — InformationalRequest received, continuing process
4 codes2xx — SuccessRequest successfully received, understood, and accepted
5 codes3xx — RedirectionFurther action needed to complete the request
6 codes4xx — Client ErrorThe request contains bad syntax or cannot be fulfilled
15 codes5xx — Server ErrorThe server failed to fulfil an apparently valid request
5 codesHow to Use HTTP Status Code Checker
- 1Search for a specific HTTP status code.
- 2Browse codes by category (1xx through 5xx).
- 3Click any code to see causes and examples.
- 4Copy the code details for documentation.
Zenovay
Privacy-first analytics for your website
Understand your visitors without invasive tracking. GDPR compliant, lightweight, and powerful.
Related Tools
JSON Formatter & ValidatorFormat, validate, and beautify JSON data with syntax highlighting and error detection.
JWT DecoderDecode and inspect JWT tokens. View header, payload, and verify signatures.
Base64 Encode/DecodeEncode text to Base64 or decode Base64 back to text. Supports UTF-8 and binary data.
URL Encode/DecodeEncode or decode URL components. Handle special characters, query strings, and full URLs.
Frequently Asked Questions
What are HTTP status codes?▾
HTTP status codes are three-digit numbers returned by a server in response to a client request. They indicate whether the request was successful, requires further action, or encountered an error. The first digit defines the category: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), and 5xx (server error). Status codes are defined in RFC 9110 and are a core part of the HTTP protocol used by every web browser and API client.
What are the five categories of HTTP status codes?▾
1xx Informational: The server has received the request and is continuing the process. These are interim responses rarely seen by end users. 2xx Success: The request was received, understood, and accepted. 200 OK, 201 Created, and 204 No Content are the most common. 3xx Redirection: The client must take additional action to complete the request, usually following a redirect to a new URL. 4xx Client Error: The request contains bad syntax or cannot be fulfilled — the problem is on the client side (wrong URL, missing auth, invalid data). 5xx Server Error: The server failed to fulfil a valid request — the problem is on the server side.
What are the most common HTTP status codes?▾
The most frequently encountered codes are: 200 OK (successful request), 301 Moved Permanently (permanent redirect), 302 Found (temporary redirect), 304 Not Modified (cached response), 400 Bad Request (malformed request), 401 Unauthorized (authentication required), 403 Forbidden (access denied), 404 Not Found (resource missing), 422 Unprocessable Content (validation error), 429 Too Many Requests (rate limited), 500 Internal Server Error (server crash), 502 Bad Gateway (upstream server error), 503 Service Unavailable (server overloaded), and 504 Gateway Timeout (upstream timeout).
What is the difference between 301 and 302 redirects?▾
301 Moved Permanently tells the browser and search engines that the resource has permanently moved to a new URL. Search engines transfer SEO link equity to the new URL, and browsers cache the redirect — future requests go directly to the new URL without checking the old one. 302 Found is a temporary redirect — the client should keep using the original URL for future requests. Search engines do not transfer full SEO equity and do not cache the redirect. Use 301 for permanent changes (HTTPS migration, domain change, URL restructuring). Use 302 for A/B testing, maintenance pages, or login redirects. For POST requests, prefer 307 (temporary) or 308 (permanent) to preserve the HTTP method.
How do I debug HTTP status codes in my application?▾
For 4xx errors: Check the request URL, headers, and body. Use browser DevTools (Network tab) to inspect the exact request and response. For 401/403, verify authentication tokens and user permissions. For 404, confirm the resource exists and the URL is correct. For 422, check the response body for field-level validation errors. For 5xx errors: Check server logs immediately — look for stack traces and exception messages. For 502/504, verify the backend application server is running and responding. Use curl with -v flag for verbose output, or tools like Postman to isolate the request. Monitor status code distribution with analytics to detect regressions.