| Code | Description | Explanation | Possible diagnosis | Client Suggestion |
| | | | Contact own IT | Take action if repeated | Check if page exists | Contact CSM |
| 100 | Continue | The 100 Continue status code means that the initial part of the request has been received by the server and that the client should proceed with the request or ignore the response if the request has already finished. | None | | | | |
| 101 | Switching Protocols | The requester has asked the server to switch protocols and the server has agreed to do so. | None | | | | |
| 102 | Processing (WebDAV; RFC 2518) | A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. [3] This prevents the client from timing out and assuming the request was lost. The status code is deprecated.[4] | None | | | | |
| 103 | Early Hints (RFC 8297) | Used to return some response headers before final HTTP message.[5] | None | | | | |
| 200 | OK | Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action. | None | | | | |
| 201 | Created | The request has been fulfilled, resulting in the creation of a new resource.[6] | Unknown server issue / configuration | | | | ✔️ |
| 202 | Accepted | The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 203 | Non-Authoritative Information (since HTTP/1.1) | The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.[7][8] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 204 | No Content | The server successfully processed the request, and is not returning any content. | Unknown server issue or page does not exist / page contains no content. | ✔️ | ✔️ | ✔️ | |
| 205 | Reset Content | The server successfully processed the request, asks that the requester reset its document view, and is not returning any content. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 206 | Partial Content | The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 207 | Multi-Status (WebDAV; RFC 4918) | The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.[9] | N/A | ✔️ | | | ✔️ |
| 208 | Already Reported (WebDAV; RFC 5842) | The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again. | N/A | ✔️ | | | ✔️ |
| 226 | IM Used (RFC 3229) | The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.[10] | N/A | ✔️ | | | ✔️ |
| 300 | Multiple Choices | Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 301 | Moved Permanently | This and all future requests should be directed to the given URI. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 302 | Found (Previously "Moved temporarily") | Tells the client to look at (browse to) another URL. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect with the same method (the original describing phrase was "Moved Temporarily"),[12] but popular browsers implemented 302 redirects by changing the method to GET. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.[11] | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 303 | See Other (since HTTP/1.1) | The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 304 | Not Modified | Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 305 | Use Proxy (since HTTP/1.1) | The requested resource is available only through a proxy, the address for which is provided in the response. For security reasons, many HTTP clients (such as Mozilla Firefox and Internet Explorer) do not obey this status code.[13] | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 307 | Temporary Redirect (since HTTP/1.1) | In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 308 | Permanent Redirect | This and all future requests should be directed to the given URI. 308 parallel the behaviour of 301, but does not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 400 | Bad Request | The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). | Server issue or crawler issue | | ✔️ | ✔️ | ✔️ |
| 401 | Unauthorized | Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. 401 semantically means "unauthorised", the user does not have valid authentication credentials for the target resource.Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.[citation needed] | Login required to access page | ✔️ | | | ✔️ |
| 402 | Payment Required | Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, for example, by GNU Taler,[14] but that has not yet happened, and this code is not widely used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.[15] Sipgate uses this code if an account does not have sufficient funds to start a call.[16] Shopify uses this code when the store has not paid their fees and is temporarily disabled.[17] Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments.[18] | Payment required to access page | ✔️ | | | ✔️ |
| 403 | Forbidden | The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). This code is also typically used if the request provided authentication by answering the WWW-Authenticate header field challenge, but the server did not accept that authentication. The request should not be repeated. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 404 | Not Found | The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 405 | Method Not Allowed | A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 406 | Not Acceptable | The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 407 | Proxy Authentication Required | The client must first authenticate itself with the proxy. | Login required to access page | ✔️ | | | ✔️ |
| 408 | Request Timeout | The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time." | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 409 | Conflict | Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 410 | Gone | Indicates that the resource requested was previously in use but is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead. | Unknown server issue or page does not exist / page contains no content. | ✔️ | ✔️ | ✔️ | |
| 411 | Length Required | The request did not specify the length of its content, which is required by the requested resource. | Bad crawler request | | | ✔️ | ✔️ |
| 412 | Precondition Failed | The server does not meet one of the preconditions that the requester put on the request header fields. | Bad crawler request | | | ✔️ | ✔️ |
| 413 | Payload Too Large | The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large" in RFC 2616.[19] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 414 | URI Too Long | The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously in RFC 2616.[20] | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 415 | Unsupported Media Type | The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 416 | Range Not Satisfiable | The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously RFC 2616.[21] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 417 | Expectation Failed | The server cannot meet the requirements of the Expect request-header field.[22] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 418 | I'm a teapot (RFC 2324, RFC 7168) | This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[23] This HTTP status is used as an Easter egg in some websites, such as Google.com's "I'm a teapot" easter egg.[24][25][26] Sometimes, this status code is also used as a response to a blocked request, instead of the more appropriate 403 Forbidden.[27][28] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 419 | Page Expired | Used by the Laravel Framework when a CSRF Token is missing or expired. | Login required to access page | ✔️ | | | ✔️ |
| 421 | Misdirected Request | The request was directed at a server that is not able to produce a response (for example because of connection reuse). | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 422 | Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic errors.[9] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 423 | Locked (WebDAV; RFC 4918) | The resource that is being accessed is locked.[9] | Retry later | | ✔️ | | ✔️ |
| 424 | Failed Dependency (WebDAV; RFC 4918) | The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).[9] | Retry later | | ✔️ | | ✔️ |
| 425 | Too Early (RFC 8470) | Indicates that the server is unwilling to risk processing a request that might be replayed. | Retry later | | ✔️ | | ✔️ |
| 426 | Upgrade Required | The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field. | Bad crawler request | | | ✔️ | ✔️ |
| 428 | Precondition Required (RFC 6585) | The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.[29] | Retry later | | ✔️ | | ✔️ |
| 429 | Too Many Requests (RFC 6585) | The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.[29] | Retry later | | ✔️ | | ✔️ |
| 430 | Request Header Fields Too Large | Used by Shopify, instead of the 429 Too Many Requests response code, when too many URLs are requested within a certain time frame.[36] | Retry later | | ✔️ | | ✔️ |
| 431 | Request Header Fields Too Large (RFC 6585) | The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.[29] | Bad crawler request | | | ✔️ | ✔️ |
| 440 | Login Time-out | The client's session has expired and must log in again.[43] | Login required to access page | ✔️ | | | ✔️ |
| 444 | No Response | Used internally[50] to instruct the server to return no information to the client and close the connection immediately. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 449 | Retry With | The server cannot honour the request because the user has not provided the required information.[44] | Login required to access page | ✔️ | | | ✔️ |
| 450 | Blocked by Windows Parental Controls | The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.[37] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 451 | Unavailable For Legal Reasons (RFC 7725) | A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.[30] | Page target URL incorrect / Server configuration | ✔️ | | ✔️ | |
| 460 | Error 460 | Client closed the connection with the load balancer before the idle timeout period elapsed. Typically when client timeout is sooner than the Elastic Load Balancer's timeout.[55] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 463 | Error 463 | The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.[55] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 464 | Error 464 | Incompatible protocol versions between Client and Origin server.[55] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 494 | Request header too large | Client sent too large request or too long header line. | Bad crawler request | | | ✔️ | ✔️ |
| 495 | SSL Certificate Error | An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate. | Bad crawler request | | | ✔️ | ✔️ |
| 496 | SSL Certificate Required | An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided. | Bad crawler request | | | ✔️ | ✔️ |
| 497 | HTTP Request Sent to HTTPS Port | An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests. | Bad crawler request | | | ✔️ | ✔️ |
| 498 | Invalid Token | Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.[38] | Login required to access page | ✔️ | | | ✔️ |
| 499 | Client Closed Request | Used when the client has closed the request before the server could send a response. | Bad crawler request | | | ✔️ | ✔️ |
| 499 | Token Required | Returned by ArcGIS for Server. Code 499 indicates that a token is required but was not submitted.[38] | Login required to access page | ✔️ | | | ✔️ |
| 500 | Internal Server Error | A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. | Unknown server issue / configuration | | | | ✔️ |
| 501 | Not Implemented | The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API). | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 502 | Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server. | Unknown server issue / configuration | | | | ✔️ |
| 503 | Service Unavailable | The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[31] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 504 | Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. | Unknown server issue / configuration | | | | ✔️ |
| 505 | HTTP Version Not Supported | The server does not support the HTTP version used in the request. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| >506 | Variant Also Negotiates (RFC 2295) | Transparent content negotiation for the request results in a circular reference.[32] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| >507 | Insufficient Storage (WebDAV; RFC 4918) | The server is unable to store the representation needed to complete the request.[9] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| >508 | Loop Detected (WebDAV; RFC 5842) | The server detected an infinite loop while processing the request (sent instead of 208 Already Reported). | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| >509 | Bandwidth Limit Exceeded | The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.[39] | Retry later | | ✔️ | | ✔️ |
| >510 | Not Extended (RFC 2774) | Further extensions to the request are required for the server to fulfil it.[33] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 511 | Network Authentication Required (RFC 6585) | The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).[29] | Login required to access page | ✔️ | | | ✔️ |
| 520 | Web Server Returned an Unknown Error | The origin server returned an empty, unknown, or unexpected response to Cloudflare.[52] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 521 | Web Server Is Down | The origin server refused connections from Cloudflare. Security solutions at the origin may be blocking legitimate connections from certain Cloudflare IP addresses. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 522 | Connection Timed Out | Cloudflare timed out contacting the origin server. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 523 | Origin Is Unreachable | Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect or missing. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 524 | A Timeout Occurred | Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 525 | SSL Handshake Failed | Cloudflare could not negotiate a SSL/TLS handshake with the origin server. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 526 | Invalid SSL Certificate | Cloudflare could not validate the SSL certificate on the origin web server. Also used by Cloud Foundry's gorouter. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 527 | Railgun Error | Error 527 indicates an interrupted connection between Cloudflare and the origin server's Railgun server.[53] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 529 | Site is overloaded | Used by Qualys in the SSLLabs server testing API to signal that the site can't process the request.[40] | Retry later | | ✔️ | | ✔️ |
| 530 | Error 530 | Error 530 is returned along with a 1xxx error.[54] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 561 | Unauthorized | An error around authentication returned by a server registered with a load balancer. You configured a listener rule to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user.[55] | Login required to access page | ✔️ | | | ✔️ |
| 598 | (Informal convention) Network read timeout error | Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.[42] | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 599 | Network Connect Timeout Error | An error used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy. | Unknown server issue / configuration | ✔️ | ✔️ | ✔️ | |
| 999 | Request Denied | When sending an HTTP GET or HEAD request to LinkedIn for a specific profile, such as the page for a company or an individual, the 999 Request Denied status code response is returned based on, among other things, the user agent. | Login required to access page | ✔️ | | | ✔️ |
