How this check works
Separate HTTP and HTTPS requests start at the domain’s root. We follow standard HTTP redirect responses within the configured limit and show successful traces in the technical details. Review unexpected final hosts, downgrade redirects and unnecessary intermediate hops with your hosting provider.
Keep the route to your page short
Every redirect adds another request. Aim for a direct permanent redirect from insecure or alternate entry points to the intended HTTPS page, while preserving meaningful paths on your own site.
A bounded, public-only trace
The scanner follows at most five redirects and checks every destination for unsafe addresses. It does not execute JavaScript redirects or HTML meta refresh instructions.
Common questions
Why does a redirect trace stop early?
It may hit a redirect loop, the hop limit, a timeout or an unsafe destination. The scanner never follows redirects into private networks.
Do you test a URL's path?
This domain tool normalizes input to the hostname and begins at the root page. It is not a general-purpose URL fetcher.