A consistent HTTPS policy improves transport safety, yet it remains separate from the question of who controls an address claim.
Observe the first request safely
Determine whether HTTP receives a direct permanent redirect to the canonical HTTPS origin.
Long or cross-domain redirect chains should be recorded as separate evidence.
Read the HSTS policy
Record max-age, includeSubDomains and preload signals where present.
These settings describe browser upgrade behavior and do not authenticate page content.
Check hostname consistency
The redirected hostname, certificate and canonical should agree on one maintained origin.
Mixed www and non-www behavior can divide crawl signals and confuse reviewers.
Avoid relying on preload alone
Preload participation can strengthen upgrade behavior but may remain after other site changes.
Verify the current response rather than treating a historical list entry as proof.
Document transport separately
Publish an HTTPS-policy finding alongside, not inside, the identity conclusion.
This keeps technical quality from being overstated as a verified Mars Market address.