HTTP Status Codes
Complete reference for all 62 HTTP response status codes. Each code explained with common causes, fixes, and context for web developers and SEO professionals.
Informational
The server received the request and is continuing the process. These interim responses indicate that the client should wait for a final response.
The server received the request headers and the client should proceed to send the body.
The server is switching to a different protocol as requested by the client.
The server is processing the request but has no response available yet.
The server sends preliminary headers to let the browser preload resources.
Success
The request was successfully received, understood, and accepted by the server.
The request succeeded and the server returned the requested content.
The request succeeded and a new resource was created on the server.
The request was accepted for processing but the processing is not yet complete.
The response was modified by an intermediary proxy before reaching the client.
The request succeeded but there is no content to return in the response body.
The request succeeded and the client should reset the document view or form.
The server is delivering only part of the resource due to a range request.
The response contains status information for multiple resources in a single message.
The resource was already included in a previous part of the multi-status response.
The server fulfilled a GET request using instance manipulations applied to the resource.
Redirection
The client must take additional action to complete the request. These codes indicate the resource has moved or an alternative should be used.
The request has multiple possible responses and the client must choose one.
The resource has permanently moved to a new URL and all future requests should use it.
The resource is temporarily located at a different URL for now.
The response to this request can be found at a different URL using a GET request.
The resource has not changed since the last request, so the cached version can be used.
The requested resource must be accessed through the proxy specified in the Location header.
The resource is temporarily at a different URL and the request method must not change.
The resource has permanently moved and the request method must not change.
Client Error
The request contains an error or cannot be fulfilled. The client should modify the request before retrying.
The server cannot process the request due to a client-side error in the request.
The request requires authentication and valid credentials were not provided.
This code is reserved for future use in digital payment systems.
The server understood the request but refuses to authorize it.
The server cannot find the requested resource at this URL.
The HTTP method used is not supported for this URL.
The server cannot produce a response matching the client's Accept headers.
The client must first authenticate with the proxy server.
The server timed out waiting for the client to finish sending the request.
The request conflicts with the current state of the resource on the server.
The resource has been permanently removed and will not be available again.
The server requires a Content-Length header that was not included in the request.
One or more conditions in the request headers evaluated to false on the server.
The request body is larger than the server is willing to process.
The requested URL is longer than the server is willing to interpret.
The server does not support the media type of the request body.
The requested byte range is outside the bounds of the resource.
The server cannot meet the requirements specified in the Expect request header.
The server refuses to brew coffee because it is, permanently, a teapot.
The request was sent to a server that cannot produce a response for it.
The request body is syntactically correct but contains semantic errors.
The resource is currently locked and cannot be modified.
The request failed because it depended on another request that also failed.
The server is unwilling to process a request that might be replayed.
The server requires the client to switch to a different protocol to proceed.
The server requires the request to include conditional headers.
The client has sent too many requests in a given amount of time.
The server refuses the request because the headers are too large.
The resource is unavailable due to legal restrictions or censorship demands.
Server Error
The server failed to fulfill a valid request. These indicate problems on the server side, not with the client.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server acting as a gateway received an invalid response from the upstream server.
The server is temporarily unable to handle the request due to overload or maintenance.
The gateway server did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
The server has a configuration error in its content negotiation setup.
The server cannot store the representation needed to complete the request.
The server detected an infinite loop while processing a WebDAV request.
The server requires additional extensions to the request to fulfill it.
The client needs to authenticate to gain network access, typically via a captive portal.
Test Your Redirects
Use our free redirect checker to trace redirect chains, detect loops, and verify status codes for up to 50 URLs at once.