HTTP Status Code Reference Look up any HTTP status code in seconds. Color-coded by category, with plain-English explanations, common scenarios, related codes, and copy-ready return snippets for Express, Next.js, Go, Flask, Axum, and curl.
Codes documented
62
Standard + WebDAV + commonly used.
Most common
16
The 16 you'll meet daily.
Looking up
200 OK
Click a row or paste a code.
Search by number, name, or scenario. Type a number to jump straight to it.
All
Press / to focus search, type a number to jump.
The 10–16 codes you'll see every day.
200 OK 201 Created 204 No Content 301 Moved Permanently 302 Found 304 Not Modified 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 422 Unprocessable Content 429 Too Many Requests 500 Internal Server Error 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout
Status codes 62 Click any row to expand details.
1xx Informational
100 Continue The initial part of the request was received and the client should continue. 101 Switching Protocols Server agrees to switch protocols as requested in Upgrade. 102 Processing WebDAV — server has accepted the request but has not finished. 103 Early Hints Lets the server preview headers (typically Link) before the final response. 2xx Success
200 OK Standard success response with a body. 201 Created Request succeeded and a new resource was created. 202 Accepted Request accepted but not yet processed. 203 Non-Authoritative Information Response payload was modified by a transforming proxy. 204 No Content Success with no response body. 205 Reset Content Success — the client should reset its current view. 206 Partial Content Range request succeeded; only the requested bytes are returned. 207 Multi-Status WebDAV — body contains multiple per-resource status codes. 208 Already Reported WebDAV — members of a binding have already been enumerated. 226 IM Used Delta encoding — server returned an instance manipulation result. 3xx Redirect
300 Multiple Choices Multiple representations are available; client must pick one. 301 Moved Permanently Resource permanently relocated to a new URL. 302 Found Temporary redirect; client may use the original URL again later. 303 See Other Follow the redirect with a GET regardless of original method. 304 Not Modified Cached copy is still fresh; no body returned. 305 Use Proxy Deprecated — must access the resource via a proxy. 307 Temporary Redirect Temporary redirect that preserves the request method. 308 Permanent Redirect Permanent redirect that preserves the request method. 4xx Client Error
400 Bad Request Server cannot or will not process the request due to client error. 401 Unauthorized Authentication required or has failed. 402 Payment Required Reserved for future use; commonly co-opted for paywalls. 403 Forbidden Authenticated but not allowed to access this resource. 404 Not Found The requested resource does not exist. 405 Method Not Allowed Request method is known but not supported by this resource. 406 Not Acceptable Server cannot produce a representation matching the Accept headers. 407 Proxy Authentication Required Like 401 but for an intermediate proxy. 408 Request Timeout Server timed out waiting for the request to arrive. 409 Conflict Request conflicts with the current state of the resource. 410 Gone Resource intentionally and permanently removed. 411 Length Required Request is missing a required Content-Length header. 412 Precondition Failed A conditional header (If-Match, If-Unmodified-Since) failed. 413 Content Too Large Request body exceeds the server's limit. 414 URI Too Long Request target URI exceeds the server's limit. 415 Unsupported Media Type Body's Content-Type is not supported by this resource. 416 Range Not Satisfiable Requested Range can't be satisfied for the target resource. 417 Expectation Failed Expectation in the Expect header cannot be met. 418 I'm a teapot April Fools' joke — the server is a teapot, not a coffee maker. 421 Misdirected Request Request was sent to a server that cannot produce a response for it. 422 Unprocessable Content Request is well-formed but semantically invalid. 423 Locked WebDAV — resource is locked. 424 Failed Dependency Request failed because a previous dependent request failed. 425 Too Early Server is unwilling to process a request that might be replayed. 426 Upgrade Required Client must switch to a different protocol. 428 Precondition Required Server requires the request to be conditional. 429 Too Many Requests Client has been rate-limited. 431 Request Header Fields Too Large Sum of the request headers exceeds the server's limit. 451 Unavailable For Legal Reasons Content is denied for legal reasons. 5xx Server Error
500 Internal Server Error Generic server-side error — the catch-all. 501 Not Implemented Server doesn't recognize the request method. 502 Bad Gateway Upstream server returned an invalid response. 503 Service Unavailable Server is temporarily unable to handle the request. 504 Gateway Timeout Upstream did not respond in time. 505 HTTP Version Not Supported Server doesn't support the HTTP protocol version of the request. 506 Variant Also Negotiates Transparent content negotiation misconfiguration. 507 Insufficient Storage WebDAV — server is out of storage for this request. 508 Loop Detected WebDAV — server detected an infinite loop while processing. 510 Not Extended Further extensions to the request are required. 511 Network Authentication Required Client must authenticate to gain network access (captive portal). 200 OK Success
Standard success response with a body.
The request succeeded and the response body carries the result. The exact payload depends on the method: a representation for GET, the result of the action for POST/PUT, status info for DELETE.
Common scenarios GET returning a resource Successful API call with JSON payload
What to do Consume the response body.
Return this status Drop-in snippets for popular HTTP stacks.