Skip to main content
HighHeadersOWASP A02:2021CWE-319

How to fix: Site served over plain HTTP (no TLS at all)

The scanned URL uses the plain http:// scheme, meaning the connection is not encrypted at all. This check does not negotiate a TLS handshake or detect specific deprecated TLS versions (TLS 1.0/1.1) on an HTTPS endpoint; it only flags a bare HTTP URL.

Why it matters

Traffic to a plain HTTP URL is unencrypted end-to-end, so any network observer can read or modify requests and responses, including credentials, session tokens, and page content, without needing to defeat any TLS protocol at all.

Serve the site exclusively over HTTPS. If TLS 1.0/1.1 support on an HTTPS endpoint is a separate concern, that requires a dedicated TLS-handshake probe rather than a URL scheme check.

How to fix it

  1. 1Serve the site over HTTPS and redirect all HTTP requests to HTTPS.
  2. 2Obtain a TLS certificate (e.g. via Let's Encrypt) if one is not already configured.
  3. 3Add the Strict-Transport-Security header once HTTPS is confirmed working.

Code examples

Nginx: redirect HTTP to HTTPS

nginx
server {
  listen 80;
  server_name example.com;
  return 301 https://$host$request_uri;
}

References

Detected automatically by VulnRadar. The check id is deprecated-tls, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Site served over plain HTTP (no TLS at all)?
VulnRadar rates this high severity in the headers 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 deprecated-tls, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Site served over plain HTTP (no TLS at all) 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.

Propose a checkHow a check is built

Scan your own site for site served over plain http (no tls at all)

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Site served over plain HTTP (no TLS at all) fix | VulnRadar