HTTP Status Codes
Look up any HTTP status code by number, name, or meaning. Codes are grouped by class from 1xx informational through 5xx server errors, each with a plain-English explanation.
1xx Informational
100101102103
Continue
The server received the request headers and the client should send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
Processing
The server has received the request and is working on it, but no response is available yet.
Early Hints
Used to return some response headers before the final response, often to preload resources.
2xx Success
200201202203204205206207226
OK
The request succeeded. The meaning depends on the method used.
Created
The request succeeded and a new resource was created as a result.
Accepted
The request was received but not yet acted upon. Processing happens later.
Non-Authoritative Information
The returned metadata is from a copy, not the origin server.
No Content
The request succeeded but there is no content to send back.
Reset Content
Tells the client to reset the document that sent the request.
Partial Content
The server is delivering only part of the resource, used for range requests.
Multi-Status
Conveys information about multiple resources, used in WebDAV.
IM Used
The server fulfilled a GET request and the response is a result of instance manipulations.
3xx Redirection
300301302303304307308
Multiple Choices
The request has more than one possible response. The client should pick one.
Moved Permanently
The resource has a new permanent URL. Update your links.
Found
The resource is temporarily at a different URL. Keep using the original.
See Other
The response can be found at another URL using a GET request.
Not Modified
The cached version is still valid, so no need to re-send the resource.
Temporary Redirect
The resource is temporarily elsewhere, and the method must not change.
Permanent Redirect
The resource is permanently elsewhere, and the method must not change.
4xx Client Error
400401402403404405406407408409410411412413414415416417418422425426428429431451
Bad Request
The server can't process the request due to a client error like malformed syntax.
Unauthorized
Authentication is required and has failed or not been provided.
Payment Required
Reserved for future use, sometimes used by APIs for billing or rate limits.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The server can't find the requested resource. The classic broken link.
Method Not Allowed
The request method is known but not supported for this resource.
Not Acceptable
The server can't produce a response matching the Accept headers.
Proxy Authentication Required
Authentication with a proxy is needed before the request can proceed.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the resource.
Gone
The resource is permanently gone with no forwarding address.
Length Required
The server requires a Content-Length header that wasn't provided.
Precondition Failed
A precondition in the request headers evaluated to false.
Payload Too Large
The request body is larger than the server is willing to process.
URI Too Long
The requested URL is longer than the server will interpret.
Unsupported Media Type
The request's media format isn't supported by the server.
Range Not Satisfiable
The requested range can't be fulfilled for the resource.
Expectation Failed
The expectation in the Expect header couldn't be met.
I'm a Teapot
An April Fools' joke from 1998. The server refuses to brew coffee.
Unprocessable Entity
The request was well-formed but had semantic errors, common in form validation.
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 to avoid lost updates.
Too Many Requests
The client sent too many requests in a given time, hitting a rate limit.
Request Header Fields Too Large
The server won't process the request because its headers are too large.
Unavailable For Legal Reasons
The resource is blocked for legal reasons like a government takedown.
5xx Server Error
500501502503504505507508511
Internal Server Error
A generic error meaning the server hit an unexpected condition.
Not Implemented
The server doesn't support the functionality to fulfill the request.
Bad Gateway
The server, acting as a gateway, got an invalid response upstream.
Service Unavailable
The server is down for maintenance or overloaded. Try again later.
Gateway Timeout
The server, acting as a gateway, didn't get a timely upstream response.
HTTP Version Not Supported
The HTTP version used in the request isn't supported.
Insufficient Storage
The server can't store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Network Authentication Required
The client needs to authenticate to gain network access, common on captive portals.