Website Tools

Redirect Checker

Check whether a website redirects and where it ends up.

Enter a URL below to trace its complete redirect chain - see every hop from the URL you entered to wherever it actually ends up, including the HTTP status code at each step.

More Website Tools

View all 19

HTTP Headers Checker Website Response Time Checker HTTP Status Checker Robots.txt Checker IP Address Lookup Sitemap Checker Website Status Checker Favicon Checker

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.

What Is the Redirect Checker?

It follows a URL through every redirect until it reaches the final page, and shows each step with its status code. It also detects redirect loops.

When to Use It

After moving pages or switching to HTTPS or www.
To find long redirect chains that slow pages down and waste search engine crawl budget.
When a browser reports "too many redirects".

How to Use It

Enter the starting URL, for example http://example.com.
Follow the chain to the final URL.

Understanding the Result

Ideally any old URL reaches its final page in one 301 redirect. Chains such as http → https → www → final page should be shortened to a single hop. Use 301/308 for permanent moves so search engines transfer rankings to the new URL.

Limitations

Only server-side redirects are followed (a maximum of five hops); JavaScript or meta-refresh redirects are not. Check the HTTPS redirect specifically with the HTTPS Redirect Checker.

Frequently Asked Questions

A 301 (Moved Permanently) tells browsers and search engines the redirect is permanent - search engines transfer the old page's SEO value to the new URL. A 302 (Found) or 307 (Temporary Redirect) signals a temporary change, so the original URL is expected to become the canonical one again and generally keeps its own ranking signals.

This often builds up over time - an HTTP-to-HTTPS redirect, then a non-www-to-www (or reverse) redirect, then an old-URL-to-new-URL redirect, each added separately, can chain together into 3-4 hops for a single request. Each hop adds latency, so consolidating them into a single, direct redirect is a common performance fix.

This tool always makes a fresh, live request, so it will show your current, real redirect behavior at the moment you check. If you're still seeing the old chain, double check the change actually deployed (and that any server or CDN-level caching has been cleared), then run the check again.

A single, correctly-configured 301 redirect passes ranking signals with minimal loss. However, long chains, redirect loops, or mixing 301s and 302s inconsistently can dilute signal, slow crawling, and in the worst cases (a genuine loop) prevent a page from being indexed at all.