How to use
- In Contact, list the places to report a vulnerability, one per line. An email, a phone number or an https report-form URL all work.
- Pick an Expires date for the file. The default is about a year ahead.
- If needed, fill in the policy (Policy), encryption key (Encryption), thanks page (Acknowledgments) and Preferred-Languages.
- Make sure no red warning remains, then save with Download security.txt.
- Serve it at
https://yourdomain/.well-known/security.txt. It must be UTF-8 plain text delivered over HTTPS.
What security.txt is
When a security researcher finds a flaw on your site and has no idea whom to tell, the report easily ends up on a public forum or social media. security.txt records your reporting channel at a fixed location in a fixed format, and was standardised as RFC 9116 in 2022. It suits personal sites and open-source projects as much as large companies.
Fields
| Field | Required | Meaning |
|---|---|---|
Contact |
Yes | Where to report. mailto:, tel: or https:; may repeat |
Expires |
Yes | Expiry date. Less than a year is recommended; may appear once |
Encryption |
No | URL of the public key for encrypted reports |
Acknowledgments |
No | Page thanking reporters |
Preferred-Languages |
No | Languages to report in, as comma-separated language tags |
Canonical |
No | The file’s own canonical URL |
Policy |
No | Your vulnerability disclosure policy |
Hiring |
No | Security job postings |
CSAF |
No | URL of the CSAF advisory provider’s provider-metadata.json |
Fields that take URLs must start with https://. The tool flags http:// and relative paths as errors. If you type a bare email address into Contact, it adds mailto:, and a phone number such as +82 2 555 1234 becomes tel:+8225551234.
Example output
# Security contact for example.com
Contact: mailto:security@example.com
Contact: https://example.com/report
Expires: 2027-10-17T23:59:59Z
Preferred-Languages: ko, en
Canonical: https://example.com/.well-known/security.txt
Policy: https://example.com/policy
Expires is written as 23:59:59 UTC on the date you pick. A file past its date is treated as stale and untrustworthy, so put the renewal date in your calendar.
Signing and cautions
- To guard against tampered contact details, you can sign the file with a PGP cleartext signature, which RFC 9116 recommends. This tool does not sign; use the gpg command at the bottom of the page yourself. Never paste a private key into this page.
- Check that the mailbox you list is actually monitored. A reporting channel that nobody reads can be worse than no file.
- Related tools: the robots.txt Generator for crawler rules, the llms.txt Generator for an AI guide file, and the RSA Key Generator for an encryption key.
Frequently asked questions
Do I have to have one?
It is not a legal requirement, but it is the most standard way to show people who want to disclose a vulnerability responsibly where to go.
Where does the file go?
/.well-known/security.txt is the standard location. /security.txt is also allowed for backward compatibility, but for a new file use the .well-known path.
Can I set a long expiry?
Technically yes, but RFC 9116 recommends under a year and the tool warns at a year or more. The expiry exists to weed out abandoned files.
Can I list several contacts?
Yes. Contact may repeat, and earlier lines have higher priority.
Where does my input go?
The text you enter is processed only in your browser and never sent to a server.