Developer tool
Redirect and HTTP Status Checker
Trace every redirect hop with its status code, Location header and timing. Check one URL or up to 20 at once and spot loops, long chains and slow hops.
Our server follows the URLs you enter, one request per hop, and shows the result. Nothing is stored.
How to use the redirect and http status checker
See exactly where a URL ends up
A link that "just redirects" can hide a chain of four hops, a temporary redirect that should be permanent, or a loop. This tool traces each hop by hand, so you see what a browser or crawler would experience.
How to use it
- Enter one URL, or paste up to 20 URLs, one per line.
- Press Trace. Each URL appears as a chain: the request, its status code, the Location it points to and the time that hop took.
- Look at the summary row: final URL, number of hops and total time.
- Export the table as CSV to share with a team.
Reading the status codes
- 200 the page loaded.
- 301 / 308 permanent redirect. Search engines pass signals to the new URL.
- 302 / 303 / 307 temporary redirect. Use only for genuinely short-term moves.
- 404 / 410 not found or gone.
- 429 / 5xx the server is limiting you or failing.
Common problems it finds
- Chains: http to https to www to a trailing-slash version. Point the first URL straight at the final one.
- Wrong type: a 302 left in place after a migration. Change it to 301.
- Loops: two rules sending visitors back and forth. The checker stops and flags the loop.
- Slow hops: a redirect that takes over a second adds that delay to every visit.
- Dead ends: a redirect that lands on a 404.
When to use it
Run it after a site migration or domain change, when you change URL structure, before launching a campaign link, and while auditing old backlinks.
Limits
The tool follows HTTP redirects only, sends a plain GET request without cookies, and caps each trace at 10 hops. Redirects that depend on location, language or login may differ from what your visitors see.
Frequently asked questions
What is the difference between 301 and 302?
301 (and 308) mean moved permanently: search engines transfer ranking signals and update their index. 302 (and 307) mean temporary: the original URL stays the one to index. Use permanent codes for lasting changes such as an http to https move.
How many redirects are too many?
Keep chains to one hop where you can. Each extra hop adds latency and Google stops following after about ten. The checker follows up to 10 hops and tells you when a chain is longer or loops.
Can I check many URLs at once?
Yes. Paste up to 20 URLs, one per line. Each is traced separately and the table shows its final destination, hop count and total time.
Does it follow JavaScript or meta refresh redirects?
No. It follows HTTP redirects (3xx with a Location header), which is what search engines and APIs rely on. Meta refresh and JavaScript redirects need a browser to run.
Why was my URL refused?
Only public http and https URLs on standard web ports are checked. Private addresses, localhost and internal names are blocked, and every redirect target is checked the same way.
Why do times differ between runs?
Each timing covers connecting and waiting for the response headers from our server to yours. Network distance, caching and server load change it from run to run.