Website Tools

Redirect Checker

Follow a URL through every redirect to see each hop, its status code and the final page.

Not sure what to enter? Try an example: http://github.com

Free & instant No signup How to use FAQ

Enter a URL to trace each redirect step by step, with the status code of every hop and the address the visitor finally lands on.

What does a redirect checker do?

A redirect checker requests a URL and follows each redirect the server sends - up to 5 hops here - listing every step with its HTTP status code and destination until it reaches the final page. It shows whether http:// goes to https://, whether www and non-www point to one version, and whether a chain has more hops than necessary.

Common redirect status codes
Code	Meaning	Use it for
301	Moved Permanently	Permanent URL changes, HTTP to HTTPS, domain moves
302	Found (temporary)	Short-term redirects where the original URL will return
307	Temporary Redirect	Temporary redirects that must keep the request method (e.g. POST)
308	Permanent Redirect	Permanent redirects that must keep the request method

How to check a redirect chain

Enter the domain or URL you want to test in the box above.
Click Check Redirects.
Read each hop in order and note its status code and where it points.
Aim for a single permanent (301 or 308) redirect from any old or alternate URL straight to the final page.
If you see a chain or a loop, update the first redirect to point directly at the final destination.

Related checks

Once you know the final URL, confirm that page actually loads with the Website Status Checker.
To test only whether http:// is forced to https://, use the HTTPS Redirect Checker.
To see which server the final domain points to, run an IP Address Lookup.

Redirects come in different types that matter for SEO and browser caching: a 301 is permanent (search engines transfer the original page's ranking signals to the new URL), while a 302 or 307 is temporary (the original URL is expected to work again later, so ranking signals generally stay put). A long redirect chain (more than 2-3 hops) can slow down page load and is worth cleaning up even if the final destination is correct. JustChecker monitors your websites around the clock and alerts you the instant something changes.

Frequently Asked Questions

Aim for one. Each extra hop adds a round trip for visitors and search engines; http to https to www to a new page should be collapsed into a single redirect straight to the final URL.

Two or more URLs redirecting to each other forever, so the page never loads and browsers show "too many redirects". It is often caused by conflicting HTTPS or www rules in the server and a CDN.

A single 301 passes almost all of it. Long chains and temporary 302s used for permanent moves are what cause problems.

Share this tool:

Need a website for your business? Only $599