HTTP Status Code Lookup - Momo Toolbox

Server received request headers; client should send request body.

Server agrees to switch protocols, commonly used for WebSocket upgrade.

Server received the request but has not yet completed it (WebDAV).

Server hints the client to preload resources before the final response.

Request succeeded. The most common status code for successful GET/POST.

Request succeeded and a new resource was created, typical for POST/PUT.

Request accepted but not yet processed, typical for async tasks.

Returned information comes from a third party, not the origin server.

Request succeeded with no content returned, typical for DELETE/PUT.

Asks the client to reset the view (e.g., clear forms).

Server returns partial content, typical for Range requests (resume/video streaming).

WebDAV extension; response body contains multiple independent statuses.

Server fulfilled a GET request and applied instance manipulations.

Resource has multiple representations; client can pick one.

Resource moved permanently to a new URI; SEO juice transferred.

Resource temporarily at another URI; future requests use the original URI.

Asks to GET another URI, typical for post-POST redirects.

Resource not modified; client can use cached version (conditional request).

Deprecated; originally required access via a proxy.

Like 302 but preserves the original method (POST stays POST).

Like 301 but preserves the original request method.

Malformed request syntax; server cannot understand. Common for parameter errors.

Authentication required. Response should include WWW-Authenticate header.

Reserved for future use; commonly repurposed for paywalls.

Server refused the request. Differs from 401: identity verified but no permission.

Server cannot find the requested resource. The most common error code.

Request method not allowed (e.g., POST on a read-only resource).

Resource cannot generate a format matching the Accept header.

Client must authenticate with a proxy first.

Client did not send a request within the server timeout.

Request conflicts with current server state, common for concurrent updates.

Resource permanently removed; unlike 404 it indicates intentional deletion.

Request must include a Content-Length header.

If-Match/If-Unmodified-Since precondition failed.

Request body exceeds the server size limit.

Request URI exceeds the server length limit.

Request Content-Type is not supported by the server.

Range request exceeds the resource size.

Expect header field could not be met.

April Fools joke; server refuses to brew tea because it is a teapot.

Request sent to a server that cannot respond (HTTP/2).

Syntactically correct but semantically wrong, common for validation errors (WebDAV).

Resource is locked (WebDAV).

Prior request failed causing this one to fail (WebDAV).

Server refuses to process within the TLS replay window.

Client must switch to a higher protocol like TLS/1.1.

Server requires If-Match etc. to prevent lost updates.

Rate limit exceeded. Response should include Retry-After.

Header total size or a single field exceeds the limit.

Refused for legal reasons (e.g., copyright, government censorship).

Server encountered an unexpected error. The most common server error code.

Server does not support the request method.

Gateway/proxy received an invalid response from upstream.

Server temporarily unavailable (overloaded or maintenance). Should include Retry-After.

Gateway/proxy timed out waiting for upstream response.

Server does not support the HTTP version used in the request.

Transparent content negotiation misconfiguration.

Server lacks storage to complete the request (WebDAV).

Infinite loop detected while processing the request (WebDAV).

Further extensions are required to fulfill the request.

Network login required first (e.g., public WiFi captive portal).