security.txt Generator
Generate security.txt files following the RFC 9116 standard for vulnerability disclosure
security.txt Generator
Generate security.txt files following the RFC 9116 standard for vulnerability disclosure
URI for reporting security vulnerabilities. Must use mailto:, https://, or tel: scheme. At least one Contact field is required.
Date and time after which this security.txt data should be considered stale. Required by RFC 9116. Recommended: no more than one year from now.
URI pointing to an encryption key for secure communication. Must use https://, dns:, or openpgp4fpr: scheme.
URI to a page listing security researchers who have responsibly reported vulnerabilities.
The canonical URI where this security.txt file is located. Helps verify authenticity.
URI to the organization's vulnerability disclosure policy.
Comma-separated list of preferred language codes (ISO 639) for security reports.
URI to the organization's security-related job positions.
# This is a security.txt file that follows the RFC 9116 standard. # https://www.rfc-editor.org/rfc/rfc9116 Contact: mailto:security@example.com Preferred-Languages: en
