Bug bounty program
SE
Semrush
Most upvoted reports56
All reportsSubdomains5,693
| Name | Scope | First seen |
|---|---|---|
| github-explorer-search.sellzone.comgit | In scope | 2026-11-14 |
| git.semrush.comgit | In scope | 2026-11-14 |
| gitlab.semrush.comgit | In scope | 2026-11-14 |
| git.tncovvlzzzlbstl.semrush.comgit | In scope | 2026-11-14 |
| core-docker-gitlab-runner.semrush.netgit, tools | In scope | 2026-11-14 |
| www.core-docker-gitlab-runner.semrush.netgit, tools | In scope | 2026-11-14 |
| core-gitlab-runner-2.semrush.netgit | In scope | 2026-11-14 |
| www.core-gitlab-runner-2.semrush.netgit | In scope | 2026-11-14 |
| github.semrush.netgit | In scope | 2026-11-14 |
| gitlab.semrush.netgit | In scope | 2026-11-14 |
| gitlab-demo.rc.semrush.netgit, test | In scope | 2026-11-14 |
5,384 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.