What it means
We could only read your security.txt over plain HTTP. RFC 9116 requires the file to be served over HTTPS, so readers know it really comes from your site.
Why it matters
Over plain HTTP anyone on the network path can change the file, for example to replace your security contact with their own address and collect vulnerability reports about your site. Tools that follow the standard ignore a security.txt that isn't served over HTTPS.
How to fix it
- Make sure your site works over HTTPS; the SSL check shows whether the certificate is valid.
- Serve the file at
https://example.com/.well-known/security.txt. - Redirect plain HTTP to HTTPS for the whole site, the file included.
- If you use a CDN, check that it doesn't serve a cached plain HTTP copy.
Check it worked
Run the standard files check again. security.txt should be read over HTTPS, and the finding should be gone.