WHOISRedirect Checker
See every hop in a URL's full redirect chain — not just where it ends up.
What is a redirect checker?
A redirect checker follows a web address from start to finish and shows every step it takes. Browsers jump straight to the final page and hide the hops in between; this redirect checker lists each one with its address, status code, a short explanation of the code and the location it pointed to next.
That makes it easy to spot long chains, loops, wrong destinations and redirects that use the wrong type of status code.
How the redirect checker works
The tool requests the address you enter, adding https:// if you leave it out. When the server answers with a redirect, the tool reads the Location header and requests that address next. It repeats this until a page answers without a redirect, up to a maximum of five redirects. If a chain needs more than five, which is also what happens with a loop, the check stops and says so. Each hop is recorded with its own status code.
How to use the redirect checker
- Enter the starting address, such as
http://example.comor a short link. - Press Check Redirects.
- Read the table from top to bottom: hop number, address, status code and where it redirects to.
- Check that the last row is the address you expect, with a 200 status.
What the redirect results mean
Permanent redirects: 301 and 308
These tell browsers and search engines that the content has moved for good. Search engines move their signals to the new address, so these are the right choice for site moves and for sending http to https.
Temporary redirects: 302 and 307
These say the original address will be used again. They suit short campaigns, A/B tests and maintenance, but are a common mistake for permanent moves.
No redirects
If the address answers directly, the tool says so and shows the status code it returned.
Why redirect chains matter
Each extra hop costs a full round trip before the page can start loading, which is noticeable on mobile connections. Long chains also make problems harder to track down. Search engines follow a limited number of hops, so a short, direct path is safest. The ideal is a single redirect straight to the final address.
Setting up redirects correctly
Redirects are usually set in the web server configuration, in an .htaccess file on Apache, in a CDN's rules or with a CMS plugin. Keep them in one place where possible, because rules spread across several systems are the main cause of chains and loops. After any change, test the old address, the http version and the www version here.
Common uses
- Checking that
httpandwwwversions all reach one final address. - Testing old URLs after a website redesign or domain move.
- Seeing where a shortened or tracking link really leads before you click it.
- Making sure permanent moves use 301 or 308 rather than 302.
Common problems and fixes
Too many redirects. The chain is longer than five hops or loops between two addresses. Common causes are conflicting rules in the server and in a plugin or CDN, both forcing HTTPS or www. Remove one of the rules.
Two hops where one would do. For example, http://example.com goes to https://example.com and then to https://www.example.com. Point the first address straight at the final one.
The chain ends in a 404. The redirect target no longer exists. Update the rule to point at a live page.
Related tools
- Website Status Checker adds timing and server details to the final result.
- HTTP Headers Checker shows every header the final page sends.
- HSTS Checker checks that HTTPS is enforced after the redirect.
- Bulk URL Status Checker tests many old URLs at once.
Frequently asked questions
How many redirects are too many?
Aim for one redirect at most between any address and its final page. Every extra hop adds a round trip and slows loading, especially on mobile. This tool follows up to five redirects, and a chain longer than that is reported as too many, which usually means a loop or conflicting rules.
Is a 301 or 302 redirect better for SEO?
For a permanent move, use a 301 or 308. It tells search engines the content has moved and that the new address should replace the old one in results. A 302 or 307 says the move is temporary, so the old address may stay indexed. Use those only for genuinely short-term changes.
What causes a redirect loop?
A loop happens when address A redirects to B and B redirects back to A, often because two systems apply opposite rules. A common example is a CDN sending traffic to HTTP while the server forces HTTPS, or a plugin and the server disagreeing about www. Remove or align the conflicting rule.
Why does my site redirect twice?
Usually because HTTP to HTTPS and non-www to www, or the reverse, are handled by separate rules. The first rule changes the protocol, then the second changes the host. Combine them so every variant redirects straight to the final address in a single hop.
Can I check where a short link goes?
Yes. Paste the short or tracking link and the tool follows each redirect without opening the destination in your browser. The table shows every address along the way and the final one. It is a safer way to see where an unfamiliar link leads before you click it.
Does the redirect checker follow JavaScript redirects?
No. It follows server redirects sent through HTTP status codes and the Location header, which is how most redirects work. Redirects made by JavaScript or by a meta refresh tag inside the page only happen in a browser, so they do not appear in this table.
What is the difference between 307 and 302?
Both are temporary redirects. A 307 guarantees the browser repeats the request with the same method, so a submitted form stays a form submission. With a 302, some browsers change it to a normal page request. The same difference exists between the permanent codes 308 and 301.