URL redirect checker
What this URL redirect checker does
Enter a starting URL and the tool follows the server's HTTP redirect responses in order, recording each hop's status code (for example 301 Moved Permanently, 302 Found, 307 Temporary Redirect) up to ten consecutive redirects. You see the chain your clients would traverse before the browser settles on a final address—essential when a marketing short link, CDN rule, or apex-to-www rule silently sends users through several hosts. It does not execute JavaScript or meta-refresh tags; only standard HTTP location hops appear.
When to use it
Use it while migrating domains, debugging "too many redirects" browser errors, auditing affiliate links, or proving which HTTPS hostname you truly terminate on after AWS, Cloudflare, or nginx layers each add a hop. After you read the chain, open HTTP headers lookup on the final URL for cache and security headers, and Safe URL checker on the ultimate destination if reputation matters.
Worked example
An old blog path should 301 to a new slug, but organic traffic tanked. You run URL redirect checker on the legacy URL: hop 1 returns 302 to a tracking domain, hop 2 returns 302 back to your apex, hop 3 finally 301s to the article. That extra volatility can dilute signals; you simplify to a single 301 from the old path straight to the final HTTPS canonical. Re-run the checker after deploy until the chain shortens as intended.
Frequently asked questions
Why stop at ten redirects?
Browsers and crawlers also cap chains to avoid infinite loops. If you hit the limit, fix the configuration rather than raising the ceiling.
301 versus 302 in practice?
301 signals a permanent move and generally consolidates ranking signals to the target; 302/307 imply temporary moves. Mixing them during migrations can confuse crawlers—align with your SEO runbook.
Does this show redirect bodies?
Redirects are usually empty bodies with a Location header. For payload inspection you need a client that captures full responses per hop.
Why might this differ from my browser?
Browsers follow HTML refreshes, cookies, and HSTS upgrades differently. This checker focuses on declared HTTP redirect sequences from the starting URL you submit.