Browsers can be tricked onto an insecure connection to your site.
What an attacker could do: On shared or hostile Wi-Fi, an attacker intercepts a visitor's first plain-HTTP request and keeps them on an unencrypted connection, reading or rewriting the session before HTTPS ever engages.
Add a Strict-Transport-Security response header with a long max-age so browsers refuse HTTP for your domain. Confirm every subdomain is HTTPS-ready before adding includeSubDomains.
# nginx: serve on HTTPS responses only
add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;Also touches
Raw evidence from the scan
example.com responded to https:// without a Strict-Transport-Security header, so a browser's first request can still be made over plain HTTP.
Add the Strict-Transport-Security header at the edge for every HTTPS response.
probe: sample:missing-hsts