Skip to content

Bug bounty program

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

Subdomains of Scopely
NameScopeFirst seen
apigw-affinity-limits-example-tophat.adev.scopely.ioapiIn scope2026-11-14
apigw-complete-public-satellite-example.adev.scopely.ioapiIn scope2026-11-14
apigw-existing-vpclink-example.adev.scopely.ioapiIn scope2026-11-14
apigw-private-example.adev.scopely.ioapi, internalIn scope2026-11-14
apigw-private-example-2.adev.scopely.ioapi, internalIn scope2026-11-14
apigw-service-limits-example.adev.scopely.ioapiIn scope2026-11-14
console-api-gw-poc.adev.scopely.ioadmin, apiIn scope2026-11-14
api.use1.sat2.k8s.adev.scopely.ioapi, toolsIn scope2026-11-14
api.internal.use1.sat2.k8s.adev.scopely.ioapi, internal, toolsIn scope2026-11-14
playgami-ai-api.adev.scopely.ioapiIn scope2026-11-14
apigw-private-example.private.adev.scopely.ioapi, internalIn scope2026-11-14
apigw-private-example-2.private.adev.scopely.ioapi, internalIn scope2026-11-14
service-limit-api-gw-poc.private.adev.scopely.ioapi, internalIn scope2026-11-14
service-limit-api-gw-poc.adev.scopely.ioapiIn scope2026-11-14
service-limit-api-gw-poc-2.adev.scopely.ioapiIn scope2026-11-14
simple-apigw-example.adev.scopely.ioapiIn scope2026-11-14
test-mixed-openapi-gw.adev.scopely.ioapi, testIn scope2026-11-14
test-player-profile-api-default.adev.scopely.ioapi, testIn scope2026-11-14
test-raw-openapi-gw.adev.scopely.ioapi, testIn scope2026-11-14
api.use1.sat1.k8s.aprod.scopely.ioapi, toolsIn scope2026-11-14
api.internal.use1.sat1.k8s.aprod.scopely.ioapi, internal, toolsIn scope2026-11-14
playgami-ai-api.aprod.scopely.ioapiIn scope2026-11-14
prod-api.spinnaker.playgami.scopely.ioapi, ciIn scope2026-11-14
sandbox-api.spinnaker.playgami.scopely.ioapi, ci, testIn scope2026-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.

Updated AboutDevelopersSign in