Skip to main content

Redirect Checker: Trace Every Hop and Status Code

Enter any URL to see its full redirect path: the HTTP status code, response time and server for each hop, plus notes on chains, loops and temporary redirects that can cost you search traffic.

Free · no sign-up · checked from our server, not your browser

How to use the Redirect checker

  1. Enter a URL

    Paste an old page address, a domain without https, or a campaign link you want to audit.

  2. Run the check

    We request it from our server with redirects turned off, then follow each Location header ourselves so every hop is recorded.

  3. Fix what you find

    Point old URLs straight at the final page, replace 302s that should be permanent, and remove loops.

When to use it

Site migrations

Confirm that old URLs answer with a single 301 to the matching new page, not a chain through the homepage.

HTTP to HTTPS and www rules

Check that http://, www and trailing-slash variants reach the canonical address in one step.

Affiliate and campaign links

See every tracking domain a link passes through and how long each one takes to answer.

Debugging loops

Find the exact hop where two rules send visitors back and forth.

Reading redirect status codes

301 (Moved Permanently) and 308 (Permanent Redirect) tell browsers and search engines the move is permanent; ranking signals are consolidated on the new URL. 308 also keeps the request method, which matters for form posts and APIs.

302 (Found) and 307 (Temporary Redirect) say the original address will come back. Search engines may keep the old URL indexed. Use them for short-lived campaigns, A/B tests or maintenance, not for permanent moves. A 303 sends the visitor to a different resource after a form submission.

Each extra hop adds a network round trip, often 100–300 ms on mobile, and Google follows only a limited number of hops per crawl. Keep internal redirects to a single step and update links to point at the final address. Meta refresh redirects are slower and less reliable than HTTP redirects; use a 301 instead where you control the server.

Frequently asked questions

How many redirects does the checker follow?

Up to ten. It stops earlier if it sees the same address twice (a loop) or if a request fails, and reports where it stopped.

Does it follow JavaScript redirects?

No. It follows HTTP redirects (301, 302, 303, 307, 308) and HTML meta refresh tags with a delay of ten seconds or less. Redirects done in JavaScript need a real browser to detect.

Why do I see a different result in my browser?

Servers can redirect differently by country, language, device, cookies or user agent. The checker sends a bot user agent with no cookies from our server's location. Your browser may also have cached an earlier 301.

Can I check URLs on a private network or localhost?

No. For security the checker only contacts public addresses on ports 80 and 443. Private, loopback and reserved IP ranges are blocked, including domains that resolve to them.

Is there a limit?

Each visitor can run 20 checks per minute. There is no account or sign-up.