Toolzium
Command Palette
Search for a command to run...
HTTP Status Code Reference
Comprehensive dictionary of HTTP status codes, their meanings, and typical use cases.
The server has received the request headers and the client should proceed to send the request body.
Common Use Case
Client sending a large payload to check if server accepts it.
The requester has asked the server to switch protocols and the server has agreed to do so.
Common Use Case
Upgrading HTTP to WebSocket.
Standard response for successful HTTP requests.
Common Use Case
Successful GET or POST requests.
The request has been fulfilled, resulting in the creation of a new resource.
Common Use Case
Successful POST request creating a user.
The server successfully processed the request and is not returning any content.
Common Use Case
Successful DELETE request.
This and all future requests should be directed to the given URI.
Common Use Case
Domain redirection.
Tells the client to look at (browse to) another URL.
Common Use Case
Temporary redirect.
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.
Common Use Case
Caching optimization.
The server cannot or will not process the request due to an apparent client error.
Common Use Case
Invalid JSON payload.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
Common Use Case
Missing or invalid auth token.
The request contained valid data and was understood by the server, but the server is refusing action.
Common Use Case
Insufficient permissions.
The requested resource could not be found but may be available in the future.
Common Use Case
Invalid URL.
The user has sent too many requests in a given amount of time.
Common Use Case
Rate limiting.
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Common Use Case
Unhandled backend exception.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Common Use Case
Proxy/gateway error.
The server cannot handle the request (because it is overloaded or down for maintenance).
Common Use Case
Maintenance or overload.
Related Tools You Might Like
Hash Generator
Generate MD5, SHA1, SHA256, SHA512, and other cryptographic hashes online. Hash text, files, and pas…
CSV to JSON Converter
Convert CSV files to JSON format with automatic header detection. Transform tabular data to JSON arr…
CSS Box Shadow Generator
Visual CSS box-shadow editor with sliders for offset, blur, spread, and color. Multiple shadows, ins…
Markdown Previewer
Preview Markdown syntax and convert to HTML in real-time. Markdown editor with GitHub-flavored markd…
Lorem Ipsum Generator
Generate Lorem Ipsum placeholder text for design mockups and testing. Create paragraphs, sentences, …
API Status Monitor
Check if popular APIs and services are reachable. Pre-loaded services: Google, GitHub, AWS, Cloudfla…