SaaS Ranking

security.txt (RFC 9116) in Data warehouses and databases

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

14 of 41 companies we measured here publish it, that is 34%. Last checked 2026-10-18.

34% here against 11% across every category we measure. Data warehouses and databases 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 Data warehouses and databases.

The evidence at a glance
  • Found14
  • Not found at checked addresses27
  • Not measured4

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

Published

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

VendorWhat we found
Aiven https://console.aiven.io/.well-known/security.txtChecked
ClickHouse https://clickhouse.com/.well-known/security.txtChecked
Convex https://www.convex.dev/.well-known/security.txtChecked
Databricks https://www.databricks.com/.well-known/security.txtChecked
Dremio https://dremio.com/.well-known/security.txtChecked
EDB https://www.enterprisedb.com/.well-known/security.txtChecked
Prisma https://www.prisma.io/.well-known/security.txtChecked
Redis https://redis.io/.well-known/security.txtChecked
Snowflake https://www.snowflake.com/.well-known/security.txtChecked
Supabase https://supabase.com/.well-known/security.txtChecked
SurrealDB https://surrealdb.com/.well-known/security.txtChecked
Teradata https://www.teradata.com/.well-known/security.txtChecked
Tiger Data https://www.tigerdata.com/.well-known/security.txtChecked
Turso https://turso.tech/.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
CockroachDB 1 address checkedChecked
Crunchy Data 1 address checkedChecked
DoubleCloud 1 address checkedChecked
Dragonfly 1 address checkedChecked
Exasol 1 address checkedChecked
Firebolt 1 address checkedChecked
Gel 1 address checkedChecked
Instaclustr 1 address checkedChecked
Materialize 1 address checkedChecked
MotherDuck 1 address checkedChecked
Neon 1 address checkedChecked
Nile 1 address checkedChecked
Percona 1 address checkedChecked
PingCAP TiDB Cloud 1 address checkedChecked
PlanetScale 1 address checkedChecked
Qdrant 1 address checkedChecked
QuestDB 1 address checkedChecked
ScyllaDB 1 address checkedChecked
SingleStore 1 address checkedChecked
StarRocks 1 address checkedChecked
Tinybird 1 address checkedChecked
Ubicloud 1 address checkedChecked
Vertica 1 address checkedChecked
Weaviate 1 address checkedChecked
Xata 1 address checkedChecked
Yellowbrick 1 address checkedChecked
YugabyteDB 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
Couchbase The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Cybertec The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
InfluxData The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
MongoDB Atlas The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked

Other criteria in Data warehouses and databases

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.