List of all Http Status codes in one place.
Monitor uptime and Http Status Code of your service.
100 - Continue
The server has received the request headers, and the client should proceed to send the request body.
101 - Switching Protocols
The requester has asked the server to switch protocols.
102 - Processing
This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.
103 - Early Hints
Used to return some response headers before final HTTP message.
200 - OK
The request is OK (this is the standard response for successful HTTP requests).
201 - Created
The request has been fulfilled, and a new resource is created.
202 - Accepted
The request has been accepted for processing, but the processing has not been completed.
203 - Non-Authoritative Information
The request has been successfully processed, but is returning information that may be from another source.
204 - No Content
The request has been successfully processed, but is not returning any content.
205 - Reset Content
The request has been successfully processed, but is not returning any content, and requires that the requester reset the document view.
206 - Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
207 - Multi-Status
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.
2xx - Successful
2xx codes indicate successful responses usually this means the action requested by the client was received, understood and accepted successfully.
208 - Already Reported
The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
218 - This is fine (Apache Web Server)
Used as a catch-all error condition for allowing response bodies to flow through Apache when ProxyErrorOverride is enabled.
226 - IM Used
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.
300 - Multiple Choices
A link list. The user can select a link and go to that location. Maximum five addresses.
301 - Moved Permanently
The requested page has moved to a new URL.
302 - Found
The requested page has moved temporarily to a new URL.
303 - Not Modified
Indicates the requested page has not been modified since last requested.
304 - Not Modified
Indicates the requested page has not been modified since last requested.
306 - Switch Proxy
No longer used. Originally meant \"Subsequent requests should use the specified proxy.\"
307 - Temporary Redirect
The requested page has moved temporarily to a new URL.
308 - Resume Incomplete
Used in the resumable requests proposal to resume aborted PUT or POST requests.
400 - Bad Request
The request cannot be fulfilled due to bad syntax.
100 - Continue
The server has received the request headers, and the client should proceed to send the request body.
401 - Unauthorized
The request was a legal request, but the server is refusing to respond to it. For use when authentication is possible but has failed or not yet been provided.
402 - Payment Required
Not yet implemented by RFC standards, but reserved for future use.
403 - Forbidden
The request was a legal request, but the server is refusing to respond to it.
404 - Not Found
The requested page could not be found but may be available again in the future.
405 - Method Not Allowed
A request was made of a page using a request method not supported by that page.
406 - Not Acceptable
The server can only generate a response that is not accepted by the client.
407 - Proxy Authentication Required
The client must first authenticate itself with the proxy.
408 - Request Timeout
The server timed out waiting for the request.
409 - Conflict
The request could not be completed because of a conflict in the request.
410 - Gone
The requested page is no longer available.
408 - Request Timeout
The server timed out waiting for the request.
409 - Conflict
The request could not be completed because of a conflict in the request.
410 - Gone
The requested page is no longer available.
411 - Length Required
The \"Content-Length\" is not defined. The server will not accept the request without it.
412 - Precondition Failed
The precondition given in the request evaluated to false by the server.
413 - Request Entity Too Large
The server will not accept the request, because the request entity is too large.
414 - Request-URI Too Long
The server will not accept the request, because the URL is too long. Occurs when you convert a POST request to a GET request with a long query information.
415 - Unsupported Media Type
The server will not accept the request, because the media type is not supported.
410 - Gone
The requested page is no longer available.
416 - Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion.
417 - Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418 - I'm a teapot
Any attempt to brew coffee with a teapot should result in the error code \"418 I'm a teapot\". The resulting entity body MAY be short and stout.
419 - Page Expired (Laravel Framework)
Used by the Laravel Framework when a CSRF Token is missing or expired..
420 - Method Failure (Spring Framework)
A deprecated response used by the Spring Framework when a method has failed.
421 - Misdirected Request
The request was directed at a server that is not able to produce a response (for example because a connection reuse).
422 - Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
423 - Locked
The resource that is being accessed is locked.
424 - Failed Dependency
The request failed due to failure of a previous request (e.g., a PROPPATCH).
426 - Precondition Required
The origin server requires the request to be conditional.
429 - Too Many Requests
The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes.
431 - Request Header Fields Too Large
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
440 - Login Time-out
The client's session has expired and must log in again. (IIS)
409 - Conflict
The request could not be completed because of a conflict in the request.
444 - Connection Closed Without Response
TA non-standard status code used to instruct nginx to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.
440 - Login Time-out
The client's session has expired and must log in again. (IIS)
444 - Connection Closed Without Response
TA non-standard status code used to instruct nginx to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.
449 - Retry With
The server cannot honour the request because the user has not provided the required information. (IIS).
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.
451 - Unavailable For Legal Reasons
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.
444 - Connection Closed Without Response
TA non-standard status code used to instruct nginx to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.
494 - Request Header Too Large
Used by nginx to indicate the client sent too large of a request or header line that is too long.
495 - SSL Certificate Error
An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.
444 - Connection Closed Without Response
TA non-standard status code used to instruct nginx to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.
496 - SSL Certificate Required
An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.
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.
498 - Invalid Token (Esri)
Returned by ArcGIS for Server. Code 498 indicates an expired or otherwise invalid token.
499 - Client Closed Request
A non-standard status code introduced by nginx for the case when a client closes the connection while nginx is processing the request.
409 - Conflict
The request could not be completed because of a conflict in the request.
500 - Internal Server Error
An error has occurred in a server side script, a no more specific message is suitable.
501 - Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502 - Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503 - Service Unavailable
The server is currently unavailable (overloaded or down).
504 - Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505 - HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 - Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.
507 - Insufficient Storage
The server is unable to store the representation needed to complete the request.
508 - Loop Detected
The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
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.
510 - Not Extended
Further extensions to the request are required for the server to fulfil it.
511 - Network Authentication Required
The client needs to authenticate to gain network access.
520 - Unknown Error
The 520 error is used as a \"catch-all response for when the origin server returns something unexpected\", listing connection resets, large headers, and empty or invalid responses as common triggers.
521 - Web Server Is Down"
The origin server has refused the connection from Cloudflare.
522 - Connection Timed Out
Cloudflare could not negotiate a TCP handshake with the origin server.
523 - Origin Is Unreachable
Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect.
524 - A Timeout Occurred
Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response.
525 - SSL Handshake Failed
Cloudflare could not negotiate a SSL/TLS handshake with the origin server.
526 - Invalid SSL Certificate
Used by Cloudflare and Cloud Foundry's gorouter to indicate failure to validate the SSL/TLS certificate that the origin server presented..
527 - Railgun Listener to Origin Error
Error 527 indicates that the request timed out or failed after the WAN connection had been established.
530 - Origin DNS Error
Error 530 indicates that the requested host name could not be resolved on the Cloudflare network to an origin server.
598 - 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.