Free Online Redirect Checker
Trace a URL redirect chain and inspect status codes.
Redirect chain
Response headers at the destination
| Header | Value |
|---|
The server follows redirects without a browser and stops after six hops. A chain that hits that limit, or that revisits a URL, is flagged below. Some sites behave differently for automated requests, so confirm unusual results in a private browser window.
About the Redirect Checker
Redirects are supposed to be invisible. A visitor types an old address, the server answers with a 301 or 302, the browser requests the new location, and the page appears. When a chain grows long, loops, or ends at an error, the experience becomes slow or broken while the original URL still looks fine in a bookmark. This tool traces each hop and shows the status code and target at every step, so you can see exactly where traffic is being sent.
Status codes you may see
- 301 Moved Permanently: the canonical new address. Search engines transfer signals and browsers cache it aggressively.
- 302 Found and 307 Temporary Redirect: a short-term move that should not be cached indefinitely. A 307 preserves the request method.
- 303 See Other: commonly used after a form submission to send the browser to a confirmation page with a GET.
- 308 Permanent Redirect: like a 301 but guaranteed to preserve the method and body.
- 200 OK: the chain ended at a real page. A 4xx or 5xx final status means the destination itself is failing.
Chains often reveal configuration mistakes that are hard to spot otherwise. A site may redirect to HTTPS, then to the www host, then to a trailing-slash variant, then to a language path: four hops before any content loads. Each hop costs a round trip, and on a slow mobile connection the delay is noticeable. Consolidating those rules into a single redirect is a simple performance win. A loop, where a URL eventually points back to itself, is worse: browsers stop with an error page, and crawlers may abandon the URL entirely.
The server follows up to six redirects, which is enough for normal sites and low enough to avoid runaway chains. If the limit is reached, the report warns you and shows the path it managed to collect. A repeated URL in the chain is also flagged as a probable loop. Note that this inspection uses a server-side request with its own user agent and no cookies. Sites that redirect based on a session, a country header, or a device type may produce a different chain than a real visitor would see. Use the result as a strong hint, then verify edge cases in a browser.
The final destination's headers are included because they often explain the outcome: a cache-control directive, a content type, or a server banner can clarify whether a page is being served from a cache or generated fresh. The report can be copied or downloaded for a ticket, and no URL you enter is stored beyond the current request.
How to use this tool
- Enter the URL exactly as a visitor would request it.
- Click Check redirects. The server requests each hop without following the chain in the browser.
- Review the hop list, status codes, and final destination.
- Copy the report or download it as JSON when you need to document the chain.
Frequently asked questions
Why does the chain end before reaching a page?
The checker stops after six redirects. That usually means a loop or a misconfigured rule. It can also stop on a network error or a response that is not a redirect, such as a 404.
Is a 302 bad for SEO?
Not inherently. A temporary redirect is appropriate for short-lived changes. For a permanent move, a 301 or 308 is clearer because it tells search engines to consolidate the old URL with the new one.
Why do I see a different destination in my browser?
Server-side checks do not send your cookies, language preferences, or client hints. A site may route logged-in users, mobile devices, or specific regions differently. Test in a private window to compare.