HTTP Status Code Lookup
Look up any HTTP status code — what it means and when servers send it.
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 (e.g. to WebSocket).
OK
The request succeeded. The meaning depends on the HTTP method used.
Created
The request succeeded and a new resource was created as a result.
Accepted
The request has been received but not yet acted upon.
No Content
There is no content to send, but the request succeeded.
Partial Content
Used for range requests — the server is delivering only part of the resource.
Moved Permanently
The resource has been permanently moved to a new URL.
Found
The resource temporarily resides at a different URL.
Not Modified
The resource has not changed since the version specified in the request headers.
Temporary Redirect
Like 302, but the request method and body must not change.
Permanent Redirect
Like 301, but the request method and body must not change.
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
Authentication is required and has failed or not been provided.
Payment Required
Reserved for future use — rarely seen outside of API rate-limiting schemes.
Forbidden
The client does not have access rights to the content, even if authenticated.
Not Found
The server can't find the requested resource.
Method Not Allowed
The request method is known but not supported by the target resource.
Not Acceptable
No content matching the criteria in the Accept headers could be produced.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the target resource.
Gone
The resource requested is no longer available and will not be available again.
Length Required
The server refuses the request because the Content-Length header was not defined.
Payload Too Large
The request entity is larger than limits defined by the server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
I'm a teapot
A joke status code from RFC 2324 — the server refuses to brew coffee because it is a teapot.
Unprocessable Entity
The request was well-formed but contains semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
The server has encountered a situation it doesn't know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
The server, acting as a gateway, got an invalid response from the upstream server.
Service Unavailable
The server is not ready to handle the request — often due to maintenance or overload.
Gateway Timeout
The server, acting as a gateway, did not get a response in time from the upstream server.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.