Check Redirect Chain
Comments
200 (OK). Indicates a successful request and successful retrieval of data, if any was present in the header or body of the response
200 (OK). Indicates a successful request and successful retrieval of data, if any was present in the header or body of the response
301 (Moved Permanently). This status code tells the user that a permanent redirect to another page or site has occurred
302 (Found/Moved Temporarily). The requested URI has been temporarily moved to a new address. Taken from the Location field
403 (Forbidden). The server understood the request but refuses to fulfill it. Access to the resource is denied in this case
404 (Not Found). The server received the client's request but could not find a document matching it
500 (Internal Server Error). This is any error on the server side, rather than the client side
502 (Bad Gateway). The proxy or gateway server received an invalid response from the backend
504 (Gateway Timeout). The proxy or gateway server did not receive a response from the backend within the allotted time
0 (No Response). Not an actual server response code. Indicates that a connection was never established or no response was received at all. Usually caused by network-level blocking (e.g. DPI), the site being unreachable, a dropped connection, or a request timeout
Redirect Checker is a tool for checking Redirect chain on a website. The service sends HTTP-requests to the specified URL and sequentially monitors all redirects up to the final page, showing each step: the address, the HTTP response status, and the final address to which the redirect is made.
Checking the chain of redirects is useful when setting up 301 and 302 redirects after changing the domain, merging websites, moving the website to HTTPS, or changing the URL structure. The tool helps identify unnecessary intermediate redirects that slow down page loading and negatively affect the website’s indexing by search engines, as well as detect cyclic redirects and server configuration errors.
The service supports both HTTP and HTTPS connections and automatically detects the protocol when entering a domain without specifying the scheme. The server response status code is displayed for each step of the chain. (200, 301, 302, 404, 500 and others), which allows you to quickly locate the problem in the web server settings or redirect configuration.