web

HTTP Status Codes

Searchable HTTP status code reference — 1xx, 2xx, 3xx, 4xx, 5xx — with descriptions, common causes, and best practices.

Category

Code	Message	Category	Description
100	Continue	1xx	The server has received the request headers and the client should proceed to send the request body.
101	Switching Protocols	1xx	The requester has asked the server to switch protocols and the server has agreed to do so.
102	Processing	1xx	The server has received and is processing the request, but no response is available yet.
103	Early Hints	1xx	Used to return some response headers before final HTTP message.
200	OK	2xx	Standard response for successful HTTP requests.
201	Created	2xx	The request has been fulfilled, resulting in the creation of a new resource.
202	Accepted	2xx	The request has been accepted for processing, but the processing has not been completed.
203	Non-Authoritative Information	2xx	The server is a transforming proxy that received a 200 OK from origin but modified the response.
204	No Content	2xx	The server successfully processed the request and is not returning any content.
205	Reset Content	2xx	The server successfully processed the request, but is not returning any content. Unlike 204, this requires the client to reset the document view.
206	Partial Content	2xx	The server is delivering only part of the resource due to a range header sent by the client.
207	Multi-Status	2xx	The message body that follows is an XML message and can contain a number of separate response codes.
208	Already Reported	2xx	The members of a DAV binding have already been enumerated in a preceding part of the multistatus response.
226	IM Used	2xx	The server has fulfilled a 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	3xx	Indicates multiple options for the resource from which the client may choose.
301	Moved Permanently	3xx	The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs.
302	Found	3xx	The requested resource resides temporarily under a different URI.
303	See Other	3xx	The response to the request can be found under another URI using the GET method.
304	Not Modified	3xx	Indicates the resource has not been modified since the version specified by the request headers.
305	Use Proxy	3xx	The requested resource is available only through a proxy, the address for which is provided in the response.
307	Temporary Redirect	3xx	The requested resource resides temporarily under a different URI. The request method should not be changed.
308	Permanent Redirect	3xx	The resource has been permanently moved to a new URI. The request method should not be changed.
400	Bad Request	4xx	The server cannot or will not process the request due to an apparent client error.
401	Unauthorized	4xx	The request requires user authentication.
402	Payment Required	4xx	Reserved for future use.
403	Forbidden	4xx	The server understood the request but refuses to authorize it.
404	Not Found	4xx	The server has not found anything matching the Request-URI.
405	Method Not Allowed	4xx	The method specified in the Request-Line is not allowed for the resource.
406	Not Acceptable	4xx	The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers.
407	Proxy Authentication Required	4xx	The client must first authenticate itself with the proxy.
408	Request Timeout	4xx	The client did not produce a request within the time that the server was prepared to wait.
409	Conflict	4xx	The request could not be completed due to a conflict with the current state of the resource.
410	Gone	4xx	The requested resource is no longer available at the server and no forwarding address is known.
411	Length Required	4xx	The server refuses to accept the request without a defined Content-Length.
412	Precondition Failed	4xx	The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
413	Payload Too Large	4xx	The server is refusing to process a request because the request payload is larger than the server is willing or able to process.
414	URI Too Long	4xx	The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
415	Unsupported Media Type	4xx	The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
416	Range Not Satisfiable	4xx	The client has asked for a portion of the file, but the server cannot supply that portion.
417	Expectation Failed	4xx	The expectation given in an Expect request-header field could not be met by this server.
418	I'm a Teapot	4xx	Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot".
421	Misdirected Request	4xx	The request was directed at a server that is not able to produce a response.
422	Unprocessable Entity	4xx	The request was well-formed but was unable to be followed due to semantic errors.
423	Locked	4xx	The resource that is being accessed is locked.
424	Failed Dependency	4xx	The request failed due to failure of a previous request.
425	Too Early	4xx	Indicates that the server is unwilling to risk processing a request that might be replayed.
426	Upgrade Required	4xx	The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.
428	Precondition Required	4xx	The origin server requires the request to be conditional.
429	Too Many Requests	4xx	The user has sent too many requests in a given amount of time.
431	Request Header Fields Too Large	4xx	The server is unwilling to process the request because its header fields are too large.
451	Unavailable For Legal Reasons	4xx	The server is denying access to the resource as a consequence of a legal demand.
500	Internal Server Error	5xx	A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501	Not Implemented	5xx	The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502	Bad Gateway	5xx	The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503	Service Unavailable	5xx	The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
504	Gateway Timeout	5xx	The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505	HTTP Version Not Supported	5xx	The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
506	Variant Also Negotiates	5xx	Transparent content negotiation for the request results in a circular reference.
507	Insufficient Storage	5xx	The server is unable to store the representation needed to complete the request.
508	Loop Detected	5xx	The server detected an infinite loop while processing the request.
510	Not Extended	5xx	Further extensions to the request are required for the server to fulfill it.
511	Network Authentication Required	5xx	The client needs to authenticate to gain network access.

All standard HTTP status codes from RFC 7231, RFC 6585, RFC 7538, and others. Search by code, message, or description.

How to use HTTP Status Codes

1Paste your input in the panel above or use the example data if available.
2Choose an action — format, generate, convert, encode, or analyze.
3Your result appears instantly. Use Copy to grab it, or Download if a file option is shown.

Runs entirely in your browser

Nothing you type, paste, generate, or upload leaves your device.

Related tools

developer

JSON Validator

Validate JSON syntax strictly.

jsonvalidate

developer

Regex Cheatsheet

Reference for all regex syntax.

regexcheatsheet