HTTP Status Codes Wizard
Navigate the world of HTTP response codes with our interactive search and filter engine. Perfect for debugging APIs and understanding server behavior.
100% Private & Secure
This tool runs completely inside your browser using client-side WebAssembly and JS. Zero data is ever sent to our servers.
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The requester has asked the server to switch protocols.
OK
Standard response for successful HTTP requests.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
No Content
The server successfully processed the request and is not returning any content.
Moved Permanently
This and all future requests should be directed to the given URI.
Found
The resource was found, but at a different URI temporarily.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Temporary Redirect
The request should be repeated with another URI; however, future requests should still use the original URI.
Permanent Redirect
The request and all future requests should be repeated using another URI.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
Forbidden
The request was valid, but the server is refusing action.
Not Found
The requested resource could not be found but may be available in the future.
Method Not Allowed
A request method is not supported for the requested resource.
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
Gone
Indicates that the resource requested is no longer available and will not be available again.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time.
Internal Server Error
A generic error message, given when an unexpected condition was encountered.
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
How to use this tool
- Search for a specific code or name in the search bar
- Use the category filters to narrow down by response type
- View detailed descriptions for each status code
Example Usage
404
Not Found - The resource could not be located.
201
Created - A new resource has been successfully created.
When to use this tool
- Designing RESTful APIs
- Debugging server-side response logic
- Learning web protocol standards
Frequently Asked Questions
What are the 5 categories of HTTP status codes?
HTTP status codes are divided into: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
What is the difference between 401 and 403?
401 Unauthorized means the user is not authenticated. 403 Forbidden means the user is authenticated but does not have the necessary permissions for the resource.
When should I use a 204 No Content status?
Use 204 when the server successfully processed the request, but there is no requirement to return any data in the response body (common for DELETE or successful UPDATE operations).
More Developer Tools
Expert API Design Tip
Always choose the most specific status code possible. While a 400 Bad Request is technically correct for many errors, using a 422 Unprocessable Entity or 409 Conflict provides much better context to the client developing against your API.