Security fix guide
security.txt File Missing
No /.well-known/security.txt file found. This file helps security researchers report vulnerabilities responsibly.
Issue ID: SEC-SECURITY-TXT-001
Severity: advisory
Impact: Low
Effort: S
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
No /.well-known/security.txt file found. This file helps security researchers report vulnerabilities responsibly.
Why it matters
No /.well-known/security.txt file found. This file helps security researchers report vulnerabilities responsibly. This affects browser trust signals and whether visitors feel safe submitting contact details.
How we detect it
- FreeSiteAudit flags this issue when the rule for SEC-SECURITY-TXT-001 fails and the page evidence points to Http headers.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Create a /.well-known/security.txt file following the RFC 9116 standard
- 2Include Contact, Expires, and optionally Encryption and Policy fields
How to re-check it
- Navigate to /.well-known/security.txt and confirm it exists with valid fields
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.