HTTP Status Code Lookup

Search by code, name, or keyword

Code	Name	Description
100	Continue	The initial part of the request was received; the client should continue with the body.
101	Switching Protocols	The server agrees to switch protocols as requested by the client.
103	Early Hints	Preliminary headers sent before the final response, used for preloading resources.
200	OK	The request succeeded.
201	Created	The request succeeded and a new resource was created.
202	Accepted	The request was accepted for processing, but processing isn't complete.
204	No Content	The request succeeded but there is no content to return.
206	Partial Content	Only part of the requested resource is being returned (range requests).
301	Moved Permanently	The resource has permanently moved to a new URL.
302	Found	The resource temporarily resides at a different URL.
303	See Other	The response can be found at a different URL, fetched with GET.
304	Not Modified	The cached version of the resource is still valid; no body is returned.
307	Temporary Redirect	The resource temporarily resides at a different URL; method must not change.
308	Permanent Redirect	The resource permanently resides at a different URL; method must not change.
400	Bad Request	The server could not understand the request due to invalid syntax.
401	Unauthorized	Authentication is required and has failed or not been provided.
402	Payment Required	Reserved for future use; occasionally used for payment/quota systems.
403	Forbidden	The client does not have access rights to the content.
404	Not Found	The server cannot find the requested resource.
405	Method Not Allowed	The request method is known but not supported for this resource.
406	Not Acceptable	No content matching the client's Accept headers was found.
408	Request Timeout	The server timed out waiting for the request.
409	Conflict	The request conflicts with the current state of the resource.
410	Gone	The resource is no longer available and will not be available again.
411	Length Required	The request did not specify the length of its content.
413	Payload Too Large	The request body is larger than the server is willing to process.
414	URI Too Long	The requested URI is longer than the server is willing to interpret.
415	Unsupported Media Type	The media format of the request body is not supported.
416	Range Not Satisfiable	The requested range cannot be fulfilled.
418	I'm a Teapot	A humorous status defined in RFC 2324; not seriously used by real servers.
422	Unprocessable Content	The request was well-formed but contains semantic errors.
425	Too Early	The server is unwilling to process a request that might be replayed.
429	Too Many Requests	The client has sent too many requests in a given time (rate limiting).
431	Request Header Fields Too Large	The request's header fields are too large.
451	Unavailable For Legal Reasons	The resource is unavailable for legal reasons (e.g. censorship).
500	Internal Server Error	The server encountered an unexpected condition.
501	Not Implemented	The server does not support the functionality required.
502	Bad Gateway	The server, acting as a gateway, received an invalid response upstream.
503	Service Unavailable	The server is not ready to handle the request (overload or maintenance).
504	Gateway Timeout	The server, acting as a gateway, did not get a response in time.
505	HTTP Version Not Supported	The server does not support the HTTP protocol version used.

How to look up an HTTP status code

Search common HTTP status codes by number, name, or keyword to see what each one means.

Status code ranges

1xx: informational
2xx: success
3xx: redirection
4xx: client error
5xx: server error

Common uses

Understand what a status code in a server log or API response actually means.
Decide which status code to return from your own API for a given situation.

Good to know

Some codes are rarely used in practice (like 418), while others are essential for correct client behavior, such as 304 for caching or 429 for rate limiting.