Paste any URL and trace its redirect chain hop by hop — every status code, the final destination and how long it took.
Our server requests the URL and follows each redirect manually, so you see the whole chain instead of only the final page. Only public addresses can be checked; page content is never downloaded.
Check any web address and see exactly what happens when it is requested: every redirect hop with its status code, the final destination, how long the whole chain took, and the key response headers. Our server makes the request for you, so it also works for addresses your browser cannot open directly.
Checking http://asadwebs.com shows the classic pattern: a 301 redirect from the HTTP address to the HTTPS one, then a final 200 from https://asadwebs.com/. A shortened link typically shows one or two 301 or 302 hops before the final 200 at its destination.
The server sends a HEAD request (falling back to a minimal GET when a site refuses HEAD) and deliberately does not auto-follow redirects. Each 3xx response carries a Location header; the tool resolves it against the current URL, validates it, and requests it next — up to 10 hops. For every hop it records the URL, status code, elapsed time and the Server and Content-Type headers, using the PHP curl extension. To prevent abuse, every host is resolved first and the request is pinned to a validated public IP address; private, loopback and reserved addresses are rejected at every hop.
It shows every step between the address you entered and the final page. Long chains slow visitors down and waste crawl budget; each hop should be a deliberate move, and permanent moves should use a 301 rather than a temporary 302 left in place by accident.
Both send the visitor to a new URL. A 301 is permanent: browsers and search engines treat the new address as the canonical one. A 302 is temporary and keeps the original address canonical. Using 302 for a move that is actually permanent is a common, quiet SEO mistake.
Servers can respond differently by location, device, cookies or request type. This tool checks from our server with no cookies and no login — close to a first-time visitor or a crawler — but a site behind a bot wall may still answer it differently from your browser.
Only public addresses are fetched: URLs that resolve to private, loopback or internal network addresses are refused, and page content is never downloaded — only status lines and headers are read. Avoid checking URLs that contain private tokens, because the address you enter is necessarily sent to our server to perform the check.
The tool follows at most 10 hops and stops early if a redirect loop is detected, the next address is not a public URL, or a hop takes more than a few seconds. The results table shows exactly where the chain ended and the note under it explains why.