SaaS Ranking

security.txt (RFC 9116) in Cloud hosting

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

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

49% here against 11% across every category we measure. Cloud hosting 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 hosting.

The evidence at a glance
  • Found17
  • Not found at checked addresses18
  • Not measured2

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

Published

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

VendorWhat we found
Clever Cloud https://clever-cloud.com/.well-known/security.txtChecked
Cloudflare https://www.cloudflare.com/.well-known/security.txtChecked
DigitalOcean https://www.digitalocean.com/.well-known/security.txtChecked
Exoscale https://www.exoscale.com/.well-known/security.txtChecked
Gcore https://gcore.com/.well-known/security.txtChecked
Hetzner https://www.hetzner.com/.well-known/security.txtChecked
IONOS Cloud https://cloud.ionos.com/.well-known/security.txtChecked
Kinsta https://kinsta.com/.well-known/security.txtChecked
Mittwald https://www.mittwald.de/.well-known/security.txtChecked
OVHcloud https://www.ovhcloud.com/.well-known/security.txtChecked
Render https://render.com/.well-known/security.txtChecked
Scaleway https://www.scaleway.com/.well-known/security.txtChecked
Upstash https://upstash.com/.well-known/security.txtChecked
Upsun https://upsun.com/.well-known/security.txtChecked
Val Town https://www.val.town/.well-known/security.txtChecked
Vercel https://vercel.com/.well-known/security.txtChecked
WP Engine https://wpengine.com/.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
AccelByte Gaming Services 1 address checkedChecked
Aptible 1 address checkedChecked
Beam 1 address checkedChecked
Bunny 1 address checkedChecked
Contabo 1 address checkedChecked
Fastly 1 address checkedChecked
Fly.io 1 address checkedChecked
Heroku 1 address checkedChecked
Koyeb 1 address checkedChecked
MacStadium Orka 1 address checkedChecked
Netlify 1 address checkedChecked
Northflank 1 address checkedChecked
Railway 1 address checkedChecked
Second Front Game Warden 1 address checkedChecked
T Cloud Public 1 address checkedChecked
Tensorlake 1 address checkedChecked
UpCloud 1 address checkedChecked
Vultr 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
Akamai The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Cloudways The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked

Other criteria in Cloud hosting

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.