HTTP Status Codes
52 status codes shown
1xx Informational
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message.
2xx Success
The request has succeeded. The meaning depends on the HTTP method used.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but the processing has not been completed.
The returned metadata is not exactly the same as available from the origin server.
The server has fulfilled the request but does not need to return a response body.
The server has fulfilled the request and the client should reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
A Multi-Status response conveys information about multiple resources.
The members of a DAV binding have already been enumerated in a previous reply.
3xx Redirection
The request has more than one possible response. The client should choose one.
The resource has been permanently moved to a new URL. Future requests should use the new URL.
The resource resides temporarily under a different URL. Client should continue to use the original URL.
The response to the request can be found under a different URL using GET method.
The resource has not been modified since the last request. Client can use cached version.
The request should be repeated with another URL but future requests should still use the original URL.
The request and all future requests should be repeated using another URL. Method and body are not changed.
4xx Client Error
The server cannot process the request due to malformed syntax or invalid parameters.
Authentication is required and has failed or has not been provided.
Reserved for future use. Some APIs use this for rate limiting or payment requirements.
The server understood the request but refuses to authorize it. Authentication will not help.
The requested resource could not be found on the server.
The HTTP method used is not supported for the requested resource.
The resource is not available in a format that would satisfy the Accept headers.
The client must first authenticate itself with the proxy.
The server timed out waiting for the request from the client.
The request conflicts with the current state of the target resource.
The resource is no longer available and will not be available again.
The server requires the Content-Length header to be set in the request.
One or more preconditions in the request header fields evaluated to false.
The request entity is larger than the server is willing or able to process.
The URI provided was too long for the server to process.
The media format of the requested data is not supported by the server.
The range specified in the Range header cannot be fulfilled.
The server refuses to brew coffee because it is, permanently, a teapot. (RFC 2324)
The request was well-formed but the server was unable to process the contained instructions.
The server is unwilling to risk processing a request that might be replayed.
The user has sent too many requests in a given amount of time (rate limiting).
The server is unwilling to process the request because its header fields are too large.
The resource is unavailable due to legal demands (e.g., censorship or government-mandated block).
5xx Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server received an invalid response from the upstream server while acting as a gateway.
The server is currently unable to handle the request due to overloading or maintenance.
The server did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
The server is unable to store the representation needed to complete the request.
The server detected an infinite loop while processing the request.
The client needs to authenticate to gain network access (e.g., captive portal).
Quick reference for all HTTP status codes with descriptions and common use cases. Searchable and grouped by category.
How to Use
- 1 Enter your input or configure options
- 2 See the result update in real time
- 3 Copy the output to use in your project
Why Use This Tool
Private & Secure
Your data never leaves your device. Everything is processed right in your browser — nothing is uploaded or stored on any server.
Lightning Fast
No waiting for uploads or server processing. Results appear instantly because all the work happens on your machine.
Free, No Sign-Up
Use this tool as many times as you want. No account required, no email, no limits — just open and go.
Developer Friendly
Built for developers who need quick, reliable tools without the clutter. Keyboard-friendly and paste-ready.
Frequently Asked Questions
Is HTTP Status Codes free to use?
Yes, HTTP Status Codes is completely free with no usage limits, no account required, and no ads. You can use it as many times as you need.
Is my data safe when using HTTP Status Codes?
Absolutely. HTTP Status Codes runs entirely in your browser. Your files and data are never uploaded to any server — everything is processed locally on your device.
Can I use HTTP Status Codes for large files?
Yes. HTTP Status Codes processes everything in your browser, so it handles most file sizes well. For extremely large datasets, performance depends on your device's available memory.
Does HTTP Status Codes work offline?
Once the page is loaded, HTTP Status Codes works without an internet connection since all processing happens locally in your browser.