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 |
|---|---|---|
| apigw-private-example.adev.scopely.ioapi, internal | In scope | 2026-11-14 |
| apigw-private-example-2.adev.scopely.ioapi, internal | In scope | 2026-11-14 |
| api.internal.use1.sat2.k8s.adev.scopely.ioapi, internal, tools | In scope | 2026-11-14 |
| apigw-private-example.private.adev.scopely.ioapi, internal | In scope | 2026-11-14 |
| apigw-private-example-2.private.adev.scopely.ioapi, internal | In scope | 2026-11-14 |
| changelog.private.adev.scopely.iointernal | In scope | 2026-11-14 |
| service-limit-api-gw-poc.private.adev.scopely.ioapi, internal | In scope | 2026-11-14 |
| 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 |
| internal-core.breadcrumbs.aprod.scopely.iointernal | In scope | 2026-11-14 |
| internal-dahtzee-data.breadcrumbs.aprod.scopely.iointernal | In scope | 2026-11-14 |
| internal-default-data.breadcrumbs.aprod.scopely.iointernal | In scope | 2026-11-14 |
| internal-scrabble-data.breadcrumbs.aprod.scopely.iointernal | In scope | 2026-11-14 |
| api.internal.use1.sat1.k8s.aprod.scopely.ioapi, internal, tools | In scope | 2026-11-14 |
| ranger-internal.warehouse.aprod.scopely.iointernal | In scope | 2026-11-14 |
| spark-internal.warehouse.aprod.scopely.iointernal | In scope | 2026-11-14 |
| intranet.scopely.iointernal | In scope | 2026-11-14 |
| event3-8internal.preview-collector.scopely.iointernal, staging | 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.