HTTP STATUS CODE LOOKUP
Search HTTP status codes by number, name, or keyword. Nothing leaves your browser.
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols as requested by the client (e.g. to WebSocket).
The request succeeded. The meaning depends on the HTTP method.
The request succeeded and a new resource was created as a result.
The request has been received but not yet acted upon.
The request succeeded but there's no content to return.
Only part of the resource is being returned, per a Range header.
The resource has permanently moved to a new URL given by the Location header.
The resource temporarily resides at a different URL.
The response can be found at another URL using a GET request.
The resource hasn't changed since the version specified by request headers; use the cached version.
The resource temporarily resides at a different URL; repeat the request with the same method.
The resource has permanently moved; repeat the request with the same method at the new URL.
The server can't process the request due to a client error (malformed syntax, invalid data, etc.).
Authentication is required and has failed or hasn't been provided.
The server understood the request but refuses to authorize it.
The server can't find the requested resource.
The request method is known but not supported for this resource.
No content matching the criteria given in the request's Accept headers is available.
The server timed out waiting for the request.
The request conflicts with the current state of the target resource.
The requested resource is no longer available and won't be available again.
The server requires a Content-Length header that wasn't provided.
The request body is larger than the server is willing or able to process.
The requested URI is longer than the server is willing to interpret.
The media format of the requested data isn't supported by the server.
A joke status code from the Hyper Text Coffee Pot Control Protocol (RFC 2324) — a server that is a teapot refuses to brew coffee.
The request was well-formed but couldn't be followed due to semantic errors.
The server is unwilling to risk processing a request that might be replayed.
The client has sent too many requests in a given time (rate limiting).
The server won't process the request because its headers are too large.
The resource is unavailable due to a legal demand to deny access.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server doesn't support the functionality required to fulfill the request.
The server, acting as a gateway, got an invalid response from an upstream server.
The server isn't ready to handle the request, often due to maintenance or overload.
The server, acting as a gateway, didn't get a timely response from an upstream server.
The server doesn't support the HTTP protocol version used in the request.
How to look up an HTTP status code
- 1
Type a status code (e.g. 404), a name (e.g. Not Found), or a keyword (e.g. redirect) into the search box.
- 2
Browse the matching codes with their meaning and category.
- 3
Clear the search to see the full reference list.
Questions
- What do the different status code ranges mean?
- 1xx codes are informational, 2xx mean success, 3xx are redirections, 4xx are client errors (something wrong with the request), and 5xx are server errors (something wrong on the server's end) — the first digit tells you the category at a glance.
- What's the difference between 401 and 403?
- 401 Unauthorized means the request lacks valid authentication credentials — you need to log in or provide a token. 403 Forbidden means the server recognizes who you are but you don't have permission to access that resource, regardless of authentication.
- What's the difference between 301 and 302 redirects?
- 301 Moved Permanently tells clients (and search engines) to update their records to the new URL permanently. 302 Found signals a temporary redirect — the original URL should still be used for future requests.
- Is 418 I'm a Teapot a real status code?
- It's real in the sense that it's defined in RFC 2324 (an April Fools' RFC from 1998) and RFC 7168 — some servers and libraries implement it as an easter egg, but it isn't used in serious production APIs.