Free security.txt Validator
Check whether a site publishes a valid security.txt · the RFC 9116 file that tells researchers how to responsibly report vulnerabilities.
Free account required to run the check. What you type here is kept through sign-in.
How to use it
- Enter your domain, for example example.com.
- Run the check. SimplyScan fetches https://example.com/.well-known/security.txt, and /security.txt if that is missing.
- Read the validation: which required fields are present, whether the file has expired, and where it was found.
- Publish or fix the file, then check again.
Example
A file that passes: a contact, an expiry date under a year away and the canonical location.
Input
# https://example.com/.well-known/security.txt Contact: mailto:security@example.com Expires: 2027-06-30T23:59:59Z Preferred-Languages: en Policy: https://example.com/security-policy
Result
Found at /.well-known/security.txt ✓ Contact field present ✓ Expires field present and in the future ✓ Served over HTTPS
What the checks mean
- No security.txt
- Researchers who find a bug have no documented way to tell you, so reports go to a support inbox, social media, or nowhere.
- Contact
- Required. A mailto: address or an https:// form where reports should go.
- Expires
- Required by RFC 9116. It tells readers when to stop trusting the file. Keep it less than a year away and update it before it passes.
- Location
- /.well-known/security.txt is the canonical place. A copy at /security.txt still works for older tools.
- Policy, Acknowledgments, Encryption, Preferred-Languages
- Optional fields: your disclosure rules, a thank-you page, a PGP key and the languages you read.
Where to put the file
Vite, Next.js, Lovable and most static sites
public/.well-known/security.txt
Files in public/ are served from the site root, so this becomes /.well-known/security.txt.
Netlify and Cloudflare Pages
<publish folder>/.well-known/security.txt
Some build tools skip folders that start with a dot. Open the live URL afterwards to confirm the file is there.
Go deeper
Page updated
Frequently asked questions
Where should security.txt live?
At /.well-known/security.txt (the canonical location). A copy at /security.txt is tolerated for legacy reasons, but the well-known path is required by RFC 9116.
What fields are required?
A Contact field is mandatory. An Expires field is required by RFC 9116, and the file should be served over HTTPS. Recommended extras include Encryption, Policy, Acknowledgments, and Preferred-Languages.
Will this invite attacks?
No. The file only tells people who have already found something where to report it. Without it, the same people just have no good way to reach you.
Do I need a bug bounty to publish one?
No. A contact address is enough. Add a Policy link if you want to say what you will and won't accept.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
CORS Tester
Test any URL for dangerous CORS misconfigurations · origin reflection, wildcard-with-credentials, and null-origin acceptance that can leak authenticated data.
Exposed Files Scanner
Check whether your site accidentally exposes .env, .git/config, backup archives, or other high-risk files.
Supabase RLS Checker
Discover tables advertised by your public API and check whether anonymous reads return rows.