A searchable reference of all HTTP status codes with descriptions.
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 received and is processing the request, but no response is available yet.
103
Early Hints
Used to return some response headers before the final HTTP message.
200
OK
The request has succeeded. The meaning depends on the HTTP method used.
201
Created
The request has been fulfilled and a new resource has been created.
202
Accepted
The request has been accepted for processing, but the processing has not been completed.
203
Non-Authoritative Information
The returned metadata is not exactly the same as available from the origin server.
204
No Content
The server has fulfilled the request but does not need to return a response body.
205
Reset Content
The server has fulfilled the request and the client should reset the document view.
206
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
207
Multi-Status
A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate.
208
Already Reported
Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.
226
IM Used
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.
300
Multiple Choices
The request has more than one possible response. The client should choose one of them.
301
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
302
Found
The URI of the requested resource has been changed temporarily. The client should continue to use the original URI.
303
See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
304
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
307
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with the same method.
308
Permanent Redirect
The resource is now permanently located at another URI, specified in the response. The method must not change.
400
Bad Request
The server cannot process the request due to something perceived to be a client error (e.g., malformed request syntax).
401
Unauthorized
The client must authenticate itself to get the requested response. Similar to 403 but authentication is possible.
402
Payment Required
Reserved for future use. Originally created for digital payment systems, currently rarely used.
403
Forbidden
The client does not have access rights to the content. Unlike 401, the server knows the client's identity.
404
Not Found
The server cannot find the requested resource. The URL is not recognized or the resource does not exist.
405
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
406
Not Acceptable
The server cannot produce a response matching the list of acceptable values defined in the request headers.
407
Proxy Authentication Required
Similar to 401 but authentication needs to be done by a proxy.
408
Request Timeout
The server would like to shut down this unused connection. It is sent on an idle connection by some servers.
409
Conflict
The request conflicts with the current state of the server.
410
Gone
The content has been permanently deleted from server, with no forwarding address.
411
Length Required
The server rejected the request because the Content-Length header field is not defined.
412
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
413
Payload Too Large
The request entity is larger than limits defined by the server.
414
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
415
Unsupported Media Type
The media format of the requested data is not supported by the server.
416
Range Not Satisfiable
The range specified by the Range header in the request cannot be fulfilled.
417
Expectation Failed
The expectation indicated by the Expect request header 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, an April Fools joke)
422
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
425
Too Early
The server is unwilling to risk processing a request that might be replayed.
426
Upgrade Required
The server refuses to perform the request using the current protocol but might be willing after the client upgrades.
428
Precondition Required
The origin server requires the request to be conditional to prevent the lost update problem.
429
Too Many Requests
The user 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 its header fields are too large.
451
Unavailable For Legal Reasons
The user agent requested a resource that cannot legally be provided.
500
Internal Server Error
The server has encountered a situation it does not know how to handle.
501
Not Implemented
The request method is not supported by the server and cannot be handled.
502
Bad Gateway
The server, while acting as a gateway, got an invalid response from the upstream server.
503
Service Unavailable
The server is not ready to handle the request. Common causes include maintenance or overloading.
504
Gateway Timeout
The server is acting as a gateway and cannot get a response in time from the upstream server.
505
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
506
Variant Also Negotiates
The server has an internal configuration error: transparent content negotiation results in a circular reference.
507
Insufficient Storage
The server is unable to store the representation needed to complete the request.
508
Loop Detected
The server detected an infinite loop while processing the request.
510
Not Extended
Further extensions to the request are required for the server to fulfill it.
511
Network Authentication Required
The client needs to authenticate to gain network access.
How to Use
Browse the complete list of HTTP status codes or use the search box to filter by code number, name, or description. Click the category buttons to filter by type — Informational (1xx), Success (2xx), Redirection (3xx), Client Error (4xx), or Server Error (5xx). Each entry shows the status code, its official name, and a clear description of what it means.