Free Tool

security.txt Validator

Check if a website has a valid security.txt file for responsible vulnerability disclosure.

Why security.txt Matters

Easy Contact

Security researchers can quickly find how to report vulnerabilities.

Responsible Disclosure

Define your vulnerability disclosure policy clearly.

Industry Standard

RFC 9116 standard adopted by major organizations.

Frequently Asked Questions

What is security.txt?

security.txt is a standard (RFC 9116) that allows websites to define security policies and contact information for security researchers to report vulnerabilities.

Where should security.txt be located?

It should be at /.well-known/security.txt (preferred) or /security.txt in the root of your domain.

What should security.txt contain?

At minimum: a Contact field (email or URL) and an Expires field. Optional fields include Encryption, Acknowledgments, Policy, and Preferred-Languages.

Check beyond your security contact file

This tool checks whether your domain publishes a valid security.txt file.

Scan your deployed website for exposed secrets, security misconfigurations, and other supported application security issues.

This checks your deployed app, not your private repository.

Try URL and repository scans for 7 days. Your 3 trial scans share one allowance, and every report includes its available findings, fixes, and exports.

Card required. Then $29/month for Go unless you cancel before the trial ends.

Create an account to save your scan. Use a website you own or have permission to scan.