Look up any HTTP status code or check the live status of a URL.
Enter an HTTP status code or search by name
The initial part of the request was received. The client should continue sending the rest of the request.
The server is switching protocols as requested by the client, e.g. upgrading HTTP to WebSocket.
WebDAV: the server has received the request and is still processing it. No response is available yet.
Allows the server to send Link headers before the final response, so the browser can start preloading resources early.
The request succeeded. The response body contains the requested resource or the result of the action.
The request succeeded and a new resource was created. The Location header points to the new resource URL.
The request was accepted for processing but processing has not been completed and may not be completed at all.
The response was transformed by a proxy. The payload was modified from the 200 OK response of the origin server.
The server fulfilled the request successfully but has no content to return. The response body is empty.
The server fulfilled the request. The client should reset the document view, e.g. clear a form after submission.
The server is delivering only part of the resource in response to a Range header. Used for video streaming and download resume.
WebDAV: the response body is an XML message containing status information for multiple independent operations.
WebDAV: the members of a DAV binding have already been enumerated in a previous reply and will not be included again.
The server fulfilled a GET request for the resource and the response is a representation of the result of one or more instance-manipulations.
The request has more than one possible response. The user agent or user should choose one. Usually accompanied by a list of choices.
The resource URL has permanently changed. Clients and search engines should update their links to the new URL in the Location header.
The resource is temporarily at a different URL. Clients should continue using the original URL for future requests.
Redirects the client to a different URL via GET. Commonly used after a POST to prevent form resubmission on page refresh.
The resource has not changed since the version specified in the request headers. The client should use its cached copy.
Temporary redirect. The client must preserve the original HTTP method and body - a POST stays a POST, unlike 302.
Permanent redirect that preserves the HTTP method. A POST stays a POST. Use this instead of 301 for non-GET redirects.
The server cannot process the request due to a client error - malformed syntax, invalid framing, or deceptive routing.
Authentication is required and the request has not been authenticated. Respond with valid credentials in the Authorization header.
Reserved for future use. Some APIs use it to signal that a paid subscription or quota limit has been exceeded.
The server understood the request but refuses to fulfill it. Re-authenticating will not help - the client lacks permission.
The server cannot find the requested resource. The URL is not recognized, the resource does not exist, or it has been removed.
The HTTP method is not supported for this resource. The Allow header in the response lists the supported methods.
No content matching the Accept headers could be found. The server cannot produce a response in the requested format.
Authentication is required by the proxy server between the client and the origin server.
The server timed out waiting for the complete request from the client. The client may retry the request.
The request conflicts with the current state of the server. Common with edit conflicts or duplicate resource creation.
The resource has been permanently removed with no forwarding address. Unlike 404, this signals intentional deletion.
The server refuses to accept the request without a defined Content-Length header.
The server does not meet one or more preconditions specified in the request headers (If-Match, If-Unmodified-Since, etc.).
The request body exceeds the server's processing limits. The server may close the connection or return a Retry-After header.
The request URI is longer than the server is willing to interpret. Often caused by GET requests that should use POST.
The Content-Type or Content-Encoding of the request body is not supported by the server.
The Range header in the request specifies a range that cannot be fulfilled, e.g. it exceeds the file size.
The expectation given in the Expect request header could not be met by the server.
Any attempt to brew coffee with a teapot should result in this error. An April Fools joke from 1998 that became a real standard.
The request was directed at a server that is unable to produce a response for the combination of scheme and authority.
The request was well-formed but could not be processed due to semantic errors. Common in REST APIs with validation failures.
WebDAV: the resource being accessed is locked.
WebDAV: the request failed because it depends on another request that failed.
The server refuses to process a request that might be replayed to guard against replay attacks.
The server refuses to perform the request using the current protocol. The client must switch to the protocol in the Upgrade header.
The origin server requires the request to be conditional to prevent the lost-update problem.
The client has sent too many requests in a given amount of time (rate limiting). Check the Retry-After header for when to retry.
The server refuses to process the request because its header fields are individually or collectively too large.
The resource cannot be legally provided in this jurisdiction. Named after Ray Bradbury's Fahrenheit 451.
The server encountered an unexpected condition that prevented it from fulfilling the request. Check server logs for details.
The server does not support the functionality required to fulfill the request method.
The server, acting as a gateway or proxy, received an invalid response from an inbound server.
The server is temporarily unable to handle the request due to overload or scheduled maintenance. Check Retry-After.
The server, acting as a gateway or proxy, did not receive a timely response from an upstream server.
The HTTP protocol version used in the request is not supported by the server.
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent negotiation itself.
WebDAV: the server is unable to store the representation needed to complete the request.
WebDAV: the server terminated an operation because it encountered an infinite loop while processing the request.
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access. Used by captive portals in hotels, airports, and Wi-Fi hotspots.
HTTP status codes are three-digit numbers returned by a web server in response to every HTTP request. The first digit defines the category: 1xx informational, 2xx success, 3xx redirection, 4xx client errors, and 5xx server errors. Understanding them is essential for debugging APIs, diagnosing redirect chains, and interpreting web server logs.
The live URL checker fetches the final status code of any URL from a Cloudflare edge server, following redirects and measuring response time. Useful for checking whether a redirect is permanent (301) or temporary (302), or whether a page returns a 200 even when a CMS shows a soft 404.