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
login.accounts.databricks.comauthNot in the scope2026-11-14
sapcases.auth.databricks.comauthNot in the scope2026-11-14
idp.gitspoke.cloud.databricks.comauthListed out of scope2026-11-14
idp.gitspoke.staging.cloud.databricks.comauth, stagingListed out of scope2026-11-14
auth.bse.corp.databricks.comauth, internalNot in the scope2026-11-14
auth.dev.bse.corp.databricks.comauth, dev, internalNot in the scope2026-11-14
okta-event-hook-api.dev.bse.corp.databricks.comapi, auth, dev, internalNot in the scope2026-11-14
okta-event-webhook-api.dev.bse.corp.databricks.comapi, auth, dev, internalNot in the scope2026-11-14
okta-event-hook-api.bse.corp.databricks.comapi, auth, internalNot in the scope2026-11-14
idp.gitspoke-fifth.dev.databricks.comauth, devNot in the scope2026-11-14
idp.gitspoke-fourth.dev.databricks.comauth, devNot in the scope2026-11-14
idp.gitspoke-third.dev.databricks.comauth, devNot in the scope2026-11-14
idp.gitspoke.dev.databricks.comauth, devNot in the scope2026-11-14
idp-poc.dev.databricks.comauth, devNot in the scope2026-11-14
login.dev.databricks.comauth, devNot in the scope2026-11-14
auth.yc-prototype.us-west-2.dev.databricks.comauth, devNot in the scope2026-11-14
psc-auth.dev.gcp.databricks.comauth, devListed out of scope2026-11-14
psc-auth.gcp.databricks.comauthListed out of scope2026-11-14
psc-auth.staging.gcp.databricks.comauth, stagingListed out of scope2026-11-14
login.databricks.comauthIn scope2026-11-14
oauth-fivetran-prod.databricks.comauthNot in the scope2026-11-14
oauth-fivetran-sandbox1.databricks.comauth, testNot in the scope2026-11-14
oauth-fivetran-sandbox2.databricks.comauth, testNot in the scope2026-11-14
oauth-fivetran-sandbox3.databricks.comauth, testNot in the scope2026-11-14
sso.aps1.pub-dev.databricks.comauth, devNot in the scope2026-11-14
sso.euw2.pub-dev.databricks.comauth, devNot in the scope2026-11-14
sso.pub-dev.databricks.comauth, devNot in the scope2026-11-14
auth.sso.pub-dev.databricks.comauth, devNot in the scope2026-11-14
sso.usw2.pub-dev.databricks.comauth, devNot in the scope2026-11-14
sso.pub.databricks.comauthNot in the scope2026-11-14
auth.sso.pub.databricks.comauthNot in the scope2026-11-14
signin.databricks.comauthNot in the scope2026-11-14
signin-regulated.databricks.comauthNot in the scope2026-11-14
sso.databricks.comauthNot in the scope2026-11-14
login.staging.databricks.comauth, stagingNot in the scope2026-11-14
sapcases.mulesoft.auth.testing.databricks.comauth, testNot 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