HTTP status codes
A searchable reference for the status codes you see in logs, APIs and uptime monitors. Filter by class or search by code, name or description.
43 codes
1xx · Informational
- The server received the request headers and the client should send the body.
100Continue - The server agrees to switch protocols, used for WebSocket upgrades.
101Switching Protocols - WebDAV: the server is still working on the request.
102Processing - Sent before the final response so the client can preload resources.
103Early Hints
2xx · Success
- The request succeeded. The meaning depends on the method used.
200OK - The request succeeded and a new resource was created.
201Created - The request was accepted for processing but is not finished yet.
202Accepted - The request succeeded but there is nothing to return in the body.
204No Content - Only part of the resource is returned, used for range requests.
206Partial Content - WebDAV: the response contains several status codes for sub-requests.
207Multi-Status
3xx · Redirection
- The resource has several representations and the client must choose one.
300Multiple Choices - The resource has moved to a new permanent URL.
301Moved Permanently - The resource is temporarily at a different URL.
302Found - Redirect to another URL, typically after a POST that should become a GET.
303See Other - The cached version is still fresh, no body is sent.
304Not Modified - Temporary redirect that keeps the original HTTP method.
307Temporary Redirect - Permanent redirect that keeps the original HTTP method.
308Permanent Redirect
4xx · Client error
- The server cannot parse the request, often malformed syntax or headers.
400Bad Request - Authentication is required or the credentials are missing or invalid.
401Unauthorized - Reserved for future use, sometimes used for paid APIs.
402Payment Required - The server understood the request but refuses to authorize it.
403Forbidden - The requested resource does not exist on the server.
404Not Found - The HTTP method is not supported for this resource.
405Method Not Allowed - The server timed out waiting for the request to complete.
408Request Timeout - The request conflicts with the current state of the resource.
409Conflict - The resource is permanently deleted and will not come back.
410Gone - The request body exceeds the size limit of the server.
413Payload Too Large - The payload format is not supported by the server.
415Unsupported Media Type - An April Fools joke from RFC 2324, sometimes still implemented literally.
418I'm a teapot - The request is well formed but contains semantic errors.
422Unprocessable Entity - The server refuses to process a request that might be replayed.
425Too Early - The client sent too many requests in a given time, rate limited.
429Too Many Requests - The request headers exceed the server's size limit.
431Request Header Fields Too Large - The resource is blocked for legal reasons.
451Unavailable For Legal Reasons
5xx · Server error
- The server hit an unexpected condition it cannot handle.
500Internal Server Error - The server does not support the functionality the request needs.
501Not Implemented - A gateway or proxy received an invalid response from upstream.
502Bad Gateway - The server is temporarily overloaded or down for maintenance.
503Service Unavailable - A gateway or proxy did not get a response from upstream in time.
504Gateway Timeout - WebDAV: the server cannot store the representation needed.
507Insufficient Storage - WebDAV: the server detected an infinite loop in the request.
508Loop Detected - The server needs extended features that the client did not request.
510Not Extended - The client must authenticate to the network before accessing the resource.
511Network Authentication Required
More free tools
Know when 5xx means your problem, not the client's
Uptriva classifies check results by status code and alerts you with the response detail attached, so you see the 503 before your users do.
Free tool by Uptriva. Reference data is bundled with the page.