HTTP Status Codes

Report an Issue

Help us improve by telling us what went wrong.

Embed this Tool

Customize and copy the embed code for your website.

Your Complete Reference for HTTP Status Codes

Every time your browser loads a web page, sends a form, or fetches an image, the server responds with an HTTP status code - a three-digit number that tells the client exactly what happened with the request. These codes are the backbone of how the web communicates success, failure, redirection, and everything in between. The HTTP Status Codes tool gives you a fast, searchable, beautifully organised reference for every standard status code, complete with descriptions, common causes, and practical advice for handling each one.

Why Every Developer Needs an HTTP Status Code Reference

If you have ever stared at a 403 error wondering whether it means your authentication token expired or the resource genuinely does not allow access, you understand the value of a good reference. HTTP status codes are deceptively simple - three digits - but the nuances between a 301 and a 302, or a 502 and a 504, can mean the difference between a correctly functioning application and hours of debugging.

Front-end developers need to handle status codes in fetch responses and Axios interceptors. Back-end developers need to return the right codes from their APIs. DevOps engineers see these codes in access logs, load balancer health checks, and monitoring dashboards. QA testers verify that endpoints return the expected codes under various conditions. In short, HTTP status codes are relevant to virtually everyone who works on web applications.

The Five Classes of HTTP Status Codes

1xx - Informational. These indicate that the server has received the request and the client should continue or wait. The most common is 100 Continue, which tells the client to proceed with sending the request body. You rarely encounter these in application code, but they are important in HTTP/1.1 protocol-level negotiations.

2xx - Success. The request was received, understood, and accepted. 200 OK is the standard success response. 201 Created indicates a new resource was created (common after POST requests). 204 No Content means success but there is nothing to return in the body - often used for DELETE operations.

3xx - Redirection. The client must take additional action to complete the request. 301 Moved Permanently is critical for SEO - it tells search engines to update their index. 302 Found (temporary redirect) preserves the original URL in search rankings. 304 Not Modified tells the browser to use its cached copy, saving bandwidth and improving performance.

4xx - Client Error. Something is wrong with the request. 400 Bad Request means malformed syntax. 401 Unauthorized means authentication is required. 403 Forbidden means the server understood the request but refuses to authorize it. 404 Not Found is perhaps the most famous status code on the internet. 429 Too Many Requests indicates rate limiting.

5xx - Server Error. The server failed to fulfil a valid request. 500 Internal Server Error is the generic catch-all. 502 Bad Gateway means an upstream server sent an invalid response. 503 Service Unavailable indicates the server is temporarily overloaded or under maintenance. 504 Gateway Timeout means the upstream server did not respond in time.

How to Use This HTTP Status Codes Tool

The tool provides a clean, categorised listing of all standard HTTP status codes from the IANA registry. You can search by code number or by keyword. Each entry includes the numeric code, the standard reason phrase, a plain-language explanation of what it means, and practical notes on when and why you might encounter it.

Need to quickly check what a 422 Unprocessable Entity means? Search for it. Wondering which 3xx code to use for a permanent URL change? Browse the redirection section. The tool is designed for speed - find your answer in seconds, not minutes of scrolling through RFC documents.

Common Mistakes with HTTP Status Codes

One of the most frequent mistakes developers make is returning 200 OK with an error message in the response body. APIs that do this break client-side error handling because the HTTP layer reports success while the application layer reports failure. Always use the appropriate 4xx or 5xx code so that error-handling middleware, monitoring tools, and browser developer consoles all work correctly.

Another common issue is using 302 when 301 is intended. If a page has permanently moved, a 302 redirect wastes search engine crawl budget and dilutes link equity because search engines keep checking the old URL. Use 301 for permanent moves and 302 only for genuinely temporary redirections.

Misusing 403 and 401 is also widespread. Use 401 when the user is not authenticated at all. Use 403 when they are authenticated but lack permission for the specific resource. Getting this right helps front-end code decide whether to show a login prompt or an access denied message.

Bookmark This HTTP Status Codes Reference

Keep this tool open in a pinned tab. The next time you encounter an unfamiliar status code in your server logs, API response, or browser console, you will have the answer in seconds. No sign-up, no clutter, no ads covering the content - just a clean, comprehensive HTTP status codes reference built for working developers.