↪ HTTP Redirect Tracer
Follow the complete redirect chain step-by-step - status codes, response times, HSTS, and final destination.
Why redirect chains matter
Each redirect adds latency to page load time and dilutes PageRank. Search engines follow redirect chains but prefer a single, direct path to the final URL. An HTTP-to-HTTPS redirect that passes through multiple hops is both a performance and security issue.
What we detect
- Chain length - how many hops before the final destination
- HTTP exposure - any unencrypted HTTP hops in the chain (SSL stripping risk)
- 301 vs 302 - temporary redirects don't pass SEO link equity
- HSTS - whether each hop includes Strict-Transport-Security
- Response time - milliseconds per hop and total chain time