Redirects are invisible when they work, which is exactly why a chain of four of them can sit there for years.
Every hop slows the page down and can dilute where search engines send the ranking. This shows you each one.
What It Shows
Every hop, with its status code, how long it took, and its full headers. It follows up to 10 redirects and stops if it detects a loop.
The redirect mistakes: temporary redirects (302 and 307) where a permanent one (301 or 308) belongs, chains longer than two hops, and redirects from https down to http.
The headers on the final page: security headers like HSTS and the Content-Security-Policy, cookie flags, caching, and compression.
You can also visit as Safari on an iPhone, since some sites redirect phones differently. It sends a regular GET request and stops reading after the headers.
To see a page the way Googlebot does, use URL Inspection in Google Search Console. Many sites only treat a request as Googlebot when it comes from Google's own addresses, so no outside tool can show you that.
Frequently Asked Questions
What's the difference between a 301 and a 302?
A 301 says the page moved for good, so search engines move its ranking to the new address. A 302 says the move is temporary, so they keep the old address. For a page that moved for good, use a 301 (or a 308, which also keeps the request method).
How many redirects is too many?
One is normal, like http to https, or adding a trailing slash. Two is fine. Past that, link straight to the final address and update the first redirect to point there.