security.txt Generator

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.

security.txt fields

FieldRequiredExample
ContactYes (one or more)mailto:[email protected]
ExpiresYes2027-06-01T00:00:00.000Z
EncryptionNohttps://example.com/pgp-key.txt
PolicyNohttps://example.com/disclosure
AcknowledgmentsNohttps://example.com/thanks
Preferred-LanguagesNoen, de
CanonicalNohttps://example.com/.well-known/security.txt
HiringNohttps://example.com/jobs

When to use it

  1. Give researchers a clear route to report vulnerabilities.
  2. Meet a bug-bounty or compliance checklist item.
  3. Renew an expiring security.txt.
  4. Point to your vulnerability disclosure policy.

How to Use

  1. Enter one or more contacts — email, phone or a reporting form URL.
  2. Choose an expiry date under a year away.
  3. Add policy, encryption key, acknowledgments, hiring and canonical URLs if you have them.
  4. Download security.txt and publish it at /.well-known/security.txt.

Features

  1. RFC 9116 field set
  2. Required-field and expiry validation
  3. Automatic mailto: and tel:
  4. Multiple values per field
  5. Preferred languages
  6. 100% client-side

FAQs

Where does security.txt go?

At https://your-site/.well-known/security.txt, served over HTTPS. A copy at /security.txt is optional.

Which fields are required?

Contact (at least one) and Expires. Everything else is optional.

How far ahead should Expires be?

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.

Should I sign it?

It's recommended if you have a PGP key: gpg --clearsign security.txt produces a signed version researchers can verify.

Can I list more than one contact?

Yes — one per line. Put the preferred one first.

Is my data uploaded?

No. The file is built and validated in your browser.

Technical Details

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.

Security Tools

Security Tools

  • AES Encryption
  • Bcrypt Hash Generator
  • BIP39 Mnemonic Generator
  • CVSS Calculator
  • CORS Debugger
  • RSA Key Generator
  • SRI Hash Generator
  • Permissions-Policy Builder