Check Server Status

Enter up to 10 URLs with http:// or https://
Each url with new string

Check Server Status

About the tool

The need to constantly check the status of servers arises if you have many websites. You may also need to check the status of the server if you are using the Internet and you are unable to connect to a certain website. The server check status can determine whether your server is blocked or the server is down.

How to use?

You can monitor server status and this check server status tool can be very handy for you. All you have to do is put the URL in the box and click on the "Check Server Status" button. After a few seconds, you will see results that will give you a clear guess as to the state of the server.

List of HTTP status codes with descriptions

There are over 40 official HTTP status codes in total. There are about the same number of unofficial ones, but we will not consider them in this article. Even many of the official ones are extremely rare.

1xx Informational - information codes

HTTP 100 Continue - "Continue". Indicates that the server has received the initial part of the request and is ready to accept the rest of it. Dispatched when the Expect header is present in the request.
HTTP 101 Switching Protocols - "Switch protocol". Indicates that the server is changing the protocol. Dispatched when an Upgrade header is present in the request.
HTTP 103 Early Hints. Preliminary answer with part of the headers. Used when the server cannot quickly generate all the headers. Their full list will appear in the final answer.

2xx Success - codes of successfully completed requests

HTTP 200 OK - Success. The server processed the request successfully.
HTTP 201 Created - "Created". The server successfully processed the request and created a new resource.
HTTP 202 Accepted. The server has started processing the request, but has not yet finished the process. Ultimately, the processing of the request may or may not complete.
HTTP 203 Non-Authoritative Information. The server successfully processed the request, but the proxy through which the response to the request passed changed this response.
HTTP 204 No Content. The server successfully processed the request, but other than the response headers, there is no content to send in response.
HTTP 205 Reset Content. The server successfully processed the request and sent in response a command to reset the data that the user entered before sending the request.
HTTP 206 Partial Content. The server successfully processed the partial request and sent the content specified in the Content-Range header. Used, for example, to resume a paused download.
HTTP 207 Multi-Status - "Multi-status". The query results contain information about several independent operations.

3xx Redirection - redirection codes

HTTP 300 Multiple Choices. The server sends this code when there are several possible responses to the request. For example, there are several types of files on the server that meet the request criteria. The user or user-agent must choose one of the options.
HTTP 301 Moved Permanently - "Moved permanently". The requested resource is now available under the new URI and it is worth using it for subsequent requests.
HTTP 302 Found - Found. Previously, this code was called 302 Moved Temporarily. The requested resource is temporarily available at a different URI and it is worth using the old URI for subsequent requests.
HTTP 303 See Other. The requested resource must be searched for using a different URI with a GET request method, even though the original request may have had a different method.
HTTP 304 Not Modified. The requested resource has not been changed, so use the cached version of it.
HTTP 305 Use Proxy - "Use a proxy". The resource request must be made through a proxy. This code is no longer used.
HTTP 306 Switch Proxy - "Reserved". The request to the resource must be made through the proxy, which the server specified in the response headers. This code is no longer used.
HTTP 307 Temporary Redirect. The requested resource is temporarily available at a different URI. When requesting a new URI, the client MUST use the same method as when making the original request. This code has the same logic as 302 Found. It was introduced because with the 302 HTTP code, some clients changed the request type.
HTTP 308 Permanent Redirect - "Permanent redirect". The URI of the requested resource has changed forever and in all subsequent requests it is worth referring to it. This code is similar to 301 Moved Permanently, but in the case of 308, you cannot change the request type from POST to GET.

4xx Client Error - client error codes

HTTP 400 Bad Request - "Bad request". The server cannot process the request because it does not understand it. For example, due to a syntax error.
HTTP 401 Unauthorized - "Unauthorized". The server cannot process the request without authentication. You need to add the Authorization field to the request header or check the correctness of the data in this field, if it is already present.
HTTP 402 Payment Required. Initially, this code was supposed to be used in payment systems. It is currently not in use.
HTTP 403 Forbidden - "Forbidden". The server refuses to process the request because the user does not have permission to view the content.
HTTP 404 Not Found. The server cannot find the requested resource.
HTTP 405 Method Not Allowed. The method specified in the request cannot be used. The server MUST specify available methods in the Allow header.
HTTP 406 Not Acceptable. There is no content on the server that meets the characteristics specified in the request headers.
HTTP 407 Proxy Authentication Required. This code has the same logic as 401 Unauthorized, but in this case the client must be authorized to use the proxy.
HTTP 408 Request Timeout - "The request response timed out." The server did not receive the entire request within the maximum time allowed for this. Such a code can occur when transferring large amounts of data using the PUT or POST method.
HTTP 409 Conflict - "Conflict". The server was unable to process the request due to the content of this request conflicting with the server parameters. This can happen if two clients try to modify a resource at the same time using the PUT method.
HTTP 410 Gone - "Removed". The request could not be processed because the resource was deleted. The new location of the resource is unknown.
HTTP 411 Length Required - Content-Length header value is required. The server refuses to process the request until its Content-Length is specified in its headers.
HTTP 412 Precondition Failed. The server cannot process the request because its headers indicate a condition that cannot be met.
HTTP 413 Payload Too Large - Request body is too large. The request body exceeds the maximum size the server can accept.
HTTP 414 URI Too Long - The URI is too long. The URI exceeds the maximum length allowed. This can happen if the wrong method is selected (GET instead of POST).
HTTP 415 Unsupported Media Type - "Unsupported media data format". The server refuses to process the request because its content contains data in an invalid format for such a method.
HTTP 416 Range Not Satisfiable. The Range field specified an invalid range for the resource.
HTTP 417 Expectation Failed - Invalid value for the Expect field. The server cannot fulfill the condition in the Expect field in the request headers.
HTTP 418 I'm a teapot - "I'm a teapot." The message that the tea kettle should send when trying to brew coffee on it. This error code was introduced as an April Fool's joke in 1998.
HTTP 422 Unprocessable Entity - "Unprocessed request". The syntax of the request is correct, but due to a logical error, the server cannot execute it. This error code can occur if the request contains an XML document with a logical error.
HTTP 423 Locked - "Locked". The requested resource is blocked for requests with this method.
HTTP 424 Failed Dependency. The server was unable to fulfill the request because the requested action in it depended on another action and it did not work.
HTTP 426 Upgrade Required - "Protocol needs to be updated." The server refuses to process the request using the current protocol, but can do so after switching to a different version. The server MUST provide the required protocol version in the Upgrade field in the response headers.
HTTP 499 Client Closed Request. Non-standard code for Nginx to indicate a situation in which the client closed the connection while Nginx was processing the request.

5xx Server Error - server error codes

HTTP 500 Internal Server Error - "Internal server error". The server encountered an unexpected error while processing a request.
HTTP 501 Not Implemented. The server does not support the functionality that is required to process the request.
HTTP 502 Bad Gateway - "Invalid gateway". The server received an invalid response from the upstream server.
HTTP 503 Service Unavailable. The server is unavailable because it is overloaded or is undergoing technical work.
HTTP 504 Gateway Timeout - "The gateway is not responding." The server did not receive a timely response from the upstream server and closed the connection.
HTTP 505 HTTP Version Not Supported. The server does not support the HTTP version specified in the request headers.
HTTP 507 Insufficient Storage - "Not enough space". The server cannot complete the request because there is not enough free space on it to store the data required to complete the request.
HTTP 508 Loop Detected - Infinite Redirect Detected. The server canceled the operation because it encountered an infinite redirect while processing a request with the Depth: infinity parameter.
HTTP 509 Bandwidth Limit Exceeded - "The bandwidth of the channel has been exhausted." The site has reached the limit on the use of traffic on the hosting. This HTTP error code is not documented in the RFC and the only software that uses it is the bw / limited module that is included in the cPanel hosting control panel.