The redirect checker follows a URL through every redirect until it reaches a page that answers directly. Each step shows the status code (301, 302, 307, 308), the Location it points to, the server IP and the time it took. You see the final address and how many redirects it took to get there.
Use it to check that http:// goes to https:// in one step, that www and non-www versions end up at the same place, that an old page moved permanently (301) rather than temporarily (302), or simply to see where a shortened link really leads before you click it. Redirect loops and redirects to unsafe destinations are detected and stopped.
How to use the Redirect Checker tool
- Paste the address, for example
http://example.comor a short link. - Optionally pick a user agent (mobile and Googlebot can be redirected differently).
- Click Check redirects.
- Read the chain from top to bottom; the last step is the final page.
Why use ToolOrca Redirect Checker
- Follows up to 10 redirects, checking every step
- Status code, target, server IP and time per step
- Detects redirect loops and unsupported targets
- Desktop, mobile, Googlebot and curl user agents
- Headers of each step available on demand
301 or 302 – which should I use?
Use 301 (or 308) when a page has moved for good: search engines move the ranking to the new address. Use 302 (or 307) only for temporary moves, such as a maintenance page. 307 and 308 also keep the request method, which matters for forms and APIs.
Why redirect chains hurt
Each redirect is another round trip before the page starts loading – on mobile networks that can add hundreds of milliseconds. Search engines follow only a limited number of hops. Ideally every old URL redirects straight to its final address in one step: for example http://example.com directly to https://www.example.com/, not via https://example.com first.
Frequently asked questions
Does it follow JavaScript or meta refresh redirects?
No, only HTTP redirects (3xx status with a Location header), which is what search engines rely on.
What is a redirect loop?
Two or more addresses that redirect to each other forever. Browsers show "too many redirects". The tool stops and points out where the loop starts.
Is it safe to check a suspicious short link?
Yes. Our server follows the redirects; your browser never opens the target.
Why did it stop at a redirect?
Redirects to other ports, IP addresses, private networks or non-web schemes are not followed for safety.
Can I check a device on my home or office network?
No. For safety, private and local addresses (192.168.x.x, 10.x.x.x, localhost, .local names and similar) are refused. Our server can only test public hosts on the internet.