security.txt generator
Create a valid security.txt file so security researchers know how to report a vulnerability in your website - and where to send it.
Your security.txt
Save it as /.well-known/security.txt on your site, served over HTTPS as text/plain. Set a reminder to update it before it expires.
What is security.txt?
RFC 9116 defines a small text file that tells people who find a security problem in your website how to contact you. Without it, a researcher may not find the right address and the report can end up in a general inbox, on social media, or nowhere at all.
Where it goes
Publish it at https://your-domain/.well-known/security.txt (a copy at /security.txt is optional). It must be served over HTTPS with the text/plain content type.
Required fields
- Contact - at least one way to reach you. List the preferred one first.
- Expires - when the file should no longer be trusted, so stale contacts are not used forever.
Sign it (optional)
RFC 9116 recommends signing the file with an OpenPGP cleartext signature so readers can check it has not been tampered with. This tool does not sign anything: sign the downloaded file yourself, for example with gpg --clearsign security.txt, and include a Canonical URL when you do.
Check your site's security.txt with a free Webforta scan
A Webforta scan checks whether your security.txt is published, valid and not expired, alongside HTTPS, security headers and exposed files on websites you verify.