Bug bounty program
Scopely
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 24
- Disclosed reports
- 0
- Subdomains
- 3,664
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains3,664
| Name | Scope | First seen |
|---|---|---|
| dev.b.scopely.iodev | In scope | 2026-11-14 |
| dev-titan.b.scopely.iodev | In scope | 2026-11-14 |
| event-27-dev1.collector.scopely.iodev | In scope | 2026-11-14 |
| dev.scopely.iodev | In scope | 2026-11-14 |
| dev-bamboo.scopely.ioci, dev | In scope | 2026-11-14 |
| dev-confluence.scopely.iodev, tools | In scope | 2026-11-14 |
| dev-jira.scopely.iodev, tools | In scope | 2026-11-14 |
| bigboss.dev.scopely.iodev | In scope | 2026-11-14 |
| devpi.dev.scopely.iodev | In scope | 2026-11-14 |
| kinesis.dev.scopely.iodev | In scope | 2026-11-14 |
| logs.dev.scopely.iodev, monitoring | In scope | 2026-11-14 |
| logstash.dev.scopely.iodev | In scope | 2026-11-14 |
| pokemon.dev.scopely.iodev | In scope | 2026-11-14 |
| scheduler.dev.scopely.iodev | In scope | 2026-11-14 |
| sumo.dev.scopely.iodev | In scope | 2026-11-14 |
| artflow-dev.games.scopely.iodev | In scope | 2026-11-14 |
| dev.hyperion.scopely.iodev | In scope | 2026-11-14 |
| origin-dev-jira.scopely.iodev, tools | In scope | 2026-11-14 |
| dev.aiapi.tophat.scopely.iodev | In scope | 2026-11-14 |
| dev-ecs.aiapi.tophat.scopely.iodev | In scope | 2026-11-14 |
| dev.builds.tophat.scopely.ioci, dev | In scope | 2026-11-14 |
| develop.builds.tophat.scopely.ioci, dev | In scope | 2026-11-14 |
| cache.unity-accelerator.develop.builds.tophat.scopely.ioci, dev | In scope | 2026-11-14 |
| dev.peg-e.tophat.scopely.iodev | In scope | 2026-11-14 |
| quick-env.dev.peg-e.tophat.scopely.iodev | In scope | 2026-11-14 |
| dev.rm.tophat.scopely.iodev | In scope | 2026-11-14 |
| build-development-dashboard.unity-accelerator.tophat.scopely.ioadmin, ci, dev | In scope | 2026-11-14 |
| yellowjacket-dev.y.scopely.iodev | In scope | 2026-11-14 |
3,661 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.