security.txt Checker
Validate a website’s security.txt against RFC 9116.
About the security.txt Checker
security.txt (RFC 9116) is a small text file at /.well-known/security.txt that tells security researchers how to report vulnerabilities: whom to contact, in which language, and under which policy.
The checker fetches the file, validates the required Contact and Expires fields, warns about expired or overly long-lived files, and checks Canonical, Policy, Encryption, Preferred-Languages and an optional OpenPGP signature.
How to use it
- Enter the domain.
- Run the check.
- Fix any missing or expired fields.
Frequently asked questions
Which fields does security.txt require?
Contact (an email address with mailto:, a URL or a phone number) and Expires (a date in ISO 8601 format, recommended less than a year ahead). All other fields are optional.
Where must the file be placed?
At https://<domain>/.well-known/security.txt, served over HTTPS as text/plain. A copy at /security.txt is allowed for compatibility but /.well-known/ takes precedence.
Should security.txt be signed?
Signing with OpenPGP is recommended so readers can verify that the contact details were not tampered with, but it is optional.