Verify your HTTP to HTTPS redirect is set up correctly. Automatically tests all four URL variants (http/https with and without www), checks redirect chain length, confirms HSTS is present, and flags any multi-hop redirect that hurts SEO.
Automatically tests all 4 URL variants: http://, https://, http://www. and https://www.
Enter your domain name or any page URL. The tool automatically tests all four canonical variants: http://, https://, http://www. and https://www. — so you can see exactly how each one behaves.
Each variant shows its status code, where it redirects to, how many hops the redirect takes, and whether the final HTTPS response includes an HSTS header. Green means correctly configured, amber means works but could be improved, red means misconfigured.
Best practice is: all http:// variants redirect to https:// in a single hop (301), and the final HTTPS response includes Strict-Transport-Security. Multi-hop redirects and missing HSTS are common issues that hurt both security and page speed.
Google has used HTTPS as a ranking signal since 2014. Beyond rankings, every redirect hop adds latency. If your site takes two or three hops to get from http://example.com to https://www.example.com, that adds 200-600ms to your page load time before the first byte of content is served. Google recommends a single 301 redirect.
HSTS (HTTP Strict Transport Security) tells browsers to always use HTTPS for your domain — even if a user types http:// — without making an extra redirect request. Once a browser has seen your HSTS header, it bypasses the HTTP redirect entirely and goes straight to HTTPS. This improves both security and speed.
A 301 is a permanent redirect — it passes ranking signals (PageRank) to the destination and tells search engines to update their index. A 302 is temporary — search engines keep both URLs indexed and do not pass full ranking signals. HTTP to HTTPS redirects should always be 301.
More than one hop between http:// and your final HTTPS canonical URL is wasteful. Google and other crawlers may stop following chains longer than 5 hops, and each hop adds network latency. The ideal setup is: http://example.com → 301 → https://example.com (one hop, done).
If both www.example.com and example.com respond with 200 (not redirecting to each other), search engines see them as two different websites. You must pick one canonical version and redirect the other to it. Either is fine — the important thing is consistency. This checker verifies both redirect correctly.
Mixed content — your page loads over HTTPS but references HTTP resources (images, scripts, stylesheets). Browsers block or warn about mixed content. Fix by updating all internal links and asset URLs to use HTTPS or protocol-relative URLs. This checker tests the redirect behaviour, not mixed content scanning.
