HTTP Status Code Reference
Quick reference for HTTP status codes with descriptions
1xx Information(4)
Client should continue sending the rest of the request.
Server understands and will switch to a different protocol.
Server has received the request and is processing it.
Returns some headers before the final response for preloading.
2xx Success(10)
Request succeeded. Response contains the requested data.
Request succeeded and a new resource was created. Common for POST.
Request accepted for processing, but not yet completed.
Request succeeded, but information may be from a third party.
Request succeeded, but no content in response. Common for DELETE.
Request succeeded, client should reset the document view.
Server delivered partial content. Used for resuming downloads.
Multiple status codes in response (WebDAV).
DAV bindings already listed in previous response (WebDAV).
Server completed GET request using instance manipulation.
3xx Redirect(8)
Multiple representations available, client should choose one.
Resource permanently moved to new URL. Use new URL.
Resource temporarily at another URL.
Use GET to retrieve resource from another URL.
Resource not modified. Use cached version.
Use specified proxy (deprecated).
Temporary redirect with same method and body.
Permanent redirect with same method.
4xx Client Error(29)
Server cannot understand request format.
Authentication required.
Reserved for future use. Common for paywalled content.
Server understood but refuses to authorize.
Resource does not exist. Most common status code.
Request method not supported.
Cannot return content matching Accept header.
Client must authenticate with proxy first.
Server timed out waiting for request.
Request conflicts with server state. Common for PUT.
Resource permanently removed.
Request must include Content-Length header.
Conditions in request headers not met.
Request body too large.
Request URL too long.
Request body format not supported.
Requested range invalid.
Expect header requirements not met.
RFC 2324 easter egg. Server refuses to brew coffee.
Request sent to wrong server.
Well-formed request but semantic errors.
Resource locked (WebDAV).
Request failed due to previous failure (WebDAV).
Server unwilling to process potentially replayed request.
Client should switch to TLS.
Request requires conditional headers.
Rate limit exceeded. Slow down.
Request headers too large.
Resource unavailable for legal reasons.
5xx Server Error(11)
Server encountered unexpected condition.
Server does not support required functionality.
Server received invalid response from upstream.
Server temporarily unable to handle request.
Server timed out waiting for upstream response.
HTTP version not supported.
Content negotiation configuration error.
Server cannot store resource (WebDAV).
Infinite loop detected (WebDAV).
Further extensions required.
Network authentication required.
What are HTTP Status Codes?
HTTP status codes are three-digit numbers returned by servers to indicate the result of a request. They are categorized into five classes: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), and 5xx (server error).
Understanding HTTP status codes is essential for web development and debugging. They help developers quickly identify if a request succeeded, why it failed, and what corrective action is needed.
How to Use
Click any status code card to copy it. Use the search box to quickly find specific codes. Click category tags to filter by status type.
Status Code Categories
- 1xx - 1xx Informational: Request received, continuing process.
- 2xx - 2xx Success: Request successfully received and processed.
- 3xx - 3xx Redirection: Further action needed to complete request.
- 4xx - 4xx Client Error: Request contains bad syntax or cannot be fulfilled.
- 5xx - 5xx Server Error: Server failed to fulfill valid request.
Frequently Asked Questions (FAQ)
Q: What are the most common HTTP status codes?
A: Most common codes: 200 (OK), 301 (Permanent Redirect), 302 (Temporary Redirect), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), 500 (Internal Server Error), 502 (Bad Gateway), 503 (Service Unavailable).
Q: What's the difference between 401 and 403?
A: 401 means authentication required (who are you?), 403 means authenticated but not authorized (you can't access this). Simply put: 401 is 'who are you', 403 is 'you can't access this'.
Q: Which status codes are important for SEO?
A: Important SEO codes: 200 (normal page), 301 (permanent redirect, transfers ranking), 302 (temporary redirect, preserves original URL ranking), 404 (page not found), 410 (page deleted), 503 (temporarily unavailable).
Q: When should I use 301 vs 302 redirect?
A: Use 301 for permanent redirects (search engines transfer ranking to new URL). Use 302 for temporary redirects (search engines keep original URL ranking). Site migration: 301. Campaign pages: 302.
Q: Why am I getting a 429 status code?
A: 429 means too many requests. You've hit a rate limit. Check the Retry-After header and wait before retrying. This is a common API protection mechanism.