HTTP Status Codes

Informational (1xx)

100ContinueThe server has received the request headers and the client should proceed to send the request body.
101Switching ProtocolsThe server is switching protocols as requested by the client.
102ProcessingThe server has received and is processing the request, but no response is available yet.
103Early HintsUsed to return some response headers before final HTTP message.

Success (2xx)

200OKThe request has succeeded.
201CreatedThe request has been fulfilled and a new resource has been created.
202AcceptedThe request has been accepted for processing, but the processing has not been completed.
203Non-Authoritative InformationThe returned metadata is not exactly the same as available from the origin server.
204No ContentThe server successfully processed the request but is not returning any content.
205Reset ContentThe server successfully processed the request and asks the client to reset the document view.
206Partial ContentThe server is delivering only part of the resource due to a range header sent by the client.
207Multi-StatusConveys information about multiple resources, for situations where multiple status codes might be appropriate.
208Already ReportedThe members of a DAV binding have already been enumerated in a preceding part of the response.
226IM UsedThe server has fulfilled a GET request for the resource, and the response represents the result of instance-manipulations applied to the current instance.

Redirection (3xx)

300Multiple ChoicesThe request has more than one possible response. The user or user agent should choose one of them.
301Moved PermanentlyThe URL of the requested resource has been changed permanently. The new URL is given in the response.
302FoundThe URI of the requested resource has been changed temporarily.
303See OtherThe server sent this response to direct the client to get the requested resource at another URI with a GET request.
304Not ModifiedThe resource has not been modified since the last request.
307Temporary RedirectThe server sends this response to direct the client to get the requested resource at another URI with the same method.
308Permanent RedirectThe resource is now permanently located at another URI, specified by the Location header.

Client Error (4xx)

400Bad RequestThe server cannot process the request due to a client error.
401UnauthorizedThe client must authenticate itself to get the requested response.
402Payment RequiredReserved for future use. The original intention was that this code might be used as part of a digital cash or micropayment scheme.
403ForbiddenThe client does not have access rights to the content.
404Not FoundThe server cannot find the requested resource.
405Method Not AllowedThe request method is known by the server but is not supported by the target resource.
406Not AcceptableThe server cannot produce a response matching the list of acceptable values defined in the request headers.
407Proxy Authentication RequiredThe client must first authenticate itself with the proxy.
408Request TimeoutThe server timed out waiting for the request.
409ConflictThe request conflicts with the current state of the server.
410GoneThe requested content has been permanently deleted from the server with no forwarding address.
411Length RequiredThe server rejected the request because the Content-Length header field is not defined.
412Precondition FailedThe client has indicated preconditions in its headers which the server does not meet.
413Payload Too LargeThe request entity is larger than limits defined by the server.
414URI Too LongThe URI requested by the client is longer than the server is willing to interpret.
415Unsupported Media TypeThe media format of the requested data is not supported by the server.
416Range Not SatisfiableThe range specified by the Range header field in the request cannot be fulfilled.
417Expectation FailedThe expectation indicated by the Expect request header field cannot be met by the server.
418I'm a TeapotThe server refuses the attempt to brew coffee with a teapot.
421Misdirected RequestThe request was directed at a server that is not able to produce a response.
422Unprocessable EntityThe request was well-formed but was unable to be followed due to semantic errors.
423LockedThe resource that is being accessed is locked.
424Failed DependencyThe request failed because it depended on another request and that request failed.
425Too EarlyThe server is unwilling to risk processing a request that might be replayed.
426Upgrade RequiredThe server refuses to perform the request using the current protocol.
428Precondition RequiredThe origin server requires the request to be conditional.
429Too Many RequestsThe user has sent too many requests in a given amount of time.
431Request Header Fields Too LargeThe server is unwilling to process the request because its header fields are too large.
451Unavailable For Legal ReasonsThe user agent requested a resource that cannot legally be provided.

Server Error (5xx)

500Internal Server ErrorThe server has encountered a situation it does not know how to handle.
501Not ImplementedThe request method is not supported by the server and cannot be handled.
502Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server.
503Service UnavailableThe server is not ready to handle the request.
504Gateway TimeoutThe server is acting as a gateway and cannot get a response in time from the upstream server.
505HTTP Version Not SupportedThe HTTP version used in the request is not supported by the server.
506Variant Also NegotiatesThe server has an internal configuration error: transparent content negotiation results in a circular reference.
507Insufficient StorageThe server is unable to store the representation needed to complete the request.
508Loop DetectedThe server detected an infinite loop while processing the request.
510Not ExtendedFurther extensions to the request are required for the server to fulfill it.
511Network Authentication RequiredThe client needs to authenticate to gain network access.

Introduction to the tool

This tool is an online reference for HTTP status codes. Search and browse all standard HTTP status codes with descriptions and use cases.