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 |
|---|---|---|
| git-jira-api.dev.bse.corp.databricks.comapi, dev, git, internal, tools | Not in the scope | 2026-11-14 |
| dev-registry.corp.databricks.comdev, internal, tools | Not in the scope | 2026-11-14 |
| kube-frankfurt-dev.dev.databricks.comdev, tools | Not in the scope | 2026-11-14 |
| kube-london-dev.dev.databricks.comdev, tools | Not in the scope | 2026-11-14 |
| master.central-a.kube.dev.databricks.comdev, tools | Not in the scope | 2026-11-14 |
| redash.dev.databricks.comdev, tools | Not in the scope | 2026-11-14 |
| redash-demo.dev.databricks.comdev, test, tools | Not in the scope | 2026-11-14 |
| registry.dev.databricks.comdev, tools | Not in the 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.