Server received request headers, client should proceed to send body
Server is switching protocols as requested (e.g. WebSocket upgrade)
Server has received and is processing the request (WebDAV)
Send preload headers before the final response
Request succeeded. Standard response for successful HTTP requests
Request succeeded and a new resource was created
Request accepted for processing, but not completed yet
Response from a transforming proxy, not the origin server
Request succeeded, no body returned (common for DELETE)
Request succeeded, client should reset the document view
Server is delivering part of the resource (Range header)
Multiple status codes for multiple resources (WebDAV)
Members already enumerated in a previous reply (WebDAV)
Multiple options for the resource (e.g. different formats)
Resource has been permanently moved to a new URL
Resource temporarily at a different URL
Response can be found at another URL via GET
Resource has not been modified since last request (caching)
Temporarily at another URL, use same HTTP method
Permanently at another URL, use same HTTP method
Server cannot process the request due to client error
Authentication required. User is not authenticated
Reserved for future use (digital payment systems)
Server understood request but refuses to authorize it
Requested resource could not be found on the server
HTTP method not allowed for this resource
No content matching Accept headers found
Client must authenticate with the proxy
Server timed out waiting for the request
Request conflicts with the current state of the resource
Resource is permanently gone and will not be available again
Content-Length header is required
One or more preconditions in headers evaluated to false
Request body is larger than the server allows
Request URI is longer than the server can handle
Server does not support the request media type
Requested range cannot be served
Server refuses to brew coffee because it is a teapot (RFC 2324)
Request is well-formed but has semantic errors (WebDAV)
Server unwilling to risk processing a request that might be replayed
Client should switch to a different protocol
Server requires the request to be conditional
Client has sent too many requests (rate limiting)
Request headers are too large
Resource unavailable for legal reasons (censorship)
Generic server error, something went wrong
Server does not support the functionality required
Server got an invalid response from an upstream server
Server is temporarily unavailable (overloaded or maintenance)
Server didn't get a response from upstream in time
Server does not support the HTTP version used
Server cannot store the representation (WebDAV)
Infinite loop detected while processing request (WebDAV)
Further extensions to the request are required
Client needs to authenticate to gain network access
HTTP Status Codes Reference
A complete, searchable list of all HTTP status codes with plain-English descriptions. Filter by category (informational, success, redirect, client error, server error) or search by code number, name, or description.
About this reference
This page lists all standard HTTP status codes defined in RFC 7231, RFC 6585, and related specifications.
- 55+ HTTP status codes with descriptions
- Color-coded by category (green=success, yellow=redirect, red=error)
- Filter by category (1xx, 2xx, 3xx, 4xx, 5xx)
- Search by code number, name, or description
- One-click copy (code + name)
- Includes WebDAV and modern status codes
100% free. No signup required. No data collected or sent anywhere.