HTTP Status Codes
A complete, searchable reference of every HTTP status code grouped by class (1xx informational, 2xx success, 3xx redirection, 4xx client errors, 5xx server errors). Search by number or name to find what a code means and when to use it. Everything runs in your browser.
Secure & Private Client-Side
This tool runs entirely in your browser. No data is sent to any server, ensuring your information remains private and secure.
About HTTP Status Codes
A complete, searchable reference of every HTTP status code grouped by class (1xx informational, 2xx success, 3xx redirection, 4xx client errors, 5xx server errors). Search by number or name to find what a code means and when to use it. Everything runs in your browser.
Frequently Asked Questions
What are the five classes of HTTP status codes? expand_more
1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). The first digit defines the category of the response.
What is the difference between 301 and 302? expand_more
A 301 is a permanent redirect (browsers and search engines update their links), while a 302 is a temporary redirect (the original URL should still be used in future). Use 301 for permanent moves to preserve SEO.
What does a 404 status code mean? expand_more
404 Not Found means the server could not find the requested resource. It does not imply the error is permanent—use 410 Gone if the resource has been intentionally removed for good.
When should I return 401 vs 403? expand_more
401 Unauthorized means the request lacks valid authentication credentials. 403 Forbidden means the server understood the request but refuses to authorize it, even with valid credentials.
Are these the official status codes? expand_more
Yes. The list follows the IANA HTTP Status Code Registry and the relevant RFCs, including common codes from REST APIs and web servers.
Common Use Cases
- API Debugging: Quickly look up what a status code your endpoint returned actually means before digging into logs.
- Choosing the Right Code: Decide between 301 vs 302, or 401 vs 403, when designing a REST API.
- Reading Docs & Specs: Decode unfamiliar codes like 422, 429, or 451 you encounter in third-party API responses.
- Learning HTTP: Browse codes by class to understand how the protocol signals success, redirection, and errors.