HTTP Status Code Lookup
A searchable reference for every standard HTTP response status code (1xx–5xx), grouped by category, with a plain-language explanation of when each is used. Search by the code itself, its name, or a keyword in its description — results update live. Static reference data bundled with the page, so search is instant and nothing is looked up over the network.
- 100
Continue
The server has received the request headers and the client should proceed to send the request body.
- 101
Switching Protocols
The server is switching protocols as requested by the client's Upgrade header.
- 102
Processing
The server has received and is processing the request, but no response is available yet (WebDAV).
- 103
Early Hints
Used to return some response headers before the final HTTP message, typically for preloading resources.
- 200
OK
The request succeeded. The meaning of success depends on the HTTP method used.
- 201
Created
The request succeeded and a new resource was created as a result.
- 202
Accepted
The request has been received but not yet acted upon; processing may not have completed.
- 203
Non-Authoritative Information
The returned metadata is not exactly the same as from the origin server, but from a local or third-party copy.
- 204
No Content
The request succeeded but there is no content to send, and the client should keep its current view.
- 205
Reset Content
The server successfully processed the request and asks the client to reset the document view.
- 206
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
- 207
Multi-Status
Conveys information about multiple resources in situations where multiple status codes might be appropriate (WebDAV).
- 208
Already Reported
The members of a DAV binding have already been enumerated in a previous reply and are not being included again (WebDAV).
- 226
IM Used
The server has fulfilled a GET request and the response is a representation of the result of one or more instance manipulations.
- 300
Multiple Choices
The request has more than one possible response; the user or user agent should choose one of them.
- 301
Moved Permanently
The requested resource has been permanently moved to a new URL, given in the response.
- 302
Found
The requested resource resides temporarily under a different URL.
- 303
See Other
The response can be found under a different URL, and should be retrieved using a GET request.
- 304
Not Modified
There is no need to retransmit the requested resource; the client's cached version is still valid.
- 305
Use Proxy
The requested resource must be accessed through the proxy given by the Location field (deprecated).
- 307
Temporary Redirect
The requested resource resides temporarily under a different URL; the request method must not change.
- 308
Permanent Redirect
The requested resource has been permanently moved to a new URL; the request method must not change.
- 400
Bad Request
The server cannot process the request due to a client error, such as malformed syntax.
- 401
Unauthorized
The request lacks valid authentication credentials for the target resource.
- 402
Payment Required
Reserved for future use; originally intended for digital payment systems.
- 403
Forbidden
The server understood the request but refuses to authorize it.
- 404
Not Found
The server cannot find the requested resource.
- 405
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
- 406
Not Acceptable
The server cannot produce a response matching the list of acceptable values in the request's headers.
- 407
Proxy Authentication Required
The client must first authenticate itself with the proxy.
- 408
Request Timeout
The server timed out waiting for the request.
- 409
Conflict
The request conflicts with the current state of the target resource.
- 410
Gone
The requested resource is no longer available and will not be available again.
- 411
Length Required
The server refuses to accept the request without a defined Content-Length header.
- 412
Precondition Failed
One or more conditions in the request's header fields evaluated to false.
- 413
Content Too Large
The request entity is larger than the server is willing or able to process.
- 414
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
- 415
Unsupported Media Type
The media format of the requested data is not supported by the server.
- 416
Range Not Satisfiable
The range specified by the Range header field cannot be fulfilled.
- 417
Expectation Failed
The expectation given in the request's Expect header could not be met.
- 418
I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324, an April Fools' joke).
- 421
Misdirected Request
The request was directed at a server that is not able to produce a response.
- 422
Unprocessable Content
The request was well-formed but was unable to be followed due to semantic errors.
- 423
Locked
The resource that is being accessed is locked (WebDAV).
- 424
Failed Dependency
The request failed because it depended on another request that failed (WebDAV).
- 425
Too Early
The server is unwilling to risk processing a request that might be replayed.
- 426
Upgrade Required
The server refuses to perform the request using the current protocol but might be willing to after an upgrade.
- 428
Precondition Required
The origin server requires the request to be conditional.
- 429
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
- 431
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
- 451
Unavailable For Legal Reasons
The requested resource is unavailable for legal reasons, such as government censorship.
- 500
Internal Server Error
The server has encountered a situation it doesn't know how to handle.
- 501
Not Implemented
The request method is not supported by the server and cannot be handled.
- 502
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
- 503
Service Unavailable
The server is not ready to handle the request, often due to maintenance or overload.
- 504
Gateway Timeout
The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.
- 505
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
- 506
Variant Also Negotiates
The server has an internal configuration error: transparent content negotiation results in a circular reference.
- 507
Insufficient Storage
The server is unable to store the representation needed to complete the request (WebDAV).
- 508
Loop Detected
The server detected an infinite loop while processing the request (WebDAV).
- 510
Not Extended
Further extensions to the request are required for the server to fulfill it.
- 511
Network Authentication Required
The client needs to authenticate to gain network access.
About this tool
This tool is a searchable reference for every standard HTTP response status code — the 1xx through 5xx codes defined by RFC 9110 and related specs, plus a handful of widely-used extensions (like 429 Too Many Requests and 451 Unavailable For Legal Reasons). Codes are grouped by their first digit, which itself carries meaning: 1xx is informational, 2xx is success, 3xx is redirection, 4xx is a client error, and 5xx is a server error — useful context even before reading a specific code's description. It's static reference data, so search is instant and nothing is ever looked up over the network.
What you can do
- Every standard HTTP status code, 1xx through 5xx, with its name and meaning
- Search by code, name, or keyword — matches update live as you type
- Static reference data — nothing is looked up over the network
How to use
Step 1
Start typing
Search by the code itself (404), its name (Not Found), or a keyword in its description (rate limit).
Step 2
Read the result
Each match shows its category color, full name, and a plain-language explanation of when it's used.
Example
Searching for:
Query
429
matches 429 Too Many Requests — the standard code for rate limiting, along with any other code whose number, name, or description contains "429".
How your data is handled
This tool is labeled 🟢 Browser: the full status code list is bundled with the page and searched entirely in your browser — no network request is made when you search.
Frequently asked questions
What do the different colors mean?+
Each code's first digit determines its category: blue for 1xx (informational), green for 2xx (success), amber for 3xx (redirection), red for 4xx (client error), and purple for 5xx (server error).
Why isn't a code I'm seeing in production listed here?+
This covers standard, RFC-defined status codes. Some frameworks and CDNs use non-standard codes of their own (like Cloudflare's 520-527 range) that aren't part of the HTTP specification.
What's the difference between 401 and 403?+
401 Unauthorized means the request lacks valid authentication entirely (you're not logged in, or your credentials are missing/invalid); 403 Forbidden means the server recognizes who you are but you don't have permission for that specific resource.
Is 418 I'm a Teapot a real status code?+
It's a real, registered status code from RFC 2324 — originally an April Fools' joke (the Hyper Text Coffee Pot Control Protocol), but some real APIs and frameworks use it intentionally today.