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
git-commit-webhook.dev.bse.corp.databricks.comdev, git, internalNot in the scope2026-11-14
git-jira-api.dev.bse.corp.databricks.comapi, dev, git, internal, toolsNot in the scope2026-11-14
bitbucket.dev.databricks.comdev, gitNot in the scope2026-11-14
repos-gitlab-server.dev.databricks.comdev, gitNot in the scope2026-11-14
repos-gitlab-server-alb.dev.databricks.comdev, gitNot in the scope2026-11-14
repos-gitlab-server-public.dev.databricks.comdev, gitNot in the scope2026-11-14
repos-gitlab-test-server.dev.databricks.comdev, git, testNot in the scope2026-11-14
git.training.databricks.comgitNot 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