security.txt (RFC 9116) in API security
It tells a researcher where to report a vulnerability instead of guessing.
0 of 12 vendors we measured here publish it, that is 0%. Last checked 2026-09-02.
0% here against 14% across every category we measure. API security sits below the overall share for this criterion.
Back to security.txt (RFC 9116) across all categories, or to API security.
Published
Served at /.well-known/security.txt.
None of the vendors we measured here published this.
No security.txt found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| 42Crunch | 1 address checked |
| Akto | 1 address checked |
| APIsec | 1 address checked |
| Approov | 1 address checked |
| Aptori | 1 address checked |
| Beagle Security | 1 address checked |
| Cequence | 1 address checked |
| Data Theorem | 1 address checked |
| FireTail | 1 address checked |
| Pynt | 1 address checked |
| Salt Security | 1 address checked |
| ThreatX | 1 address checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
None. Every vendor here was measured for this criterion.
Found something we missed? Tell us and the next run picks it up.