An address change can hide several server responses behind a single page load. Google Chrome's Network panel exposes those HTTP redirects so you can identify each destination and the response that ends the chain.
A server-side redirect returns a redirect status and a Location header identifying the next URL. Chrome normally follows it automatically, so the address bar alone cannot show how many hops occurred.
Network capture begins only while DevTools is open. Starting with the original URL matters because reloading a page after a redirect requests its final destination instead; your browser's sign-in state can also change the route you see.
Tool: HTTP Redirect Checker
Use only public, non-sensitive URLs with the remote checker, which does not share Chrome's signed-in session.
Steps to detect HTTP redirects using Google Chrome:
- Press Ctrl + Shift + I in Google Chrome to open DevTools.
On macOS, the shortcut is Command + Option + I.
- Select the Network tab in DevTools.

- Enable Keep log in the Network toolbar.
Older Chrome versions label this option Preserve log. It retains requests across page navigations. The recording button at the left is red while recording; if it is gray, click it before loading the URL.
- Load the original URL through Chrome's address bar.
If a cached redirect hides response details, enable Disable cache before loading the original URL again.
- Select the Doc filter to show document requests.
The filter hides images, scripts, and other resources. For a redirect affecting one of those resources, use All instead.
- Select the first document request with a redirect status.
Common redirect statuses are 301, 302, 303, 307, and 308. A 304 Not Modified response concerns caching and is not a redirect.
- Check Location under Headers → Response headers for the selected request.
Here,
/old-pagepoints to/moved-page. A relative Location value is resolved against the request URL; a full URL can point to a different host. - Follow the document requests identified by successive Location values.
The next request,
/moved-page, points to/destination. Chrome has already followed the redirects, so selecting their recorded rows does not navigate again. - Confirm the last request's Request URL and Status Code under Headers → General.
The chain here ends at
/destinationwith 200 OK, matching the address bar and loaded page. A final 4xx or 5xx response identifies a destination that failed; repeated hops or ERR_TOO_MANY_REDIRECTS indicate a redirect loop. If no redirect response appears, no HTTP redirect was captured; scripts or an HTML refresh can change the page without an HTTP redirect response.