SaaS Ranking

security.txt (RFC 9116) in API management

It tells a researcher where to report a vulnerability instead of guessing.

5 of 44 companies we measured here publish it, that is 11%. Last checked 2026-10-17.

11% here against 11% across every category we measure. API management sits exactly at 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 management.

The evidence at a glance
  • Found5
  • Not found at checked addresses39
  • Not measured3

47 companies in total. Unmeasured companies are excluded from the published share.

Published

Served at /.well-known/security.txt.

VendorWhat we found
Postman https://www.postman.com/.well-known/security.txtChecked
Speakeasy https://www.speakeasy.com/.well-known/security.txtChecked
Stainless https://www.stainless.com/.well-known/security.txtChecked
Svix https://www.svix.com/.well-known/security.txtChecked
Traefik https://traefik.io/.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.

VendorWhat we found
Apidog 1 address checkedChecked
Apitally 1 address checkedChecked
Apollo GraphQL 1 address checkedChecked
Archbee 1 address checkedChecked
Axway 1 address checkedChecked
Blobr 1 address checkedChecked
Bump.sh 1 address checkedChecked
Doctave 1 address checkedChecked
Document360 1 address checkedChecked
DreamFactory 1 address checkedChecked
Escape 1 address checkedChecked
Fern 1 address checkedChecked
GitBook 1 address checkedChecked
Gravitee 1 address checkedChecked
Hasura 1 address checkedChecked
Hookdeck 1 address checkedChecked
Hoppscotch 1 address checkedChecked
Kong 1 address checkedChecked
KrakenD 1 address checkedChecked
Kusk 1 address checkedChecked
Mintlify 1 address checkedChecked
Moesif 1 address checkedChecked
Monoscope (formerly APIToolkit) 1 address checkedChecked
Nevatech 1 address checkedChecked
ReadMe 1 address checkedChecked
Redocly 1 address checkedChecked
Scalar 1 address checkedChecked
Sensedia 1 address checkedChecked
Slate 1 address checkedChecked
SmartBear 1 address checkedChecked
Software AG 1 address checkedChecked
Solo.io 1 address checkedChecked
Theneo 1 address checkedChecked
Treblle 1 address checkedChecked
Tyk 1 address checkedChecked
Unified.to 1 address checkedChecked
Unkey 1 address checkedChecked
Weavy 1 address checkedChecked
Zuplo 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.

VendorWhat we found
Fiorano The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Stoplight The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked
WSO2 The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked

Other criteria in API management

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.