Create a security.txt file so anyone who finds a vulnerability in your site knows how to tell you. Enter a contact address and an expiry date, add your disclosure policy, PGP key, acknowledgments page and preferred languages, and the file is validated against RFC 9116 as you type. Download it and publish it at /.well-known/security.txt. It runs in your browser.
| Field | Required | Example |
|---|---|---|
| Contact | Yes (one or more) | mailto:[email protected] |
| Expires | Yes | 2027-06-01T00:00:00.000Z |
| Encryption | No | https://example.com/pgp-key.txt |
| Policy | No | https://example.com/disclosure |
| Acknowledgments | No | https://example.com/thanks |
| Preferred-Languages | No | en, de |
| Canonical | No | https://example.com/.well-known/security.txt |
| Hiring | No | https://example.com/jobs |
At https://your-site/.well-known/security.txt, served over HTTPS. A copy at /security.txt is optional.
Contact (at least one) and Expires. Everything else is optional.
Less than a year. That way, if you forget to update it, the file expires instead of sending reports to an address nobody reads. Set a reminder to renew it.
It's recommended if you have a PGP key: gpg --clearsign security.txt produces a signed version researchers can verify.
Yes — one per line. Put the preferred one first.
No. The file is built and validated in your browser.
RFC 9116 defines security.txt, a plain-text file at /.well-known/security.txt that tells security researchers how to report a vulnerability. Two fields are mandatory: at least one Contact and exactly one Expires. Contact values must be URIs, so the generator turns a bare email into mailto: and a phone number into tel:, and leaves https:// links alone; the first contact listed is treated as preferred. Expires must be a date-time in the future, and the RFC recommends it be less than a year ahead so that a forgotten file goes stale rather than misdirecting reports indefinitely — the validator flags a past date as an error and anything more than a year away as a warning, and the date is written in ISO 8601 UTC form. The optional fields — Encryption (a key), Acknowledgments, Policy, Hiring and Canonical — must be https URIs and each may appear more than once; Preferred-Languages is a comma-separated list of language tags. The file must be served over HTTPS, and can be signed with OpenPGP cleartext signing so readers can verify it hasn't been tampered with. Generation and validation happen in the page.