Free Redirect Checker

Redirect chains leak link equity and slow every crawl. Tracing them requires following cross-origin requests — blocked in browsers — so NToolHub's Redirect Checker hands you the genuine method: curl commands that print every hop with its status code, plus browser-based tracer links and a guide to reading chains.

ℹ️
Why no live result here? Tracing a redirect chain requires following cross-origin requests, which browsers block via CORS. Instead, this tool builds the exact commands and one-click lookup links you need — everything runs from your own terminal or trusted lookup services.
Private by design. This page performs no live network lookups and uploads nothing — it only generates commands and links that run on your own machine or on trusted lookup sites you open yourself.

How to Use the Redirect Checker

  1. Paste the URL whose redirect path you want to trace.
  2. Click Get Redirect Trace Commands.
  3. Run the curl command to see every hop with its status code.
  4. Aim for a single 301 straight to the final URL — no chains, no loops.

Features

Enter any URL for curl commands showing the full redirect chain (status codes + Location headers) and chain-with-timing variants, plus redirect-checker.org and wheregoes.com links and chain-reading guidance.

Benefits & Use Cases

You see every hop exactly as crawlers do — catching chains, loops and 302s-masquerading-as-permanent that in-browser tools can't reveal — with reusable commands for ongoing audits.

Tips

Keep chains to a single 301 hop, never chain redirects (A→B→C), use 301/308 for permanent moves, and audit redirects quarterly — they accumulate silently during redesigns.

Frequently Asked Questions

Why can't this trace redirects in the browser?

Following a redirect chain means requesting each hop cross-origin, which CORS blocks. Curl follows the real chain with no restrictions.

How many redirect hops are too many?

One is ideal; two is tolerable. Three-plus hops waste crawl budget and risk Google abandoning the chain — flatten them to direct 301s.

301 vs 302 — which should I use?

301 (or 308) for permanent moves — it passes link equity. 302 is temporary and doesn't. Most 'temporary' redirects people set are actually permanent.

What causes redirect loops?

A→B→A configurations, often from conflicting www/non-www or http/https rules. The curl chain output here makes loops obvious.

Related Tools

WWW Redirect Checker

Test all 4 www/non-www and http/https variants with copy-ready curl commands. Free WWW Redirect Checker — full canonicalization audit, no sign-up.

Open tool →

URL Status Checker

URL Status Checker helper: real curl status commands and a code reference guide. Verify 200s, 404s and 5xx honestly — free tool, no sign-up.

Open tool →

HTTP Header Checker

HTTP Header Checker helper: real curl commands plus SecurityHeaders.com scans. Honest header inspection walkthrough — free, no sign-up needed.

Open tool →

Canonical URL Generator

Generate canonical link tags and audit URL variants for duplicate-content issues. Free Canonical URL Generator from NToolHub — no sign-up needed.

Open tool →

DNS Lookup

DNS Lookup helper: copy-ready dig and nslookup commands plus one-click DNS links. Honest, free DNS research tool by NToolHub — no fake results.

Open tool →