About this tool
Create an RFC 9116 security.txt so researchers know how to report vulnerabilities — contacts, expiry, policy and languages checked.
Contacts become mailto:, https: or tel: lines; Expires is written in the required date-time format; optional Encryption, Acknowledgments, Policy, Hiring and Canonical links must use HTTPS; preferred languages are checked as language codes.
Example: Contacts (email, https:// link or tel:, one per line) = security@example.com, Expires on = 2099-12-31, Policy URL = https://example.com/security-policy, Preferred languages (e.g. en, ar) = en, ar → security.txt = Contact: mailto:security@example.com Expires: 2099-12-31T23:59:00Z Policy: https://example.com/security-policy Preferred-Languages: en, ar , Lines written = 4.
security.txt only tells people how to reach you. It does not make the site more secure on its own.
Quick steps
- Fill in the fields you need — empty optional fields are left out.
- Press Generate (or Try an example to see how it works).
- Copy or download the result and paste it into your site.
Everything runs in your browser. Nothing you type is sent to 1CLIK.
FAQ
How does the security.txt Generator work?
Contacts become mailto:, https: or tel: lines; Expires is written in the required date-time format; optional Encryption, Acknowledgments, Policy, Hiring and Canonical links must use HTTPS; preferred languages are checked as language codes.
What should I keep in mind?
security.txt only tells people how to reach you. It does not make the site more secure on its own.
Is my data sent anywhere?
No. What you type stays on your device; the page only shows the result.