Docs Security
HTTP redirects to HTTPS
Checks that http://yourdomain answers with a redirect to an https:// address, so visitors who type or click an old link end up on the secure site.
What it checks
We request http://yourdomain/ without following redirects and read the first answer.
It passes when the answer is a redirect (any 3xx status) and its Location header starts with https://. A relative Location header fails, because the check needs to see the https:// address in it.
- PassThe http:// homepage redirects straight to an https:// address.
- FailThe http:// homepage loads a page, redirects to another http:// address, or does not answer at all.
Why it matters
People type domains without https://, and old links, bookmarks and printed material often use http://. Without a redirect those visitors land on the insecure version of the site, or on an error.
How to fix it
Make the http:// version of every address answer with a permanent 301 redirect to the matching https:// address. Keep the path and query string, so deep links still land on the right page, and send it in one hop rather than through other addresses.
Platform notes
Turn on Always Use HTTPS under SSL/TLS, Edge Certificates.
On Nginx, give the port 80 server block a return 301 to the https:// version of the same host and URI. On Apache, use a Redirect or a rewrite rule in the port 80 virtual host or in .htaccess.
Many hosts have a force HTTPS switch in their control panel. Set the Site Address to https:// first, or the two settings can fight.
These platforms redirect http:// to https:// once the certificate is active. If this fails, check the domain connection and any setting that turns HTTPS off.
Vercel and Netlify redirect HTTP to HTTPS on their own for domains with a certificate.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.