HTTP Status Codes Reference
Reference for HTTP status codes
About
This tool provides a comprehensive reference for HTTP status codes, including their meanings, categories, and usage. HTTP status codes are three-digit numbers returned by servers in response to client requests. Perfect for web developers debugging APIs and understanding server responses. ### How to Use 1. Enter or paste your data in the input field. 2. Adjust any available settings or options. 3. Click the action button to process. 4. Copy or download the result.
Try It Now
Comprehensive reference of HTTP status codes. Search, filter, and learn about different status codes and their meanings.
HTTP Status Codes
100Continue
The server has received the request headers and the client should proceed to send the request body.
101Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
102Processing
The server has received and is processing the request, but no response is available yet.
103Early Hints
Used to return some response headers before final HTTP message.
200OK
The request has succeeded.
201Created
The request has been fulfilled and resulted in a new resource being created.
202Accepted
The request has been accepted for processing, but the processing has not been completed.
203Non-Authoritative Information
The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response.
204No Content
The server successfully processed the request and is not returning any content.
205Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
206Partial Content
The server is delivering only part of the resource (byte serving) due to a range header sent by the client.
207Multi-Status
Conveys information about multiple resources in situations where multiple status codes might be appropriate.
208Already Reported
Used inside a <dav:propstat> response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.
226IM Used
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
300Multiple Choices
Indicates multiple options for the resource from which the client may choose.
301Moved Permanently
This and all future requests should be directed to the given URI.
302Found
Tells the client to look at (browse to) another URL.
303See Other
The response to the request can be found under another URI using a GET method.
304Not Modified
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.
305Use Proxy
The requested resource must be accessed through the proxy given by the Location field.
306Switch Proxy
No longer used. Originally meant "Subsequent requests should use the specified proxy."
307Temporary Redirect
In this case, the request should be repeated with another URI, but future requests should still use the original URI.
308Permanent Redirect
The request and all future requests should be repeated using another URI.
400Bad Request
The server cannot or will not process the request due to an apparent client error.
401Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
402Payment Required
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme.
403Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.
404Not Found
The requested resource could not be found but may be available in the future.
405Method Not Allowed
A request method is not supported for the requested resource.
406Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
407Proxy Authentication Required
The client must first authenticate itself with the proxy.
408Request Timeout
The server timed out waiting for the request.
409Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
410Gone
Indicates that the resource requested is no longer available and will not be available again.
411Length Required
The request did not specify the length of its content, which is required by the requested resource.
412Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
413Payload Too Large
The request is larger than the server is willing or able to process.
414URI Too Long
The URI provided was too long for the server to process.
415Unsupported Media Type
The request entity has a media type which the server or resource does not support.
416Range Not Satisfiable
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.
417Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418I'm a teapot
This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
421Misdirected Request
The request was directed at a server that is not able to produce a response.
422Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
423Locked
The resource that is being accessed is locked.
424Failed Dependency
The request failed because it depended on another request and that request failed.
425Too Early
Indicates that the server is unwilling to risk processing a request that might be replayed.
426Upgrade Required
The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.
428Precondition Required
The origin server requires the request to be conditional.
429Too Many Requests
The user has sent too many requests in a given amount of time.
431Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
451Unavailable For Legal Reasons
The user agent requested a resource that cannot be served due to legal reasons.
500Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
504Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.
507Insufficient Storage
The server is unable to store the representation needed to complete the request.
508Loop Detected
The server detected an infinite loop while processing the request.
510Not Extended
Further extensions to the request are required for the server to fulfill it.
511Network Authentication Required
The client needs to authenticate to gain network access.
Common Status Codes
Success Codes
- 200OK - Request succeeded
- 201Created - Resource created
- 204No Content - Success with no response body
Client Error Codes
- 400Bad Request - Invalid request
- 401Unauthorized - Authentication required
- 403Forbidden - Access denied
- 404Not Found - Resource not found
Server Error Codes
- 500Internal Server Error - Server error
- 502Bad Gateway - Invalid upstream response
- 503Service Unavailable - Server overloaded
- 504Gateway Timeout - Upstream timeout
Redirection Codes
- 301Moved Permanently - Resource moved permanently
- 302Found - Resource temporarily moved
- 304Not Modified - Resource unchanged
Examples
Input
200
Output
200 OK - The request has succeeded
Basic status code lookup
Input
404
Output
404 Not Found - The requested resource could not be found
Error status code lookup
FAQ
What are the different categories of HTTP status codes?
HTTP status codes are divided into five categories: 1xx (Informational), 2xx (Successful), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
Is this reference up-to-date?
Yes, the tool includes the latest HTTP status codes from RFC specifications.
Is this tool free?
Yes, this tool is completely free to use.
Is my data secure?
Yes, all processing is done in your browser. Your data is not sent to any server.
Does it work offline?
Yes, once the page is loaded, you can use the tool offline.