Redirect Checker

About Redirect Checker

Paste one URL or a list (one per line, max 50) and click Follow redirects. We request each hop without auto-following, so you see URL, status, and Location. Hops stop at resolved, a repeated URL (loop), or 10 hops (cap). 301 and 308 are Permanent. 302 and 307 are Temporary. Other 3xx is Other. The last non-redirect is Final.

A loop or a 10-hop stop is critical. Three or more hops is a warning. A 302 or 307 is a notice only when the hop looks like a permanent move (http to https, or apex to www, same path). Meta refresh and JavaScript redirects are not executed.

When to use it

Use it after you flip HTTPS, add or drop www, or change a CDN page rule, when you need the hop list rather than only the final address. That is also the check before a domain cutover: does the old host still 302, and does it land where the canonical says?

Use the 50-line list when a spreadsheet of legacy paths has to be proven in one run. It is not a crawl and it does not discover links.

How to use Redirect Checker

1. 1Paste one URL or a list. One URL per line. The first 50 lines are used.
2. 2Click Follow redirects. Each hop is recorded instead of jumping to the final URL.
3. 3Read the chain. Status plus Location. Loop or cap is called out on the chip.
4. 4Shorten long chains. Point the first URL at the final destination when you control the server.

Hops and stop reasons

Counts at the top are URLs, Loops, Long chain, Temporary, Direct, and Pass. Direct means the first response was already the final URL. Shorten chains by pointing the first URL at the final destination when you can.

Private hosts are blocked. Hashes are stripped before compare so #section does not look like a new hop. Location is resolved against the current URL when it is relative.

How to read the results

Each chain has its own table: Step, Status, Type, URL, and Next. Type is Permanent (301, 308), Temporary (302, 307), Other (remaining 3xx), or Final. Next is the Location, or Final when the hop is not a redirect. Stop reasons are resolved, loop, or cap (already 10 hops).

Counts: URLs is how many start addresses you pasted. Loops and Long chain (three or more hops, then resolved) are the rows to fix first. Temporary counts 302 and 307 hops. Direct is hop count 0: http://example.com answered 200 with no Location. http://github.com was one 301 to HTTPS, labeled Resolves in 1 hop.

Why this matters

Each extra 301 is another request a bot must finish before it can read the document. Three hops in a row cost more than one hop to the same destination: more timeouts, more chances a client stops, and a longer wait before title and body are seen.

A 302 on http to https, or apex to www with the same path, tells engines the move is temporary, so they may keep the first URL as the one to show. That is why those 302s are a notice here and 301 or 308 are Permanent.

Limits and privacy

Loopback and reserved IPs are rejected before hop 1. A list is clipped to the first 50 lines. About 20 runs per minute on your network. Hashes are stripped so a fragment cannot look like a new hop. There is no login.

Common mistakes

Testing www when the live host is the apex (or the reverse). You get Direct or a different chain than users hit. Type the URL the canonical names.

Treating a single 301 as a fault. Resolves in 1 hop is a pass. Long chain is three or more hops after the start URL.

Expecting a meta refresh or a window.location hop to appear. Only HTTP 3xx with Location is followed. Those other moves look like Final on the first document.