Trace HTTP redirects and final destination
Trace 301, 302, 307 and 308 redirects, view each hop and check the final HTTP status of a public URL.
Follows public HTTP redirects manually for up to eight hops and reports the final status.
How to use the Redirect Checker
Trace 301, 302, 307 and 308 redirects, view each hop and check the final HTTP status of a public URL.
Formula and method
The checker requests each public URL without automatic redirects and follows the Location header for up to eight hops.
Example
Paste an old URL to see whether it returns 301, 302, 307 or 308 and where visitors and crawlers ultimately land.
Planning examples
These examples are mathematical scenarios designed to help with planning. They are not claims about typical market performance.
| Use | Recommendation |
|---|---|
| Planning | Use your own recent data whenever possible. |
| Comparisons | Keep the same definition and time period across comparisons. |
| Benchmarks | Treat public benchmarks as context rather than guarantees. |
How to interpret the result
Prefer direct redirects when possible. Long chains add latency and make migrations or canonicalization harder to maintain.
Frequently asked questions
Does this tool use an external API?
No. The calculation runs from the values you enter.
Is the result a guarantee?
No. It is a mathematical planning result based on your inputs.
Can I use my own real data?
Yes. Your own recent account or business data is usually the best input.
Can I compare different platforms?
Use caution because metric definitions and monetization models can differ by platform.