HTTP not redirected to HTTPS
When a site answers on HTTP without redirecting to HTTPS, the initial request (and any form posted to it) can be read or tampered with on the network, and users can be kept on an insecure connection.
Why it matters
A network attacker can intercept or modify cleartext HTTP, including stripping the upgrade to HTTPS (SSL stripping).
Cookies and credentials sent over the first HTTP request are exposed before any redirect would happen.
How to check for it
- curl -sI http://yourdomain.com — expect a 301/308 to the https:// URL.
- Check for an HSTS response header (Strict-Transport-Security) on the HTTPS site.
How to fix it
- Redirect all HTTP to HTTPS at the server/CDN, then add HSTS (Strict-Transport-Security) so browsers use HTTPS automatically.
- Once stable, consider HSTS preloading for the domain.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- What does HSTS add on top of a redirect?
- HSTS tells the browser to go straight to HTTPS on future visits without an HTTP request at all, closing the SSL-stripping window.