Protego field desk

Free security tool

security.txt Generator and Validator

Give security researchers a clear way to contact you. Create a file, validate pasted text, or check a public domain.

Quick answer

Create a security.txt file to tell researchers how to report vulnerabilities, or check an existing file for common RFC 9116 issues. Generate and paste modes run locally. Domain checks use a protected server fetch. A passing format check does not verify contact ownership, signature authenticity or permission to test a website.

Create or validate a file

One URI per line for repeatable fields. Preferred-Languages uses one comma-separated line. Only Contact and Expires are required. Nothing is uploaded.

Use an ISO 8601 date and time with timezone. Choose less than a year ahead.

Publish and maintain it

Save as UTF-8 at /.well-known/security.txt and serve over HTTPS with Content-Type: text/plain; charset=utf-8. Keep contacts current and renew Expires.

Optionally clear-sign the file with OpenPGP and include its Canonical URL. Verify with a trusted key separately. This file provides reporting instructions; it does not grant testing authorization or replace a disclosure policy.

Frequently asked questions

Where should I publish security.txt?

Publish at https://your-domain/.well-known/security.txt as UTF-8 text/plain. The root /security.txt path is for legacy compatibility. The well-known file takes precedence if both exist.

Which fields are required?

Include at least one Contact URI and exactly one Expires timestamp. Put each contact on its own line in preference order. Email contacts need mailto:, phone contacts need tel:, and web contacts need HTTPS.

How should I choose Expires?

Use an ISO 8601 timestamp in RFC 3339 form with a timezone. RFC 9116 recommends less than a year ahead. Review the file before expiry; expired contact information should not be relied on.

Does the validator verify an OpenPGP signature?

No. It detects a cleartext signature envelope and parses its readable fields. Verify the signature separately using a trusted key. Unsigned files are supported; signing is recommended.

What does Canonical mismatch mean?

The URL used to fetch the file is missing from its Canonical entries. RFC 9116 says the contents should not be trusted in that situation. Check redirects and the final URL.

Is CSAF supported and is my input uploaded?

CSAF is an optional IANA-registered field linking to CSAF provider metadata. Generated and pasted text stays in your browser. Domain mode sends the domain to Protego for a public fetch with a 32 KB response cap. Server checks use the shared lookup rate limits.

References