Skip to main content
SiteScan.top

security.txt: tell researchers where to report a vulnerability before they go public

A five-line text file in /.well-known/ decides whether a found vulnerability reaches your inbox or a public forum. What RFC 9116 requires, how to write the file, and the mistakes that make it useless.

Security · Published: 3 November 2026 · 5 min read · Дмитрий Орлов

Sooner or later someone finds a problem on your site: an open admin panel, a password reset that leaks e-mail addresses, a forgotten test subdomain. Most of the people who find these things want to tell you. The question is whether they can find out how. A support form answered by a first-line agent, a generic info@ address, a social-media account — the report gets lost, the researcher gives up, and sometimes the next place the problem appears is a public post.

security.txt solves exactly this. It is a small plain-text file at a fixed address that says where security reports should go. It was standardised as RFC 9116 in 2022, and security researchers, bug-bounty platforms and automated scanners look for it first.

Where it lives

The file is served at https://example.com/.well-known/security.txt, over HTTPS, as text/plain. The older location in the site root, /security.txt, is still read by some tools, but /.well-known/ is the one the standard defines. Every domain and subdomain that runs its own service can have its own file; if they all share one security team, they can carry the same contents.

What goes in it

Two fields are required:

The useful optional ones:

A complete, realistic example:

``text Contact: mailto:security@example.com Contact: https://example.com/security/report Expires: 2027-10-31T23:00:00Z Preferred-Languages: en, ru Policy: https://example.com/security/policy Canonical: https://example.com/.well-known/security.txt ``

The file can be signed with an OpenPGP cleartext signature so a reader can tell it was not tampered with, but an unsigned file is valid and far better than none.

Mistakes that make it useless

Do you need a bug-bounty programme?

No. security.txt is a contact, not a promise of payment. A short policy that says what you consider in scope, that you will not pursue good-faith researchers, and how fast you reply is enough for most companies. A paid programme can come later, if the volume of reports justifies it.

What SiteScan checks

Every scan requests /.well-known/security.txt and counts it as published only when the answer is a 200, is not an HTML page, and has at least one line starting with Contact:. So a site that answers every address with its own homepage does not pass by accident. The row appears in the "Well-known files" group of the site checks; because the file is optional, a missing one is shown as a neutral fact, not an error. Details are in the security.txt help page. The rest of the security picture — security headers, certificates, exposed files — is in the same report. Run a free scan to check yours.

Read next

Check how much of this is on your own site

A free scan surfaces broken links, JS errors and performance problems in about a minute.