HTTP to HTTPS
Whether the HTTP request redirects to HTTPS.
Check HTTP to HTTPS redirects, follow every hop and compare www variants.
Server redirects for the URL you submit, with the www variants when they apply.
Whether the HTTP request redirects to HTTPS.
The URL where the chain stops.
Permanent 301 and 308, or temporary 302, 303 and 307.
How www and non-www hosts finish, when that comparison applies.
A later hop that requests an earlier URL.
A Location that sends HTTPS to HTTP, including a middle hop.
Use the chain and the variant table to see where this URL goes.
The check covers the submitted URL and the selected variants, not every page on the site.
An HTTP response can send clients to the HTTPS URL. This check follows that server redirect. It does not treat a browser HSTS upgrade as a redirect it observed.
A loop requests an earlier URL again, so the chain does not settle on one response. The report names that separately from a successful HTTPS destination.
Both are permanent. 308 preserves the request method. This check sends GET, so it does not show whether a POST would be preserved. 302, 303 and 307 are temporary.
That is a choice for the site. When the host is an apex or www name, this check compares both and warns if the paths or queries differ. A different path is shown for review. It is not automatically marked wrong.