Loading Tool Workspace...
Search and inspect HTTP status codes, error definitions, and troubleshooting tips.
Comprehensive searchable directory of all standard HTTP response status codes (1xx, 2xx, 3xx, 4xx, 5xx). Look up codes like 200, 301, 404, 403, and 500 with official RFC descriptions.
Unlike traditional web tools that send your personal data, uploaded photos, or sensitive text to remote cloud servers, our HTTP Status Code Checker operates strictly inside your client browser sandbox. This guarantees high processing speeds without network throttling, and ensures your data privacy is completely preserved.
Share HTTP Status Code Checker with your colleagues, teammates, or friends!
Explore more tools to boost your productivity.
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.
Standard response for successful HTTP requests.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but processing is not completed.
The server successfully processed the request, and is not returning any content.
The server is delivering only part of the resource due to a Range header sent by the client.
This and all future requests should be directed to the given URI.
Tells the client to look at another (temporary) URL.
Indicates that the resource has not been modified since the version specified in the request headers.
The request should be repeated with another URI; future requests can still use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot or will not process the request due to an apparent client error.
Authentication is required and has failed or has not yet been provided.
The request contained valid data and was understood by the server, but the server is refusing action.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource (e.g. GET on a POST-only form).
The server timed out waiting for the request.
Indicates that the request could not be processed because of conflict in the request state.
The resource requested is no longer available and will not be available again.
The request is larger than the server is willing or able to process.
The request entity has a media type which the server or resource does not support.
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time (rate limiting).
A generic error message, given when an unexpected condition was encountered.
The server either does not recognize the request method, or it lacks the ability to fulfill it.
The server was acting as a gateway or proxy and received an invalid response from upstream.
The server is currently unavailable (because it is overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response.