Where does this URL actually end up?

301 is a permanent redirect: it says this address has moved for good, and clients are free to remember it and skip the hop next time. It answered a HEAD request and sent the client to https://example-company.com/pricing. This is the http-to-https upgrade.

301 is a permanent redirect: it says this address has moved for good, and clients are free to remember it and skip the hop next time. It answered a HEAD request and sent the client to https://www.example-company.com/pricing.

302 is a temporary redirect: it says the page lives elsewhere for now, so clients keep asking the original address every time. It answered a HEAD request and sent the client to https://www.example-company.com/plans.

HTTP 200 — the destination answered normally to a HEAD request. This is where the chain ends.

3 redirects before the destination. Each one is a full round trip the visitor waits through, and chains this long are usually separate rules stacked on top of each other — an https upgrade, then a www change, then a path rewrite — where one rule pointing straight at the final address would do the same job in a single hop. The chain is not broken; it is longer than it needs to be.

The trace started at http and ended at https, so visitors who arrive on the unencrypted address are moved onto the encrypted one rather than being served over it. That is exactly what this hop is for.

The chain uses 301 and 302. Temporary statuses are the right choice when the destination really is provisional — maintenance pages, A/B splits, region routing — so this is only worth changing if the move is meant to be permanent.

The chain ends at https://www.example-company.com/plans with HTTP 200 — a page, served. However many hops it took, it arrives.