All HTTP Status Codes
Transform, format, and optimize your data instantly with this free client-side tool.
The request has succeeded. The standard response for successful HTTP requests.
The request has been fulfilled, resulting in the creation of a new resource.
The server successfully processed the request, and is not returning any content.
This and all future requests should be directed to the given URI.
Tells the client to look at (browse to) another URL. 302 has been superseded by 303 and 307.
The server cannot or will not process the request due to an apparent client error.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed.
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.
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 and no more specific message is suitable.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server cannot handle the request (because it is overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
🔥 Similar Tools
Explore LibraryFrequently Asked Questions
Got questions? We've got answers.