Bug bounty program
DA
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 |
|---|---|---|
| accounts-lake-net-manager.central.managed.dev.ns.databricks.comadmin, dev | Not in the scope | 2026-11-14 |
| zippy-global.central.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| apiproxy-internal.shards.managed.dev.ns.databricks.comdev, internal | Not in the scope | 2026-11-14 |
| zippy-regional.az-centralus.shards.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| kafka-producer-proxy-ext.az-koreacentral-c2.shards.managed.dev.ns.databricks.comdata, dev | Not in the scope | 2026-11-14 |
| kafka-producer-proxy-ext.az-koreacentral.shards.managed.dev.ns.databricks.comdata, dev | Not in the scope | 2026-11-14 |
| zippy-regional.az-koreacentral.shards.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| az-westus-c2.shards.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| database-lm-proxy.az-westus-c2.shards.managed.dev.ns.databricks.comdata, dev | Not in the scope | 2026-11-14 |
| private-link-lm.az-westus-c2.shards.managed.dev.ns.databricks.comdev, internal | Not in the scope | 2026-11-14 |
| billing-sku-management.az-westus.shards.managed.dev.ns.databricks.comadmin, dev | Not in the scope | 2026-11-14 |
| database-lm-proxy.az-westus.shards.managed.dev.ns.databricks.comdata, dev | Not in the scope | 2026-11-14 |
| kafka-producer-proxy-ext.az-westus.shards.managed.dev.ns.databricks.comdata, dev | Not in the scope | 2026-11-14 |
| zippy-regional.az-westus.shards.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| debug-broker.shards.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| zippy-regional.gcp-us-east4.shards.managed.dev.ns.databricks.comdev | Not in the scope | 2026-11-14 |
| search-es-admin.shards.managed.dev.ns.databricks.comadmin, dev | Not in the scope | 2026-11-14 |
| sso.aps1.pub-dev.databricks.comauth, dev | Not in the scope | 2026-11-14 |
| sso.euw2.pub-dev.databricks.comauth, dev | Not in the scope | 2026-11-14 |
| sso.pub-dev.databricks.comauth, dev | Not in the scope | 2026-11-14 |
| auth.sso.pub-dev.databricks.comauth, dev | Not in the scope | 2026-11-14 |
| sso.usw2.pub-dev.databricks.comauth, dev | Not in the scope | 2026-11-14 |
| sap-integration-dev.databricks.comdev | Not in the scope | 2026-11-14 |
| service-anaplan-dev-ingestion.databricks.comdev | Not in the scope | 2026-11-14 |
| supporthub-dev.databricks.comdev | Not in the scope | 2026-11-14 |
| supporthub-dev-admin.databricks.comadmin, dev | Not in the scope | 2026-11-14 |
| dev.admin.training.databricks.comadmin, dev | Not in the scope | 2026-11-14 |
| dev.binder.training.databricks.comdev | Not in the scope | 2026-11-14 |
| dev.training.databricks.comdev | Not in the scope | 2026-11-14 |
| dev.labs.training.databricks.comdev | Not in the scope | 2026-11-14 |
| dev.lna.training.databricks.comdev | Not in the scope | 2026-11-14 |
| 2a57j78d05nkylnjxxxbsfyb1hqpih3.dev.lna.training.databricks.comdev | Not in the scope | 2026-11-14 |
| partnercalendar-dev.lpt.training.databricks.comdev | Not in the scope | 2026-11-14 |
| 2a57j77qq20y5ehfkbn2udbglnlliy1.partnercalendar-dev.lpt.training.databricks.comdev | Not in the scope | 2026-11-14 |
| www.partnercalendar-dev.lpt.training.databricks.comdev | Not in the scope | 2026-11-14 |
| whatsnew-dev.lpt.training.databricks.comdev | Not in the scope | 2026-11-14 |
| 2a57j77qq20y5ehfkbn2udbglnlliy1.whatsnew-dev.lpt.training.databricks.comdev | Not in the scope | 2026-11-14 |
| www.whatsnew-dev.lpt.training.databricks.comdev | Not in the scope | 2026-11-14 |
| www-dev.databricks.comdev | 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-15.