HTTP Status Codes List
Every HTTP response carries a three-digit status code. The first digit tells you the class of response; the rest identifies the exact outcome. Select a code for its meaning, common causes, and how to return it from your server. You can also search them all in the HTTP Status Codes tool.
1xx Informational
Informational responses: the request was received and processing continues.
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 via the Upgrade header.
102 Processing
The server has accepted the request and is processing it, but no response is available yet.
103 Early Hints
Used to preload resources while the server prepares a response by sending Link headers early.
2xx Success
Success: the request was received, understood, and accepted.
200 OK
The request has succeeded. The meaning depends on the HTTP method used.
201 Created
The request has been fulfilled, resulting in the creation of a new resource.
202 Accepted
The request has been accepted for processing, but the processing has not been completed.
203 Non-Authoritative Information
The response is a transformed proxy copy from a local or third-party copy.
204 No Content
The server successfully processed the request, but there is no content to send back.
205 Reset Content
The server has fulfilled the request and the user agent should reset the document view.
206 Partial Content
The server is delivering only part of the resource due to a Range header in the request.
207 Multi-Status
The message body contains an XML status with multiple status codes for sub-operations.
208 Already Reported
The members of a DAV binding have already been enumerated in a preceding reply.
226 IM Used
The server has fulfilled a GET request for the resource using Instance Manipulations.
3xx Redirection
Redirection: the client must take additional action, usually requesting a different URL.
300 Multiple Choices
The request has more than one possible response. The user or agent should choose one.
301 Moved Permanently
The resource has been permanently moved to a new URL. Clients should update bookmarks.
302 Found
The resource temporarily resides under a different URL. The original URL should still be used.
303 See Other
The response can be found under a different URL using a GET request.
304 Not Modified
The resource has not been modified since the last request (caching mechanism).
305 Use Proxy
The requested resource must be accessed through the given proxy.
307 Temporary Redirect
The resource temporarily resides under a different URL. The method must not change.
308 Permanent Redirect
The resource has been permanently moved to a new URL. The method must not change.
4xx Client Errors
Client errors: the request is malformed, unauthorized, or targets something that does not exist.
400 Bad Request
The server cannot or will not process the request due to a client error.
401 Unauthorized
Authentication is required and has either failed or not been provided.
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. The most common error on the web.
405 Method Not Allowed
The request HTTP method is not allowed for the target resource.
406 Not Acceptable
The resource cannot generate content matching the Accept headers sent by the client.
407 Proxy Authentication Required
The client must first authenticate itself with the proxy.
408 Request Timeout
The server timed out waiting for the request from the client.
409 Conflict
The request conflicts with the current state of the target resource.
410 Gone
The resource has been permanently removed and will not be available again.
411 Length Required
The server requires a Content-Length header in the request.
412 Precondition Failed
One or more conditions in the request header fields evaluated to false.
413 Content Too Large
The request body is larger than the server is willing or able to process.
414 URI Too Long
The request URI is longer than the server is willing to interpret.
415 Unsupported Media Type
The request payload format is not supported by the server for the target resource.
416 Range Not Satisfiable
The byte range requested cannot be fulfilled.
417 Expectation Failed
The Expect header in the request cannot be met by the server.
418 I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324)
421 Misdirected Request
The request was directed at a server that cannot produce a response.
422 Unprocessable Content
The request was well-formed but semantically erroneous (WebDAV / RFC 4918).
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 client should switch to a different protocol (e.g., TLS 1.3).
428 Precondition Required
The origin server requires the request to be conditional (RFC 6585).
429 Too Many Requests
The client 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 individual header fields are too large.
451 Unavailable For Legal Reasons
The resource is blocked due to legal demands (censorship).
5xx Server Errors
Server errors: the server failed to fulfil an apparently valid request.
500 Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
501 Not Implemented
The server does not support the functionality required to fulfill the request.
502 Bad Gateway
The server acting as a gateway received an invalid response from an upstream server.
503 Service Unavailable
The server is currently unable to handle the request due to temporary overloading or maintenance.
504 Gateway Timeout
The server acting as a gateway did not receive a timely response from the upstream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates
The server has an internal configuration error in transparent content negotiation.
507 Insufficient Storage
The server does not have enough storage 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
The server requires further extensions to the request for it to be fulfilled.
511 Network Authentication Required
The client needs to authenticate to gain network access (captive portal).