Free · live registry data · no login

HTTP to HTTPS Redirect Checker

Does every variant of your domain land on HTTPS?

How it works

HTTP to HTTPS redirect checker for every variant of your domain

Having a certificate is not the same as forcing HTTPS. We request http://yourdomain, http://www.yourdomain and both https variants from our server, follow every redirect and report where each one lands, with status codes and timing. You find out whether plain-HTTP visitors are upgraded, whether www and non-www agree on one canonical host, whether the hop is a permanent 301, and whether HSTS is set so browsers skip the insecure request next time.

Results appear here after you click Check redirects.

How this works

1
Request four variants
Our server fetches http:// and https:// for both the bare domain and www, in parallel.
2
Follow every redirect
Each response is followed up to 8 hops and the status codes, final URL and timing are recorded.
3
Judge the result
We check that HTTP lands on HTTPS with a 301, that all variants agree on one host, and that HSTS is present.

Frequently asked questions

Why do I need a redirect if I already have SSL?: A certificate only secures connections that arrive over HTTPS. People who type your domain or follow old http:// links will still get the insecure version unless the server redirects them. The redirect is what makes HTTPS the default.
Should I use 301 or 302 for the HTTPS redirect?: Use 301 (or 308). It tells browsers and search engines the move is permanent so they cache it and pass ranking signals to the HTTPS URL. A 302 is treated as temporary and the insecure URL keeps being requested.
What is HSTS and should I enable it?: HTTP Strict Transport Security is a response header that tells browsers to use HTTPS only for your domain for a set period. It removes the insecure first request on repeat visits and defeats downgrade attacks. Enable it once you are sure every subdomain works on HTTPS.
www or non-www: which should be canonical?: Either works; what matters is choosing one and redirecting the other with a 301. Non-www is shorter and common for new brands; www is slightly easier at the DNS level because it can be a CNAME. See our guide on www vs non-www.
I use Cloudflare. How do I force HTTPS?: Turn on 'Always Use HTTPS' under SSL/TLS → Edge Certificates, set the SSL mode to Full (strict), and enable HSTS in the same panel. Cloudflare then issues the 301 at the edge before traffic reaches your origin.

Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.