security.txt Generator (RFC 9116)

Tell security researchers how to report vulnerabilities by publishing a correct security.txt file.

Use the tool

Why this tool exists

Enter one or more contacts (mailto:, tel: or https: URIs), an expiry date (defaults to one year ahead, since RFC 9116 recommends less than a year) and optional Encryption, Acknowledgments, Policy, Hiring, Preferred-Languages and Canonical fields. The tool validates the URIs and dates and prints the file with a reminder where to host it.

Place the file at /.well-known/security.txt over HTTPS as text/plain, and renew the Expires date before it passes. Optionally clearsign it with PGP.

No data is sent anywhere: the work happens in your browser, so you can use it offline once the page has loaded.

How to use it

  1. Enter your security contact and a policy URL if you have one.
  2. Leave Expires blank for one year, or set a date.
  3. Copy the output to /.well-known/security.txt.
  4. Put a reminder in your calendar to renew it.

Frequently asked questions

Is security.txt required?

No, but it is a recognised way to receive reports and is checked by some scanners.

Why does it expire?

So that stale contact details are not trusted. Researchers are told to ignore expired files.

Can I use a form instead of email?

Yes. Use an https: URL as the Contact value.

Is my data sent anywhere?

No. Everything is processed in your browser, and the page makes no network requests with your input.