Web

HTTP to HTTPS Redirection Test

HTTPS Redirect

Confirm every entry point ends on one HTTPS URL

Requests all four entry points — http:// and https:// × root and www — and compares the final URL of each.
Test path (optional — checks the path survives the redirect)
Try:
github.com
wikipedia.org
cloudflare.com

Tool features

Comprehensive redirection analysis with security insights and detailed reporting
4 checks

Four Entry Points

Tests http/https × root/www and checks they converge on one HTTPS URL

Chain Analysis

Shows every redirect hop with status codes and what each hop changed

Loop & Path Detection

Flags redirect loops and redirects that discard the requested path

HSTS Policy

Reads Strict-Transport-Security so the first request is protected too

What is HTTP to HTTPS redirection & how it works

How sites move insecure requests onto HTTPS

When someone types your address without a scheme, or follows an old http:// link, their first request travels unencrypted. An HTTP→HTTPS redirect immediately sends them to the secure version, so the plaintext window is as small as possible and every visitor ends up on an encrypted connection.

Best practice is a single 301 redirect from http:// straight to the final https:// URL, with no extra hops or loops — then an HSTS header so browsers skip HTTP entirely next time. This test follows all four entry points, checks they converge on one HTTPS URL, and flags loops or missing enforcement.

301 redirect
A permanent redirect that sends HTTP requests to the HTTPS URL.
HSTS
A header telling browsers to use HTTPS automatically on future visits.
Redirect loop
A broken chain where URLs redirect endlessly and never resolve.

How to use this tool

Check a site's HTTPS redirect in four steps
1
Enter a domain
Type a domain, e.g. example.com — all four entry points (http/https × root/www) are tested.
2
Add a test path
Optionally give a path such as /pricing to confirm deep links survive the redirect.
3
Review the result
See whether every variant converges on one HTTPS URL, the upgrade status code, chain length, and the HSTS policy.
4
Fix and harden
Apply the generated nginx/Apache config so one 301 upgrades every entry point, then enable HSTS and re-test.

Related tools

Keep debugging with tools from the same suite
4 tools
Website Redirect Checker
Check website redirects and status codes for any URL. Detect multi-level redirects and view final destination
WWW vs Non-WWW Redirection Test
Test domain canonicalization between www and non-www, detect redirect chains and loops, and identify the preferred version
HSTS Checker
Check HTTP Strict Transport Security (HSTS) header configuration and preload status
SSL Checker
Comprehensive SSL certificate analysis including validity, expiration, chain verification, TLS versions, and security assessment

Frequently asked questions

Common questions about HTTP to HTTPS redirection
5 Q&A

Redirecting HTTP to HTTPS ensures visitors who arrive over an insecure connection are immediately moved to the encrypted version, protecting their data and satisfying browser and SEO expectations for secure sites.

Use a 301 (Moved Permanently). It signals the HTTPS URL is the canonical one and passes SEO ranking signals, unlike a 302 temporary redirect.

HSTS (HTTP Strict Transport Security) is a response header that tells browsers to always use HTTPS for your domain, so after the first visit they skip the HTTP request entirely — closing the small window a redirect alone leaves open.

A loop occurs when URLs redirect to each other without ever reaching a final page — often a misconfigured HTTPS or www rule. This test detects loops so you can fix the offending redirect.

Yes. Each extra hop adds latency. Ideally http:// redirects in one step to the final https:// canonical URL, rather than chaining through several intermediate redirects.