Free tool, no account required

Free HTTP Status & Redirect Chain Tracer

Trace HTTP status codes (200, 301, 302, 404, 500) and redirect chains for multiple URLs at once. Detect infinite redirect loops and hop latency.

Also known as: HTTP status code checker, 301/302, redirect chain

Evidence shown with sourceNo account requiredNo invented metrics

Run a real check above

Submit a public URL, domain, or keyword. Novaverb will show only the evidence this tool can actually retrieve or measure.

Evidence model

Know what the result proves

This check proves the exact redirect chain a URL produces: every hop's status code, scheme, host, path, Location header and latency, up to the final non-redirect response. Because each hop is requested without auto-following, the chain reported is the chain that exists, including loops and the extra hops that a browser hides from you.

1. Source

Live server-side HTTP requests, one hop at a time. The result identifies where its evidence came from.

2. Boundary

The trace follows server-side HTTP redirects (up to 10 hops per URL) with the selected user agent. Client-side JavaScript redirects and browser-only navigation are outside this check.

3. Next action

Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.

How to read a redirect chain

This tool follows each URL server-side, one hop at a time, and shows the real HTTP status of every step - not just the final page. A clean setup redirects once (301) straight to a 200 OK. Extra hops slow crawlers and users and dilute link equity.

What each status means

301 / 308 - Permanent redirect. Search engines pass ranking signals and update the index to the target.
302 / 307 - Temporary redirect. Use only when the move is genuinely temporary; the original URL stays indexed.
200 - OK. The final destination served content successfully.
4xx / 5xx - The chain ended in a client or server error - a broken redirect target that wastes crawl budget.

Chains and loops to fix

Two or more redirects in a row (a chain) should be collapsed to a single hop pointing at the final URL. Mixed http→https and www→non-www hops are the most common cause - enable the Canonical domain check to see whether every variant funnels to one canonical URL.

Get the right answer

What to submit - and what to avoid

Submit the URL you actually publish or link to, not the destination you expect, since the whole point is what happens in between. The user agent can be selected, which matters because some servers redirect crawlers differently from browsers. A chain longer than ten hops is stopped and reported as a chain rather than followed indefinitely.

Use it like this

http://yourdomain.comThe http and non-www forms are the most revealing - they expose the http→https and www hops. Any form is accepted.

one URL per line (up to 20)Paste a whole list - each URL is traced independently and shown as its own expandable row. Turn on the canonical check to also test the http/https and www variants of each host.

Avoid this

how to fix a redirectThat is a search phrase, not an address. This tool checks URLs; use the Keyword tool for search terms.

Reading '0 redirects' as a failureZero redirects is a healthy result - it confirms the URL is already the final destination (200 OK, no hop).

Public methodology

Exactly how this result is produced

Each URL is requested server-side with the selected user agent and without auto-following, so the exact status code, response headers and Location of every hop are read directly. The chain is walked hop by hop up to ten, each hop is timed, chains of two or more redirects and loops are detected, and the final destination is reported.

We request each URL server-side with your selected user agent, WITHOUT auto-following, and read the exact status code, response headers and Location of every hop.
We follow the chain hop by hop (up to 10) until a non-redirect response, timing each hop and detecting chains (2+ redirects) and loops.
We report every hop's status, scheme, host, path and latency, plus the final destination - per HTTP semantics, nothing invented.

Built on public standards

The international standards this check applies

RFC 9110 defines HTTP semantics, including what each 3xx status means and how the Location header is resolved. Distinguishing a 301 from a 302 and from a 307 matters because the specification assigns them different permanence and different method-preservation rules, and this check reports the code returned rather than the intent behind it.

IETFRFC 9110

HTTP Redirection (3xx)

Traces each 3xx hop and its Location header per HTTP semantics.

Read the specification

We list a standard only where this tool genuinely reads or measures against it. Where a signal is outside a live check, the result says so instead of implying coverage.

Common questions

HTTP Status & Redirect Checker FAQ

What does the Redirect Checker check?

It traces a URL's full server-side HTTP redirect chain, showing every hop, each status code, the final destination URL, and the total number of redirects so you can see the complete path a request takes.

What is an HTTP redirect?

A redirect is a server response, using a 3xx status and a Location header, that sends a request from one URL to another. Browsers and crawlers follow it to reach the final destination.

What's the difference between a 301 and 302 redirect?

A 301 signals a permanent move and passes ranking signals to the new URL; a 302 signals a temporary move and is not meant to transfer them. Use 301 for permanent URL changes.

What is a redirect chain and why fix it?

A redirect chain is multiple hops before reaching the final URL, like A to B to C. Each hop adds latency and can dilute signals, so collapse chains to a single direct redirect where possible.

How many redirects are too many?

Keep it to one hop when you can. Long chains slow page loads and risk crawlers giving up. The tool counts total redirects so you can spot and shorten excessive chains.

Why do redirects matter for SEO?

Redirects preserve link value and user access when URLs change. A correct 301 forwards ranking signals to the new address; broken or looping redirects waste crawl budget and can strand pages searchers cannot reach.

What is a redirect loop?

A redirect loop is when URLs point back to each other endlessly, so no final page is ever reached. The chain trace reveals repeating hops so you can break the cycle.

What is a 308 redirect?

A 308 is a permanent redirect that, unlike a 301, requires the request method to stay unchanged. Like a 301 it indicates a permanent move, so signals should flow to the new URL.

Does this tool follow JavaScript redirects?

No. It follows server-side HTTP redirects using status codes and Location headers. Client-side JavaScript redirects and browser-only navigation are out of scope, so those hops will not appear in the traced chain.

What is the Location header?

The Location header accompanies a 3xx response and names the URL to go to next. The checker reads it at each hop to build the ordered chain up to the final destination.

More free checks