Why it matters
Security researchers who find a problem on your site look for /.well-known/security.txt to learn who to tell. Without it, reports go to a generic inbox or nowhere.
RFC 9116 is short but strict: Contact and Expires are required, Expires must be a full timestamp and should be less than a year away, and links should be https. This builder writes the file and flags each of those.
How to use it
- Type or paste your input; the example shows the format.
- Press Build security.txt. Results also update as you type.
- Read the summary line, then the table, notes or output below it.
- Copy or download what you need. Nothing leaves this page.
FAQ
Do I need to sign security.txt?
No. RFC 9116 allows an OpenPGP cleartext signature, but it is optional. Most sites publish it unsigned over HTTPS.
Is my input uploaded?
No. The tool runs in your browser and nothing you type, paste or open is sent anywhere.
Can I rely on the result?
It follows the public specification or formula named on this page and says where it simplifies. Check anything critical against the official tool or documentation before you ship it.