How many hops to the final URL - catch redirect loops before SEO and users suffer.
Every hop with status code and URL
Permanent or temporary - which type is used?
Where the chain ends, or where it loops
No account required · Free · Results in under 1s
HTTP redirect chains explained
Long redirect chains slow page loads and dilute SEO equity; loops block access entirely - common after HTTPS rollouts, www changes, or CMS migrations.
A redirect checker follows 301, 302, and other HTTP redirects hop by hop until a final URL or a loop. A free redirect trace shows each status code and Location header along the way.
Run a one-time check after domain moves, HTTPS enablement, or URL structure changes. Add URLs to TotalSiteControl monitoring for alerts when chains or final destinations change.
Free TotalSiteControl monitoring - email alerts, no credit card required.
Get notified when chains, status codes, or final URLs change.
Scheduled checks catch redirect loops before users hit them.
See past traces for SEO audits and migration verification.
Instant results · No signup · Check anytime
It follows HTTP redirects hop by hop and shows each status code, URL, and Location header until the final destination or a loop.
Yes. Trace any public URL instantly - no signup, no credit card, and no limit on one-off checks.
Chains from HTTP to HTTPS, www rules, and trailing slashes stack up. Long chains slow pages and can hurt SEO.
301 is permanent and passes SEO equity to the target. 302 is temporary. Using the wrong type after migrations can dilute search rankings.
Yes - 301, 302, 303, 307, and 308 redirects are followed until a final response or a loop is detected.
Conflicting rules - such as http, www, and non-www variants pointing at each other. The checker stops and flags the loop.
The redirect checker focuses on the chain only. HTTP Headers shows full response headers and security flags for a single request.
After domain moves, HTTPS rollout, or CMS URL changes. Monitoring alerts when final URLs or chains change.