Bug bounty program
GI
GitLab
Most upvoted reports257
All reportsSubdomains785
| Name | Scope | First seen |
|---|---|---|
| centos-test.gitlab.comtest | Not in the scope | 2026-11-14 |
| demo.gitlab.comtest | Not in the scope | 2026-11-14 |
| runway-ci-test-4jpyc3.staging.runway.gitlab.comci, staging, test | Not in the scope | 2026-11-14 |
| test-jm-proxy.runway.gitlab.comtest | Not in the scope | 2026-11-14 |
| cert-test.staging.gitlab.comstaging, test | Not in the scope | 2026-11-14 |
| test.gitlab.comtest | Not in the scope | 2026-11-14 |
| ws-test.gitter.imtest | Not in the scope | 2026-11-14 |
6 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.