SaaS Ranking

security.txt (RFC 9116) in Cloud storage

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

4 of 24 companies we measured here publish it, that is 17%. Last checked 2026-10-16.

17% here against 11% across every category we measure. Cloud storage sits above 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 Cloud storage.

The evidence at a glance
  • Found4
  • Not found at checked addresses20
  • Not measured4

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

Published

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

VendorWhat we found
Jottacloud https://jottacloud.com/.well-known/security.txtChecked
ownCloud https://owncloud.com/.well-known/security.txtChecked
Proton Drive https://proton.me/.well-known/security.txtChecked
Tresorit https://144472103.fs1.hubspotusercontent-eu1.net/hubfs/144472103/for-dev-review/public/.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
Backblaze 1 address checkedChecked
Box 1 address checkedChecked
Degoo 1 address checkedChecked
Dropbox 1 address checkedChecked
Egnyte 1 address checkedChecked
Filen 1 address checkedChecked
Filestash 1 address checkedChecked
Icedrive 1 address checkedChecked
IDrive 1 address checkedChecked
Internxt 1 address checkedChecked
Kiteworks 1 address checkedChecked
Koofr 1 address checkedChecked
Livedrive 1 address checkedChecked
luckycloud 1 address checkedChecked
pCloud 1 address checkedChecked
RushFiles 1 address checkedChecked
Seafile 1 address checkedChecked
Storj 1 address checkedChecked
Sync.com 1 address checkedChecked
Wasabi 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
Mega The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Nextcloud None of the addresses could be reached, so this was not measured.Checked
SpiderOak The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked
TeamDrive The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked

Other criteria in Cloud storage

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.