Kiểm tra trạng thái HTTP & Truyền chuỗi chuyển hướng miễn phí

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.