HTTP Status Codes
Look up HTTP status codes across the 1xx, 2xx, 3xx, 4xx and 5xx categories.
1xx — 1xx Informational
- 100ContinueContinue — the client should continue with the request body
- 101Switching ProtocolsSwitching Protocols — the server agrees to switch protocols (e.g. WebSocket)
- 102ProcessingProcessing — request received but not yet completed (WebDAV)
- 103Early HintsEarly Hints — preload hints sent before the final response
2xx — 2xx Success
- 200OKOK — the request succeeded
- 201CreatedCreated — the request succeeded and a new resource was created
- 202AcceptedAccepted — the request was accepted but not yet processed
- 203Non-Authoritative InformationNon-Authoritative Information — metadata from a copy, not the origin
- 204No ContentNo Content — success with no response body
- 205Reset ContentReset Content — tells the client to reset the document view
- 206Partial ContentPartial Content — range request succeeded (resumable downloads)
- 207Multi-StatusMulti-Status — multiple independent statuses (WebDAV)
- 208Already ReportedAlready Reported — members already enumerated, avoid repetition (WebDAV)
- 226IM UsedIM Used — server completed instance manipulations on the resource
3xx — 3xx Redirection
- 300Multiple ChoicesMultiple Choices — the resource has multiple representations
- 301Moved PermanentlyMoved Permanently — the resource has a new permanent URL
- 302FoundFound — the resource is temporarily at a different URL
- 303See OtherSee Other — fetch another URI with GET
- 304Not ModifiedNot Modified — the cached version is still valid
- 307Temporary RedirectTemporary Redirect — redirect while keeping the method
- 308Permanent RedirectPermanent Redirect — permanent redirect keeping the method
4xx — 4xx Client Error
- 400Bad RequestBad Request — the server could not understand the request
- 401UnauthorizedUnauthorized — authentication is required
- 402Payment RequiredPayment Required — reserved status code
- 403ForbiddenForbidden — the server refuses to fulfill the request
- 404Not FoundNot Found — the requested resource does not exist
- 405Method Not AllowedMethod Not Allowed — the method is not supported for this resource
- 406Not AcceptableNot Acceptable — cannot produce a response matching Accept headers
- 407Proxy Authentication RequiredProxy Authentication Required — authenticate with the proxy first
- 408Request TimeoutRequest Timeout — the server timed out waiting for the request
- 409ConflictConflict — the request conflicts with the current resource state
- 410GoneGone — the resource has been permanently removed
- 411Length RequiredLength Required — a Content-Length header is required
- 412Precondition FailedPrecondition Failed — a request-header precondition was not met
- 413Payload Too LargePayload Too Large — the request body exceeds the limit
- 414URI Too LongURI Too Long — the request URI exceeds the limit
- 415Unsupported Media TypeUnsupported Media Type — the request body format is not supported
- 416Range Not SatisfiableRange Not Satisfiable — the requested range cannot be served
- 417Expectation FailedExpectation Failed — the Expect header could not be met
- 418I'm a TeapotI'm a Teapot — an April Fools' joke status code (RFC 2324)
- 421Misdirected RequestMisdirected Request — the server cannot produce a response for this request
- 422Unprocessable EntityUnprocessable Entity — well-formed but semantically invalid
- 423LockedLocked — the resource is locked (WebDAV)
- 424Failed DependencyFailed Dependency — failed because a previous request failed (WebDAV)
- 425Too EarlyToo Early — the server is unwilling to risk replaying the request
- 426Upgrade RequiredUpgrade Required — the client must switch to a different protocol
- 428Precondition RequiredPrecondition Required — the request must be conditional
- 429Too Many RequestsToo Many Requests — rate limit reached
- 431Request Header Fields Too LargeRequest Header Fields Too Large — headers exceed the limit
- 451Unavailable For Legal ReasonsUnavailable For Legal Reasons — blocked for legal reasons
5xx — 5xx Server Error
- 500Internal Server Error
- 501Not ImplementedNot Implemented — the server does not support the feature
- 502Bad GatewayBad Gateway — an upstream server returned an invalid response
- 503Service UnavailableService Unavailable — the server is overloaded or under maintenance
- 504Gateway TimeoutGateway Timeout — an upstream server did not respond in time
- 505HTTP Version Not Supported
- 506Variant Also NegotiatesVariant Also Negotiates — content negotiation is misconfigured
- 507Insufficient StorageInsufficient Storage — not enough space to complete the request (WebDAV)
- 508Loop DetectedLoop Detected — an infinite loop was detected (WebDAV)
- 510Not ExtendedNot Extended — further extensions to the request are required
- 511Network Authentication RequiredNetwork Authentication Required — authenticate with the network (e.g. captive portal)
Related tools
What does HTTP Status Codes do?
Look up HTTP status codes across the 1xx, 2xx, 3xx, 4xx and 5xx categories. Search response meanings when reviewing API logs, redirects or website request failures.
Interpreting results and common questions
Does an HTTP status uniquely identify a failure?
A status describes response semantics; the cause also depends on parameters, response content, proxies and logs. A 200 response does not guarantee expected business content.
References and result limitations
Local results depend on the input and selected options. Retain the input example, format and processing rules when citing a result, and verify the output. Keep keys and other sensitive material out of public examples.
These references explain protocol or format rules; they do not endorse results produced by this site.