1xx Status Codes [Informational]

Status Code

100 Continue

101 Switching Protocol

102 Processing (WebDAV)

103 Early Hints

2xx Status Codes [Success]

Status Code
200 OK
201 Created

202 Accepted

203 Non-Authoritative Information

204 No Content
205 Reset Content
206 Partial Content

207 Multi-Status (WebDAV)

208 Already Reported (WebDAV)

226 IM Used
3xx Status Codes [Redirection]
Status Code
300 Multiple Choices

301 Moved Permanently

302 Found

303 See Other

304 Not Modified

305 Use Proxy (Deprecated)

306 (Unused)

307 Temporary Redirect

308 Permanent Redirect

(experimental)

4xx Status Codes (Client Error)

Status Code

400 Bad Request

401 Unauthorized

402 Payment Required

(Experimental)

403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable

407 Proxy Authentication Required

408 Request Timeout

409 Conflict
410 Gone

411 Length Required

412 Precondition Failed

413 Request Entity Too Large

414 Request-URI Too Long
415 Unsupported Media Type

416 Requested Range Not Satisfiable

417 Expectation Failed

418 I’m a teapot (RFC 2324)

420 Enhance Your Calm (Twitter)

422 Unprocessable Entity (WebDAV)

423 Locked (WebDAV)
424 Failed Dependency (WebDAV)

425 Too Early (WebDAV)

426 Upgrade Required

428 Precondition Required
429 Too Many Requests

431 Request Header Fields Too Large

444 No Response (Nginx)

449 Retry With (Microsoft)
450 Blocked by Windows Parental
Controls (Microsoft)

451 Unavailable For Legal Reasons

499 Client Closed Request (Nginx)

5xx Status Codes (Server Error)

Status Code
500 Internal Server Error

501 Not Implemented

502 Bad Gateway

503 Service Unavailable
504 Gateway Timeout

505 HTTP Version Not Supported

(Experimental)

506 Variant Also Negotiates

(Experimental)

507 Insufficient Storage (WebDAV)

508 Loop Detected (WebDAV)

510 Not Extended
511 Network Authentication
Required
 Description

An interim response. Indicates to the client that the initial part of the request
has been received and has not yet been rejected by the server. The client
SHOULD continue by sending the remainder of the request or, if the request
has already been completed, ignore this response. The server MUST send a
final response after the request has been completed.

Sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to

Indicates that the server has received and is processing the request, but no
response is available yet.

Primarily intended to be used with the Link header. It suggests the user agent
start preloading the resources while the server prepares a final response.

Description
Indicates that the request has succeeded.
Indicates that the request has succeeded and a new resource has been
created as a result.
Indicates that the request has been received but not completed yet. It is
typically used in log running requests and batch processing.
Indicates that the returned metainformation in the entity-header is not the
definitive set as available from the origin server, but is gathered from a local or
a third-party copy. The set presented MAY be a subset or superset of the
original version.
The server has fulfilled the request but does not need to return a response
body. The server may return the updated meta information.
Indicates the client to reset the document which sent this request.
It is used when the Range header is sent from the client to request only part
of a resource.
An indicator to a client that multiple operations happened, and that the status
for each operation can be found in the body of the response.
Allows a client to tell the server that the same resource (with the same
binding) was mentioned earlier. It never appears as a true HTTP response code
in the status line, and only appears in bodies.
The server has fulfilled a GET request for the resource, and the response is a
representation of the result of one or more instance-manipulations applied to
the current instance.
 Description
The request has more than one possible response. The user-agent or user
should choose one of them.
The URL of the requested resource has been changed permanently. The new
URL is given by the Location header field in the response. This response is
cacheable unless indicated otherwise.

The URL of the requested resource has been changed temporarily. The new
URL is given by the Location field in the response. This response is only
cacheable if indicated by a Cache-Control or Expires header field.

The response can be found under a different URI and SHOULD be retrieved
using a GET method on that resource.
Indicates the client that the response has not been modified, so the client can
continue to use the same cached version of the response.

Indicates that a requested response must be accessed by a proxy.

It is a reserved status code and is not used anymore.
Indicates the client to get the requested resource at another URI with same
method that was used in the prior request. It is similar to 302 Found with
one exception that the same HTTP method will be used that was used in the
prior request.

Indicates that the resource is now permanently located at another URI,

specified by the Location header. It is similar to 301 Moved
Permanently with one exception that the same HTTP method will be used
that was used in the prior request.

Description

The request could not be understood by the server due to incorrect syntax.
The client SHOULD NOT repeat the request without modifications.

Indicates that the request requires user authentication information. The client
MAY repeat the request with a suitable Authorization header field

Reserved for future use. It is aimed for using in the digital payment systems.

Unauthorized request. The client does not have access rights to the content.
Unlike 401, the client’s identity is known to the server.
The server can not find the requested resource.
The request HTTP method is known by the server but has been disabled and
cannot be used for that resource.
The server doesn’t find any content that conforms to the criteria given by the
user agent in the Accept header sent in the request.

Indicates that the client must first authenticate itself with the proxy.

Indicates that the server did not receive a complete request from the client
within the server’s allotted timeout period.
The request could not be completed due to a conflict with the current state of
the resource.
The requested resource is no longer available at the server.
The server refuses to accept the request without a defined Content- Length.
The client MAY repeat the request if it adds a valid Content-Length header
field.
The client has indicated preconditions in its headers which the server does not
meet.

Request entity is larger than limits defined by server.

The URI requested by the client is longer than the server can interpret.
The media-type in Content-type of the request is not supported by the
server.

The range specified by the Range header field in the request can’t be fulfilled.

The expectation indicated by the Expect request header field can’t be met by
the server.

It was defined as April’s lool joke and is not expected to be implemented by actual HTTP servers. (RFC 2324)

Returned by the Twitter Search and Trends API when the client is being rate
limited.
The server understands the content type and syntax of the request entity, but
still server is unable to process the request for some reason.
The resource that is being accessed is locked.
The request failed due to failure of a previous request.

Indicates that the server is unwilling to risk processing a request that might be
replayed.
The server refuses to perform the request. The server will process the request
after the client upgrades to a different protocol.
The origin server requires the request to be conditional.
The user has sent too many requests in a given amount of time (“rate
limiting”).
The server is unwilling to process the request because its header fields are too
large.
The Nginx server returns no information to the client and closes the
connection.
The request should be retried after performing the appropriate action.
Windows Parental Controls are turned on and are blocking access to the given
webpage.

The user-agent requested a resource that cannot legally be provided.

The connection is closed by the client while HTTP server is processing its
request, making the server unable to send the HTTP header back.

Description
The server encountered an unexpected condition that prevented it from
fulfilling the request.

The HTTP method is not supported by the server and cannot be handled.

The server got an invalid response while working as a gateway to get the
response needed to handle the request.
The server is not ready to handle the request.
The server is acting as a gateway and cannot get a response in time for a
request.

The HTTP version used in the request is not supported by the server.

Indicates that the server has an internal configuration error: the chosen
variant resource is configured to engage in transparent content negotiation
itself, and is therefore not a proper endpoint in the negotiation process.

The method could not be performed on the resource because the server is
unable to store the representation needed to successfully complete the
request.

The server detected an infinite loop while processing the request.

Further extensions to the request are required for the server to fulfill it.
Indicates that the client needs to authenticate to gain network access.