HTTP Status Codes Reference
Complete list of HTTP status codes with descriptions. Search or browse by category.
1xx Informational
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before the final response.
2xx Success
OK
The request was successful.
Created
The request was successful and a new resource was created.
Accepted
The request has been accepted for processing, but processing has not been completed.
Non-Authoritative Information
The returned meta-information is from a cached copy, not the origin server.
No Content
The request was successful but there is no content to return.
Reset Content
The server is requesting the client to reset the document view.
Partial Content
The server is returning only part of the resource due to a range header.
Multi-Status
The response body contains multiple status codes for multiple sub-requests.
Already Reported
The members have already been enumerated in a previous reply.
IM Used
The server has fulfilled the request for the resource with instance-manipulations applied.
3xx Redirection
Multiple Choices
There are multiple options for the requested resource.
Moved Permanently
The resource has been permanently moved to a new URL.
Found
The resource is temporarily located at a different URL.
See Other
The response can be found at a different URL using a GET request.
Not Modified
The resource has not been modified since the last request.
Use Proxy
The requested resource must be accessed through a proxy.
Temporary Redirect
The resource is temporarily located at a different URL. The method and body will not be changed.
Permanent Redirect
The resource has been permanently moved. The method and body will not be changed.
4xx Client Error
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
Authentication is required to access the resource.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Forbidden
The client does not have permission to access the resource.
Not Found
The server could not find the requested resource.
Method Not Allowed
The request method is not supported for the requested resource.
Not Acceptable
The server cannot produce a response matching the Accept headers.
Proxy Authentication Required
Authentication with the proxy is required.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the server.
Gone
The resource is no longer available and has been permanently removed.
Length Required
The request did not specify a required Content-Length header.
Precondition Failed
One or more preconditions in the request headers were not met.
Payload Too Large
The request body is larger than the server is willing to process.
URI Too Long
The requested URI is longer than the server is willing to process.
Unsupported Media Type
The request body is in a format not supported by the server.
Range Not Satisfiable
The range specified in the request cannot be fulfilled.
Expectation Failed
The server cannot meet the requirements of the Expect header.
I'm a Teapot
The server refuses to brew coffee because it is a teapot (RFC 2324).
Unprocessable Entity
The request was well-formed but could not be processed due to semantic errors.
Locked
The resource is currently locked.
Failed Dependency
The request failed because it depended on another request that also failed.
Too Early
The server is unwilling to process a request that might be replayed.
Upgrade Required
The client should switch to a different protocol.
Precondition Required
The server requires the request to be conditional.
Too Many Requests
The client has sent too many requests in a given time period.
Request Header Fields Too Large
The request headers are too large for the server to process.
Unavailable For Legal Reasons
The resource is unavailable due to legal demands.
5xx Server Error
Internal Server Error
The server encountered an unexpected condition.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
The server received an invalid response from an upstream server.
Service Unavailable
The server is temporarily unable to handle the request.
Gateway Timeout
The server did not receive a timely response from an upstream server.
HTTP Version Not Supported
The server does not support the HTTP version used in the request.
Variant Also Negotiates
The server has an internal configuration error during content negotiation.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.
How to Use HTTP Status Codes Reference
Step 1
Browse the categorized list of HTTP status codes.
Step 2
Use the search field to filter by code number or name.
Step 3
Read the description of each status code.
Step 4
Bookmark this page for quick reference.
Features
Complete list of standard HTTP status codes.
Categorized by type: 1xx, 2xx, 3xx, 4xx, 5xx.
Search and filter by code or name.
Clear descriptions for each status code.
Color-coded categories for easy scanning.
FAQ
HTTP status codes are three-digit numbers returned by a server in response to a client's request. They indicate whether the request was successful, redirected, or resulted in an error.
4xx codes indicate client errors (the request was malformed or unauthorized), while 5xx codes indicate server errors (the server failed to fulfill a valid request).
A 200 OK status code means the request was successful and the server returned the requested resource.
A 404 Not Found status code means the server could not find the requested resource. This typically happens when a URL is mistyped or a page has been removed.