HTTP Status Codes — Complete Reference

About the HTTP Status Codes

A complete, searchable reference of HTTP response status codes. Type a code such as 404, a class such as 5xx, or a word such as redirect to see each matching status with its official name and an explanation of when it's used.

Status codes are grouped into five classes: 1xx informational, 2xx success, 3xx redirection, 4xx client errors and 5xx server errors.

How to use it

Type a code, class (4xx) or keyword.
Read the matching statuses.
Scroll down for the full reference table.

Features

All standard codes from RFC 9110 and common extensions
Search by number, class or keyword
Plain-English descriptions

HTTP status code reference

Code	Name	Meaning
100	Continue	The server received the request headers; the client should send the body.
101	Switching Protocols	The server agrees to switch protocols, e.g. to WebSocket.
103	Early Hints	Lets the browser preload resources while the server prepares the response.
200	OK	The request succeeded.
201	Created	The request succeeded and a new resource was created; usually returned by POST or PUT.
202	Accepted	The request was accepted for processing, but processing has not finished.
203	Non-Authoritative Information	The payload was modified by a transforming proxy.
204	No Content	The request succeeded and there is no body to return.
205	Reset Content	The client should reset the document view, e.g. clear a form.
206	Partial Content	Only part of the resource is returned, in response to a Range header.
207	Multi-Status	WebDAV: the body contains status for multiple resources.
300	Multiple Choices	There are several possible responses; the client should choose one.
301	Moved Permanently	The resource has a new permanent URL, given in the Location header. Search engines transfer ranking to the new URL.
302	Found	The resource is temporarily at another URL. Clients may change POST to GET when following it.
303	See Other	Redirect to another resource with GET, commonly after a form POST.
304	Not Modified	The cached version is still valid (conditional request via ETag or Last-Modified).
307	Temporary Redirect	Temporary redirect that keeps the original method and body.
308	Permanent Redirect	Permanent redirect that keeps the original method and body.
400	Bad Request	The server cannot process the request because of a client error such as malformed syntax or invalid parameters.
401	Unauthorized	Authentication is required or has failed. The response includes a WWW-Authenticate header.
402	Payment Required	Reserved; some APIs use it when a quota or subscription is exhausted.
403	Forbidden	The client is authenticated but not allowed to access the resource.
404	Not Found	The server cannot find the requested resource.
405	Method Not Allowed	The HTTP method is not supported for this resource; see the Allow header.
406	Not Acceptable	No representation matches the Accept headers sent by the client.
407	Proxy Authentication Required	The client must authenticate with the proxy.
408	Request Timeout	The server timed out waiting for the request.
409	Conflict	The request conflicts with the current state of the resource, e.g. an edit conflict or duplicate key.
410	Gone	The resource was permanently removed and will not come back.
411	Length Required	The request must include a Content-Length header.
412	Precondition Failed	A precondition header such as If-Match evaluated to false.
413	Content Too Large	The request body is larger than the server allows.
414	URI Too Long	The request URL is longer than the server will interpret.
415	Unsupported Media Type	The Content-Type of the body is not supported.
416	Range Not Satisfiable	The requested Range cannot be served.
417	Expectation Failed	The Expect header requirement cannot be met.
418	I'm a teapot	An April Fools' joke from RFC 2324; occasionally used to refuse requests.
421	Misdirected Request	The request was sent to a server that cannot produce a response for it.
422	Unprocessable Content	The request is well-formed but contains semantic errors, commonly used for validation failures.
423	Locked	WebDAV: the resource is locked.
425	Too Early	The server will not process a request that might be replayed.
426	Upgrade Required	The client should switch to a different protocol.
428	Precondition Required	The server requires the request to be conditional to prevent lost updates.
429	Too Many Requests	The client is being rate-limited. Check the Retry-After header.
431	Request Header Fields Too Large	Headers are too large, often because of oversized cookies.
451	Unavailable For Legal Reasons	The resource is blocked for legal reasons, such as censorship or a court order.
500	Internal Server Error	A generic error: the server hit an unexpected condition.
501	Not Implemented	The server does not support the functionality required.
502	Bad Gateway	A gateway or proxy received an invalid response from the upstream server.
503	Service Unavailable	The server is overloaded or down for maintenance. Retry-After may say when to try again.
504	Gateway Timeout	A gateway or proxy did not get a timely response from the upstream server.
505	HTTP Version Not Supported	The HTTP version used is not supported.
507	Insufficient Storage	WebDAV: the server cannot store the representation.
508	Loop Detected	WebDAV: an infinite loop was detected while processing.
511	Network Authentication Required	The client must authenticate to gain network access, e.g. a captive portal.

Frequently asked questions

What's the difference between 301 and 302?

301 is a permanent redirect — browsers and search engines update to the new URL. 302 is temporary and the original URL stays canonical. Use 308/307 when the request method must be preserved.

401 vs 403?

401 Unauthorized means you aren't authenticated (or credentials are wrong). 403 Forbidden means you are authenticated but not allowed to access the resource.

When should an API return 422?

When the request is syntactically valid but fails validation — for example a missing required field or an invalid email address.