security.txt (RFC 9116) in API security
It tells a researcher where to report a vulnerability instead of guessing.
1 of 24 companies we measured here publish it, that is 4%. Last checked 2026-10-17.
4% here against 11% across every category we measure. API security sits below the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to security.txt (RFC 9116) across all categories, or to API security.
- Found1
- Not found at checked addresses23
- Not measured0
24 companies in total. Unmeasured companies are excluded from the published share.
Published
Served at /.well-known/security.txt.
| Vendor | What we found |
|---|---|
| ZAP | https://www.zaproxy.org/.well-known/security.txtChecked |
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 checkedChecked |
| Akto | 1 address checkedChecked |
| APIsec | 1 address checkedChecked |
| Approov | 1 address checkedChecked |
| Aptori | 1 address checkedChecked |
| Beagle Security | 1 address checkedChecked |
| Cequence | 1 address checkedChecked |
| Cloudbric | 1 address checkedChecked |
| Corsha | 1 address checkedChecked |
| Curity | 1 address checkedChecked |
| Cyber Chief | 1 address checkedChecked |
| Data Theorem | 1 address checkedChecked |
| FireTail | 1 address checkedChecked |
| Ghost Security | 1 address checkedChecked |
| Impart Security | 1 address checkedChecked |
| Levo.ai | 1 address checkedChecked |
| PortSwigger | 1 address checkedChecked |
| Pynt | 1 address checkedChecked |
| Reblaze | 1 address checkedChecked |
| Salt Security | 1 address checkedChecked |
| ThreatX | 1 address checkedChecked |
| Traceable | 1 address checkedChecked |
| Wallarm | 1 address checkedChecked |
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.
Other criteria in API security
- Data processing agreement
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- No third-party tracking before consent
- Notice before subprocessors change
- Named privacy contact
security.txt (RFC 9116) in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.