100 Continue
The request headers were received and the client can continue.
InformationalDeveloper
HTTP Status Codes
Search common HTTP status codes, names, classes, and meanings.
101 Switching Protocols
The server is switching protocols as requested.
Informational200 OK
The request succeeded.
Success201 Created
The request succeeded and created a resource.
Success202 Accepted
The request was accepted for processing.
Success204 No Content
The request succeeded with no response body.
Success301 Moved Permanently
The resource has a permanent new URL.
Redirect302 Found
The resource is temporarily available at another URL.
Redirect304 Not Modified
The cached response can be reused.
Redirect400 Bad Request
The server cannot process the malformed request.
Client Error401 Unauthorized
Authentication is required or failed.
Client Error403 Forbidden
The server understood the request but refuses access.
Client Error404 Not Found
The requested resource was not found.
Client Error405 Method Not Allowed
The HTTP method is not allowed for this resource.
Client Error409 Conflict
The request conflicts with current resource state.
Client Error422 Unprocessable Content
The request is syntactically valid but semantically invalid.
Client Error429 Too Many Requests
The client sent too many requests in a given time.
Client Error500 Internal Server Error
The server encountered an unexpected error.
Server ErrorFAQ
Questions people ask
What is HTTP Status Codes used for?
HTTP Status Codes helps debug API responses, redirects, authentication failures, and server errors.
Does this developer tool upload data?
No. The processing and lookup data are handled locally in the browser.
Can I copy the result?
Yes. Use the copy button to copy output or individual lookup values.
Related tools