Skip to content

Bug bounty program

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

Subdomains of Databricks
NameScopeFirst seen
grafana-ngrok.cloud.databricks.commonitoringListed out of scope2026-11-14
metrics-write-azure-ukwest.cloud.databricks.commonitoringListed out of scope2026-11-14
metrics-write-azure-westeurope.cloud.databricks.commonitoringListed out of scope2026-11-14
status.staging.cloud.databricks.commonitoring, stagingListed out of scope2026-11-14
logging-api.aruba.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs1.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs2.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs3.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs4.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs5.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs6.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs7.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstest-zs8.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzs9.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc1.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc2.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc3.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc4.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc5.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc6.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc7.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc8.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsc9.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl1.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl2.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl3.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl4.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl5.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl6.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl7.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzscl8.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsclr.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjosstestzsclr1.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjspycloud.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjspycloudw.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cjspycloudwh.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cortex.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.cortex2.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.descope.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.docontrol.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.marketo.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.material-security.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.materialsecurity.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.netsuite.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.spycloud.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.verkada-dev.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
logging-api.zscaler.dev-sec.databricks.comapi, dev, monitoringNot in the scope2026-11-14
metrics-write-azure-westusc2.dev.databricks.comdev, monitoringNot in the scope2026-11-14
sentry-azure-koreacentral.dev.databricks.comdev, monitoringNot in the scope2026-11-14
sentry-azure-westus.dev.databricks.comdev, monitoringNot in the scope2026-11-14
status.gcp.databricks.commonitoringListed out of scope2026-11-14
logging-api.abnormalai.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.cortex.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.cortex2.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.descope.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.docontrol.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.marketo.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.materialsecurity.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.netsuite.sec.databricks.comapi, monitoringNot in the scope2026-11-14
logging-api.zscaler.sec.databricks.comapi, monitoringNot in the scope2026-11-14
status.databricks.commonitoringNot in the scope2026-11-14
status.temp.databricks.commonitoringNot in the scope2026-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.

Updated AboutDevelopersSign in