Search 1xx–5xx HTTP status codes with descriptions.
Free · Runs in your browser · Last updated
The server has received the request headers and the client should proceed.
The requester has asked the server to switch protocols.
Used to return some response headers before final HTTP message.
The request has succeeded.
The request has been fulfilled and a new resource was created.
The request has been accepted for processing, but the processing has not been 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.
This and all future requests should be directed to the given URI.
Tells the client to look at another URL (temporary redirect).
Indicates the resource has not been modified since the version specified.
The request should be repeated with another URI; the method must not change.
Permanent redirect; the method must not change.
The server cannot or will not process the request due to a client error.
Authentication is required and has failed or has not been provided.
The request was valid but the server is refusing action.
The requested resource could not be found.
A request method is not supported for the requested resource.
The server timed out waiting for the request.
The request could not be processed because of conflict in the current 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 the server does not support.
The server refuses the attempt to brew coffee with a teapot.
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.
A server operator has received a legal demand to deny access.
A generic error message when no more specific message is suitable.
The server either does not recognize the request method, or it lacks the ability to fulfill it.
The server received an invalid response from the upstream server.
The server cannot handle the request (overloaded or down for maintenance).
The upstream server failed to send a request in the time allowed.
The client needs to authenticate to gain network access.
Searchable reference of every standard HTTP status code with category, name and description.
All processing for HTTP Status happens locally inside your browser using JavaScript. Your input is never uploaded to a server, logged, or shared with third parties.
Yes. HTTP Status is completely free for both personal and commercial projects. There are no usage limits, no sign-up, and no premium tier.
All processing happens locally in your browser using JavaScript. Your input is never uploaded to our servers, logged, or shared with any third party.
Once the page has loaded, the tool runs entirely client-side. You can disconnect from the internet and it will keep working in the same browser tab.
HTTP Status works in all modern browsers, including the latest versions of Chrome, Firefox, Safari, Edge, Brave, and Opera, on desktop and mobile.
No. HTTP Status runs in any modern web browser with no installation, browser extension, or account required.