Redirect Checker

How to use Redirect Checker

1. Paste the exact public HTTP or HTTPS URL you want to check, including the path and any non-sensitive query parameters.
2. Select Trace redirects to follow the server's HTTP Location responses.
3. Review each status and destination, then check whether the final response is the page you intended.

What is Redirect Checker?

HTTP redirects tell a client to request another URL using a redirect status and a Location header. This checker makes the chain visible so you can diagnose unnecessary hops, loops, HTTP-to-HTTPS transitions, and unexpected domain changes. It follows server responses without running JavaScript or maintaining a logged-in browser session.

• Trace public HTTP and HTTPS destinations in order
• Inspect response statuses and Location values
• Detect loops and report when the request limit is reached
• Review the final response reached by the diagnostic request

Interpreting the redirect chain

Check the status, source URL, and Location value at each step. An extra redirect can be intentional, but repeated loops prevent clients from reaching a final page. The checker stops after at most six requests or sooner when it reaches a response with no followable HTTP redirect.

Every destination must be public. Private network addresses and unsupported URL schemes are rejected. The tool does not follow JavaScript navigation or HTML meta refresh, and it does not forward your browser's cookies or Authorization header.

A practical example

Illustrative input only: http://example.com/old-page

Illustrative chain, not a live result:
301 · http://example.com/old-page
Location: https://example.com/new-page
200 · https://example.com/new-page

Learn a little more

Frequently asked questions