Redirects
Follow every redirect, from the first URL to the final response.
About this scan
Follows up to ten HTTP redirects using GET. Does not follow JavaScript or meta refresh redirects or send cookies. Duration includes DNS and requests.
Anyone with the result link can view the report. Reports expire after seven days. Query values and sensitive headers are redacted.
A snapshot, not a security guarantee.
From scan to solution
Make every redirect lead somewhere useful
A redirect check shows the journey between a link and its destination. RedirectPath follows HTTP redirects and records each hop so you can spot detours, loops and unexpected status codes. These guides explain which redirect to choose, how to debug a broken chain and what to check when moving a site to HTTPS.
301 vs 302 vs 307 vs 308 redirects
Choose between permanent and temporary redirects, and understand when preserving the request method matters.
Read guide TroubleshootingHow to find and fix redirect chains and loops
Read a redirect trace, identify conflicting rules and shorten unnecessary detours between a URL and its destination.
Read guide HTTPS migrationsAn HTTP to HTTPS redirect checklist
Check certificates, paths, hostnames and final responses when moving public pages from HTTP to HTTPS.
Read guideA few useful answers
Frequently asked questions
Which redirects does RedirectPath follow?
RedirectPath follows up to ten HTTP redirects using GET requests and records the status codes and destinations. It does not run JavaScript or follow HTML meta refresh redirects, and it does not send cookies.
Should I use a 301, 302, 307 or 308 redirect?
Use permanent behavior for a lasting move and temporary behavior when the original URL is expected to remain relevant. 307 and 308 preserve the request method and body; 301 and 302 can allow POST to become GET. RedirectPath tests GET, so verify form or API behavior separately.
301 vs 302 vs 307 vs 308 redirectsWhy does my browser go somewhere different from the scan?
Your browser may have cookies, cached redirects, an HSTS policy or JavaScript-driven navigation that changes the journey. The scan makes requests without that browser state. Compare the exact starting URL and inspect the browser’s network panel to identify the difference.
Does reaching the redirect limit prove there is a loop?
No. A long chain of distinct URLs can also reach the ten-redirect limit. Inspect the recorded sequence for a repeated URL and read the reason the scan stopped. Conflicting host, HTTPS or trailing-slash rules are useful places to investigate.
How to find and fix redirect chains and loopsHow do I check an HTTP to HTTPS migration?
Start with the old HTTP URL, including a real page path. Verify that the chain reaches the intended HTTPS resource without losing needed path or query information. Also check certificates and browser behavior for each supported hostname.
An HTTP to HTTPS redirect checklist