http status code checker
Showing 61 of 61 status codes
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client via the Upgrade header.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before the final HTTP message.
OK
The request has succeeded. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The returned metadata is not exactly the same as available from the origin server.
No Content
The server successfully processed the request but is not returning any content.
Reset Content
The server successfully processed the request and is asking the client to reset the document view.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Multi-Status
A multi-status response conveys information about multiple resources in situations where multiple status codes might be appropriate.
Already Reported
Used inside a DAV response to avoid enumerating the same collection member multiple times.
IM Used
The server has fulfilled a GET request and the response is a representation of the result of one or more instance manipulations.
Multiple Choices
The request has more than one possible response. The user or user agent should choose one.
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Found
The URI of the requested resource has been changed temporarily. Further changes might be made in the future.
See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
Not Modified
The resource has not been modified since the last request. The client can use its cached version.
Use Proxy
The requested resource is only available through a proxy, the address for which is provided in the response.
Temporary Redirect
The server is redirecting the request to another URI using the same HTTP method as the original request.
Permanent Redirect
The resource is now permanently located at another URI, and the same HTTP method must be used.
Bad Request
The server cannot process the request due to something perceived to be a client error.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use. Some services use this to indicate payment is needed.
Forbidden
The client does not have access rights to the content. Unlike 401, the client's identity is known.
Not Found
The server cannot find the requested resource. The URL is not recognized.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Not Acceptable
The server cannot produce a response matching the criteria given by the client's Accept headers.
Proxy Authentication Required
Authentication is needed via a proxy to access the requested resource.
Request Timeout
The server timed out waiting for the request from the client.
Conflict
The request conflicts with the current state of the server.
Gone
The requested content has been permanently deleted from the server with no forwarding address.
Length Required
The server rejected the request because the Content-Length header field is not defined.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
The request entity is larger than the limits defined by the server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Range Not Satisfiable
The range specified by the Range header field cannot be fulfilled.
Expectation Failed
The expectation given in the Expect request header cannot be met by the server.
I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324).
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Locked
The resource that is being accessed is locked.
Failed Dependency
The request failed because it depended on another request and that request failed.
Too Early
The server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The server refuses to perform the request using the current protocol but may after the client upgrades.
Precondition Required
The origin server requires the request to be conditional.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
Unavailable For Legal Reasons
The user agent requested a resource that cannot legally be provided.
Internal Server Error
The server has encountered a situation it does not know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
The server received an invalid response from the upstream server.
Service Unavailable
The server is not ready to handle the request, often due to maintenance or overloading.
Gateway Timeout
The server is acting as a gateway and did not get a response in time from the upstream server.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error during transparent content negotiation.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.
about http status code checker
A comprehensive reference for all HTTP status codes with instant search, color-coded categories, and one-click copying.
HTTP status codes are three-digit numbers returned by web servers to indicate the outcome of a client's request. They are grouped into five categories: informational (1xx), success (2xx), redirection (3xx), client errors (4xx), and server errors (5xx). Understanding these codes is essential for web developers, API designers, and anyone who works with web technologies.
This tool provides a complete, searchable list of all standard HTTP status codes as defined by IANA and relevant RFCs. Each entry includes the numeric code, its official name, and a clear description of what it means. The color coding makes it easy to visually distinguish between successful responses, redirects, and errors at a glance.
Whether you're debugging a 502 Bad Gateway error, implementing proper redirect handling with 301 vs 302, or designing API responses with appropriate status codes, this reference has you covered. The instant search lets you quickly find any code by number or keyword, saving time compared to scrolling through documentation.
Everything runs entirely in your browser — just type to filter and click to copy. This makes it a perfect quick-reference companion for developers, QA engineers, and DevOps professionals working with HTTP-based services and APIs.