How to fix: Site Served Over Unencrypted HTTP
The site is accessible over plain HTTP without TLS encryption. All traffic including credentials, session tokens, and user data is transmitted in cleartext.
Why it matters
Any on-path attacker can passively read every request and response, inject content into pages, steal session cookies, and capture credentials submitted in forms.
HTTP transmits everything in cleartext. On any shared network (coffee shop Wi-Fi, corporate proxy, ISP), passive sniffing requires no special privileges. Active attackers can additionally inject malicious scripts into responses.
How to fix it
- 1Obtain and install a TLS certificate (Let's Encrypt is free).
- 2Configure HTTPS and redirect all HTTP traffic to HTTPS.
- 3Enable HSTS to prevent future downgrades.
Code examples
Nginx redirect
server {
listen 80;
server_name example.com;
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
ssl_certificate /etc/ssl/certs/example.com.pem;
ssl_certificate_key /etc/ssl/private/example.com.key;
}References
Detected automatically by VulnRadar. The check id is unencrypted-connection, stable across every scan so you can filter or diff on it.
More ssl checks
- HighSecure Cookie Set on HTTP Endpoint
- InfoExpect-CT Header Not Present
- LowHTTPS Served on Non-Standard Port
- InfoX-HTTP-Method-Override / X-Forwarded-Method Header in Response
- InfoHSTS Present on HTTP Response (SSL-Strip Indicator)
- MediumMixed-Protocol Content (HTTPS Page Loading HTTP Resources)
- LowHSTS declared in a meta tag, where browsers ignore it
- MediumAlt-Svc advertises cleartext HTTP/2 (h2c)
Questions
- How severe is Site Served Over Unencrypted HTTP?
- VulnRadar rates this critical severity in the ssl category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id unencrypted-connection, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Site Served Over Unencrypted HTTP map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.