HTTP Status Code Lookup
Search over 60 standard HTTP status codes across the 1xx-5xx range by number or keyword to see the reason phrase and a plain-English explanation.
Continue
The initial part of a request has been received and the client should continue sending the rest.
Switching Protocols
The server is switching protocols as requested by the client, such as upgrading to WebSocket.
Processing
The server has received the request and is processing it, but no response is available yet.
Early Hints
Used to return some response headers before the final HTTP message, such as preload hints.
OK
The request succeeded and the response contains the requested data.
Created
The request succeeded and a new resource was created as a result.
Accepted
The request has been accepted for processing, but processing is not yet complete.
Non-Authoritative Information
The returned metadata is not exactly the same as from the origin server, often via a proxy.
No Content
The request succeeded but there is no content to return, such as after a successful delete.
Reset Content
Tells the client to reset the document that sent the request, such as clearing a form.
Partial Content
Used when a range request returns only part of a resource, common in video streaming and downloads.
Multiple Choices
The request has more than one possible response, and the client should choose one.
Moved Permanently
The requested resource has been permanently moved to a new URL.
Found
The resource temporarily resides at a different URL; the original URL should still be used for future requests.
See Other
The response to the request can be found at another URL using a GET request.
Not Modified
The resource has not changed since the last request, so the client can use its cached version.
Use Proxy
The requested resource must be accessed through the proxy given in the response (deprecated).
Temporary Redirect
The resource is temporarily at a different URL, and the same request method must be reused.
Permanent Redirect
The resource has permanently moved to a new URL, and the same request method must be reused.
Bad Request
The server cannot process the request due to a client error, such as malformed syntax.
Unauthorized
Authentication is required and has either failed or not been provided.
Payment Required
Reserved for future use; originally intended for digital payment systems.
Forbidden
The server understood the request but refuses to authorize it, regardless of authentication.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Not Acceptable
The server cannot produce a response matching the list of acceptable formats given by the client.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request from the client.
Conflict
The request conflicts with the current state of the target resource, such as an edit conflict.
Gone
The requested resource is no longer available and will not be available again.
Length Required
The server refuses to accept the request without a defined Content-Length header.
Precondition Failed
One or more conditions in the request headers were not met by the server.
Payload Too Large
The request body is larger than the server is willing or able to process.
URI Too Long
The requested URI is longer than the server is willing to interpret.
Unsupported Media Type
The request payload format is not supported by the server for this method or resource.
Range Not Satisfiable
The requested byte range cannot be fulfilled for the target resource.
Expectation Failed
The expectation given in the request Expect header could not be met by the server.
I'm a Teapot
A well-known April Fools joke status code from RFC 2324, indicating the server refuses to brew coffee because it is a teapot.
Misdirected Request
The request was directed at a server that is not able to produce a response for this combination of scheme and authority.
Unprocessable Entity
The request was well-formed but contains semantic errors that prevent it from being processed.
Locked
The requested resource is locked and cannot currently be accessed.
Failed Dependency
The request failed because it depended on another request that itself failed.
Too Early
The server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The server refuses to perform the request using the current protocol and requires an upgrade.
Precondition Required
The origin server requires the request to be conditional, to prevent lost updates.
Too Many Requests
The client has sent too many requests in a given amount of time (rate limiting).
Request Header Fields Too Large
The server refuses to process the request because its header fields are too large.
Unavailable For Legal Reasons
The resource is unavailable due to a legal demand, such as government censorship.
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
The server, acting as a gateway or proxy, received an invalid response from an upstream server.
Service Unavailable
The server is currently unable to handle the request, often due to maintenance or overload.
Gateway Timeout
The server, acting as a gateway or proxy, did not receive a timely response from an upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
Variant Also Negotiates
The server has an internal configuration error involving transparent 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.
Bandwidth Limit Exceeded
The server has exceeded its bandwidth limit (a common non-standard extension used by some hosts).
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, such as with a captive portal.
How to Use the HTTP Status Code Lookup
Search for an HTTP status code by its number (like "404") or by a keyword (like "redirect" or "rate limit") to see its standard reason phrase and a plain-English explanation of when it's used. The list covers 60 standard status codes across the full 1xx-5xx range.
Example
Searching "429" shows 429 Too Many Requests — returned when a client has sent too many requests in a given time window, commonly used for API rate limiting.
Common Use Cases
- Quickly checking what an unfamiliar HTTP status code means while debugging an API.
- Looking up the correct status code to return from your own API for a specific scenario.
- Studying the standard HTTP status code ranges for a course or certification.
FAQs
- What do the different number ranges mean? 1xx codes are informational, 2xx codes indicate success, 3xx codes indicate redirection, 4xx codes indicate a client error, and 5xx codes indicate a server error — the first digit always tells you the general category.
- Is 418 "I'm a Teapot" a real status code? Yes — it originates from RFC 2324, an April Fools' joke RFC from 1998 about a Hyper Text Coffee Pot Control Protocol, but it has since been kept in the registry and is occasionally used intentionally by some servers and frameworks as an easter egg.
- Does this list cover every possible status code? It covers the most commonly referenced standard codes across the full range, including some rarer and non-standard ones like 509. A small number of obscure or vendor-specific codes outside common use may not be included.