Redirect Loop Checker

A redirect loop occurs when redirect rules send a request back to a URL already visited in the same path. Browsers eventually stop with a too-many-redirects error; search crawlers also cannot reach useful content through the loop.

Loops can take important pages completely offline even though the application itself is healthy. They often appear after changing HTTPS, reverse-proxy settings, trailing slashes, locale routing or authentication rules.

1. 1Enter the URL producing a redirect error.
2. 2Run the check and inspect repeated URLs in the recorded path.
3. 3Identify which infrastructure layer owns each redirect.
4. 4Change the conflicting rule and retest from the original URL.

• A repeated normalized URL indicates circular behavior.
• A safety-limit stop without an exact repeat can still indicate an abnormally long redirect path.
• A normal final 200 means no loop was observed during this request.

• CDN forces HTTPS while the origin redirects HTTPS back to HTTP.
• Locale middleware redirects `/` to `/en/` while another rule strips `/en/`.
• Trailing-slash rules disagree between framework and server.

• Choose one canonical protocol, host and path style.
• Remove duplicate redirect ownership where possible.
• Test with cookies cleared when authentication middleware is involved.

• Document which layer controls redirects.
• Add automated smoke tests for canonical host and protocol behavior.
• Retest both desktop and bot-like requests after infrastructure changes.

The tool detects the loop visible from its request context. Conditional redirects based on login state, geography or headers may behave differently elsewhere.