TontonTools

Redirect Checker

Check any URL's redirect chain — every hop, status code and final destination.

100% Free No signup Privacy-friendly Website Management
Updated Sep 2026

Share X / Twitter Facebook LinkedIn WhatsApp

How to use Redirect Checker

  1. Paste the URL to check — an old address you've redirected, a shortened link, or any page.
  2. Run the check — the full chain appears: every hop with its status code, in order.
  3. Read the verdict: ideally one 301 hop to the final URL. Chains of 3+ hops or any 302 in a permanent move need fixing.
  4. Fix at the source — update the redirect to point directly at the final destination, then re-check.

What is Redirect Checker?

A redirect checker requests a URL and traces where it actually leads: every intermediate hop, the status code of each (301 permanent, 302 temporary, 307/308), and the final destination page. What looks like one address in the browser is often a chain — http → https → www → trailing slash → final URL — and only a checker shows the whole path.

Chains matter for SEO and speed: each extra hop adds latency, Google reportedly follows long chains reluctantly (guidance says keep them under 3), and a wrong status code — a 302 where a 301 belongs — quietly stops ranking signals from transferring after a site move.

About the Redirect Checker

Paste any URL and see the complete redirect chain: each URL in sequence, its exact status code, and where visitors finally land.

The checks worth running: after adding .htaccess redirects, confirm the old URL 301s (not 302s) and reaches the right destination in one hop; after a domain or HTTPS migration, spot-check key pages for chains stacking up (http://old.com → https://old.com → https://new.com → https://www.new.com is three hops that should be one); before buying links or auditing a site, reveal where shortened or affiliate URLs really go; and diagnose "too many redirects" browser errors by seeing exactly where the loop closes.

Every hop shows its code, so mixed chains (a 301 followed by a 302) — a classic migration bug — are visible at a glance.

Frequently Asked Questions

Paste the URL here — each hop shows its exact status code. The difference matters: 301 transfers SEO signals to the new URL; 302 tells Google the move is temporary and keeps the old URL indexed.
One is ideal; Google's guidance suggests keeping chains under 3 (it may stop following around 5). Each hop adds ~100–300 ms of latency too. Point old URLs directly at the final destination rather than daisy-chaining.
A loop — the destination redirects back into the chain. Common causes: conflicting rules (plugin + .htaccess both forcing HTTPS), or a CDN/proxy like Cloudflare set to Flexible SSL while the server also redirects to HTTPS. The chain view shows where it circles.
A single clean 301 passes essentially all ranking signals. Losses creep in through long chains, mixed 302s, and redirecting everything to the homepage instead of equivalent pages — Google treats those irrelevant redirects as soft 404s.
Redirects can vary by device, country, language or login state (mobile sites, geo-targeting, A/B tests). The checker shows the neutral server response — differences from your browser usually mean conditional redirect logic.

We use cookies for analytics and to keep the tools free via ads. See our Privacy Policy.