security.txt Generator
NewGenerate an RFC 9116 compliant security.txt file with contact, expiry, encryption, policy and canonical fields, with validation warnings.
RFC 9116 requires at least one Contact and exactly one Expires field. Use https URLs, and renew the file before it expires (under a year is recommended). With Astro or Cloudflare Pages, put the file in public/.well-known/security.txt.
Frequently Asked Questions
What is security.txt?
A standard file at /.well-known/security.txt telling researchers how to report vulnerabilities, defined in RFC 9116.
Which fields are mandatory?
At least one Contact and exactly one Expires field.
How often must I renew it?
Before the Expires date; picking a date under a year ahead is recommended.
Where do I host it?
At https://yourdomain/.well-known/security.txt over HTTPS (a copy at /security.txt is also allowed).