DEVELOPER TOOLS · LOCAL ONLY

HTTP Status Code Reference

The full list of HTTP status codes with names, classes, and when to use each.

Uses a built-in static table and makes no network requests.

1xx Informational

Code	Name	Meaning
`100`	Continue	The server received the request headers and the client can continue sending the body.
`101`	Switching Protocols	The server agrees to switch protocols as asked by the Upgrade header, commonly for WebSocket.
`103`	Early Hints	Sends resource hints before the final response so the browser can start preloading.

2xx Success

Code	Name	Meaning
`200`	OK	The request succeeded and the response body contains the requested data.
`201`	Created	The request succeeded and created a new resource, usually named in the Location header.
`202`	Accepted	The request was accepted but processing is not finished; suited to asynchronous work.
`204`	No Content	The request succeeded with no response body, common after a delete or a save.
`206`	Partial Content	The response carries only the byte range the client asked for with the Range header.

3xx Redirection

Code	Name	Meaning
`301`	Moved Permanently	The resource moved permanently; clients and search engines should use the new URL.
`302`	Found	The resource is temporarily at another URL; the original URL stays in use.
`303`	See Other	Fetch the result from another URL with GET, typically after a form submission.
`304`	Not Modified	The cached copy is still valid, so nothing needs to be downloaded again.
`307`	Temporary Redirect	A temporary redirect that must keep the original HTTP method.
`308`	Permanent Redirect	A permanent redirect that must keep the original HTTP method.

4xx Client error

Code	Name	Meaning
`400`	Bad Request	The request is malformed and the server cannot understand it.
`401`	Unauthorized	Valid authentication credentials are required, or the ones supplied have expired.
`402`	Payment Required	Reserved for payment scenarios; rarely used and not fully standardised.
`403`	Forbidden	The server understood the request but refuses to authorise it; signing in again rarely helps.
`404`	Not Found	No matching resource was found; the server does not say whether it ever existed.
`405`	Method Not Allowed	The URL does not accept the HTTP method that was used.
`406`	Not Acceptable	The server cannot produce a response matching the Accept header.
`407`	Proxy Authentication Required	The client must authenticate with the proxy first.
`408`	Request Timeout	The client did not complete the request within the server's waiting period.
`409`	Conflict	The request conflicts with the resource's current state, often from concurrent edits.
`410`	Gone	The resource was permanently removed and is explicitly not coming back.
`411`	Length Required	The server requires the request to include a Content-Length header.
`412`	Precondition Failed	A precondition given in the request headers evaluated to false.
`413`	Content Too Large	The request body is larger than the server is willing to accept.
`414`	URI Too Long	The request URL is too long, usually from an oversized GET query string.
`415`	Unsupported Media Type	The server does not support the media type of the request body.
`416`	Range Not Satisfiable	The requested Range lies outside the actual size of the resource.
`418`	I'm a teapot	A joke status from an April Fools' specification; not for production APIs.
`422`	Unprocessable Content	The syntax is valid but the content is semantically wrong, typically a validation failure.
`423`	Locked	The resource is locked; defined by the WebDAV specification.
`425`	Too Early	The server refuses to process early data that might be replayed.
`426`	Upgrade Required	The client must switch to the protocol named by the server.
`428`	Precondition Required	The server requires a conditional request to avoid lost updates.
`429`	Too Many Requests	A rate limit was hit; retry later, following the Retry-After header.
`431`	Request Header Fields Too Large	The request headers are too large for the server to process.
`451`	Unavailable For Legal Reasons	The resource is unavailable because of a legal demand.

5xx Server error

Code	Name	Meaning
`500`	Internal Server Error	The server hit an unexpected condition; this is the generic error response.
`501`	Not Implemented	The server does not support the functionality needed to fulfil the request.
`502`	Bad Gateway	A gateway or proxy received an invalid response from the upstream server.
`503`	Service Unavailable	The server is temporarily unable to serve, usually maintenance or overload.
`504`	Gateway Timeout	A gateway timed out waiting for the upstream server to respond.
`505`	HTTP Version Not Supported	The server does not support the HTTP version used in the request.
`507`	Insufficient Storage	The server has too little storage to complete the request; from WebDAV.
`511`	Network Authentication Required	Network access must be authenticated first, typical of public Wi-Fi portals.

How to use

The full list of HTTP status codes with names, classes, and when to use each.

Every common HTTP status code grouped from 1xx to 5xx, each with what it means and when it applies. Use the search box to filter by code, name, or description — try 404, gateway, or redirect.

Limits and privacy

Uses a built-in static table and makes no network requests.

Everything runs inside this browser. Your input is never uploaded, stored, or written to the URL or any log.

← All Developer Tools