security.txt

# Our security address
Contact: [email protected]

# Our PGP key
Encryption: https://example.com/pgp-key.txt
Generate security.txt file Learn more
“When security risks in web services are discovered by independent security researchers who understand the severity of the risk, they often lack the channels to properly disclose them. As a result, security issues may be left unreported. Security.txt defines a standard to help organizations define the process for security researchers to securely disclose security vulnerabilities.”
Read the Internet draft ➤

FAQ

What is the main purpose of security.txt?

The main purpose of security.txt is to help make things easier for companies and security researchers when trying to secure platforms. Thanks to security.txt, security researchers can easily get in touch with companies about security issues.

Is security.txt an RFC?

security.txt is currently an Internet draft that has been submitted for RFC review. This means that security.txt is still in the early stages of development. We welcome contributions from the public: https://github.com/securitytxt/security-txt

Where should I put the security.txt file?

The current draft states that the security.txt file should be located under the top-level directory. We are currently writing a new version of the draft that places security.txt under the /.well-known/ path (/.well-known/security.txt) [RFC5785]. Therefore it is highly recommended to use the /.well-known/ path for your security.txt file.

Will adding an email address expose me to spam bots?

The email value is an optional field. If you are worried about spam you can set a URI as the value and link to your security policy.

Generate your security.txt file

Contact:

Encryption:

Acknowledgements:


Contributors

The editor would like to acknowledge the help provided during the development of security.txt by the following individuals:

Tom Hudson helped writing the "File Format Description" and wrote several security.txt parsers.

Joel Margolis was a big help when it came to wording the Internet draft appropriately.

Jobert Abma for raising issues and concerns that might arise when using certain directives.

Gerben Janssen van Doorn for reviewing the Internet draft multiple times.

Justin Calmus was always there to answer questions related to writing the Internet draft.

Casey Ellis had several ideas related to security.txt that helped shape security.txt itself.

Eduardo Vela and Krzysztof Kotowicz for meeting in person to discuss security.txt in great detail.

Ryan Black for registering securitytxt.org and setting up the website.

Security.txt projects

Identify and Parse Web Security Policies Files in R by boB Rudis.

The official Chrome extension for security.txt by Karel Origin.

A security.txt parser for Go by Tom Hudson.

A security.txt parser for PHP by Tom Hudson.

Golang security.txt parser and cli tool by Adam Shannon.

What can you do to help?

Tweet about security.txt Contribute