Bug bounty program
Databricks
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 9
- Disclosed reports
- 0
- Subdomains
- 1,187
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains1,187
| Name | Scope | First seen |
|---|---|---|
| 9.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| accounts.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| acme-canary-test-prod.gcp.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| tunnel.asia-south1.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 0.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 1.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 2.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 3.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 4.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 5.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 6.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 7.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 8.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| 9.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| acme-canary-test-dev.dev.gcp.databricks.comdev, staging, test | Listed out of scope | 2026-11-14 |
| sanity-check.force-rotate-testing.dev.gcp.databricks.comdev, test | Listed out of scope | 2026-11-14 |
| psc-auth.dev.gcp.databricks.comauth, dev | Listed out of scope | 2026-11-14 |
| ui-assets.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| storage.us-east4.dev.gcp.databricks.comdev | Listed out of scope | 2026-11-14 |
| docs.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| tunnel.europe-west1.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| kb.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| psc-auth.gcp.databricks.comauth | Listed out of scope | 2026-11-14 |
| staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 0.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 1.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 2.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 3.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 4.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 5.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 6.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 7.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 8.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| 9.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| acme-canary-test-staging.staging.gcp.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| psc-auth.staging.gcp.databricks.comauth, staging | Listed out of scope | 2026-11-14 |
| ui-assets.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| storage.us-central1.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| storage.us-east1.staging.gcp.databricks.comstaging | Listed out of scope | 2026-11-14 |
| status.gcp.databricks.commonitoring | Listed out of scope | 2026-11-14 |
| ui-assets.gcp.databricks.com | Listed out of scope | 2026-11-14 |
| us-central1.gcp.databricks.com | Listed out of scope | 2026-11-14 |
3 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-14.