Bug bounty program
Scopely
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 24
- Disclosed reports
- 0
- Subdomains
- 3,670
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains3,670
| Name | Scope | First seen |
|---|---|---|
| test-2-service-limits.private.adev.scopely.iointernal, test | In scope | 2026-11-14 |
| test-service-limits.private.adev.scopely.iointernal, test | In scope | 2026-11-14 |
| test-2-service-limits.adev.scopely.iotest | In scope | 2026-11-14 |
| test-devops-oscar.adev.scopely.iotest | In scope | 2026-11-14 |
| test-mixed-openapi-gw.adev.scopely.ioapi, test | In scope | 2026-11-14 |
| test-player-profile-api-default.adev.scopely.ioapi, test | In scope | 2026-11-14 |
| test-raw-openapi-gw.adev.scopely.ioapi, test | In scope | 2026-11-14 |
| test-service-limits.adev.scopely.iotest | In scope | 2026-11-14 |
| 489a19fa-d8demo1-4954-858d-464demo6d5cdb20.event.collector.scopely.iotest | In scope | 2026-11-14 |
| perf.scopely.iotest | In scope | 2026-11-14 |
| staging.perf.scopely.iostaging, test | In scope | 2026-11-14 |
| sandbox.spinnaker.playgami.scopely.ioci, test | In scope | 2026-11-14 |
| sandbox-api.spinnaker.playgami.scopely.ioapi, ci, test | In scope | 2026-11-14 |
| test-devops-oscar.preview-collector.scopely.iostaging, test | In scope | 2026-11-14 |
| sandbox1.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
| sandbox2.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
| sandbox3.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
| sandbox4.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
| test.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
| test2.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
| test3.builds.tophat.scopely.ioci, test | In scope | 2026-11-14 |
3,667 names are covered by the program's own scope; 6 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-15.