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 |
|---|---|---|
| demo.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| demo-dnb-analyticsstudio.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| dnb-analytics-studio-demo-100.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| dnb-analytics-studio-demo-101.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| e2-demo-field-eng.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| sh1.formulaone.qa.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| spgmi-databricks-qa.cloud.databricks.comtest | Listed out of scope | 2026-11-14 |
| acme-canary-test-staging.staging.cloud.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| dse-waf-stage-demo.staging.cloud.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| dse-waf-stage-test.staging.cloud.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| dse-waf-waf-stage-test.staging.cloud.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| waf-stage-test.staging.cloud.databricks.comstaging, test | Listed out of scope | 2026-11-14 |
| acme-canary-test-prod.gcp.databricks.comstaging, test | 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 |
| acme-canary-test-staging.staging.gcp.databricks.comstaging, test | 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.