What it means
When we opened http:// on your site, it either answered the page over plain HTTP or redirected
somewhere that isn't HTTPS on your own site. Visitors who type your name without https://, follow an old
link or arrive from a bookmark stay on the unencrypted version. The detail shows where the plain HTTP entry
point ends.
Why it matters
On plain HTTP anyone on the network path, such as public Wi-Fi or a compromised router, can read pages, inject ads or scripts, and change download links. Browsers label such pages as not secure, and HSTS can't protect visitors until they have reached HTTPS at least once. A redirect closes the gap for everyone who arrives the old way.
How to fix it
- Make sure HTTPS works on every name first; the SSL check shows that.
- Add one permanent redirect (301 or 308) from every
http://address to the same path onhttps://. - Keep the path and query string, so deep links still land on the right page.
- Once the redirect works, add HSTS so browsers skip plain HTTP next time.
Nginx
In the port 80 server block: return 301 https://$host$request_uri;
Apache
RewriteEngine On then RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
Cloudflare
Turn on "Always Use HTTPS" under SSL/TLS, Edge Certificates.
Check it worked
Run the HTTP and security headers check again. The http:// entry points should show a 301 or
308 hop to https:// on your own site, and the finding should be gone.