Bug bounty program
SoundCloud
- Platform
- Bugcrowd
- Bounties
- Pays
- Assets in scope
- 10
- Disclosed reports
- 0
- Subdomains
- 714
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains714
| Name | Scope | First seen |
|---|---|---|
| admin.repostnetwork.comadmin | Not in the scope | 2026-11-14 |
| dashboard.repostnetwork.comadmin | Not in the scope | 2026-11-14 |
| admin.soundcloud.comadmin | Not in the scope | 2026-11-14 |
| dashboard.soundcloud.comadmin | Not in the scope | 2026-11-14 |
| media.cms.soundcloud.comadmin | Not in the scope | 2026-11-14 |
| ar-dashboard.soundcloud.comadmin | Not in the scope | 2026-11-14 |
| ar-dashboard.l.soundcloud.comadmin | Not in the scope | 2026-11-14 |
| media.cms-test-dev.soundcloud.comadmin, dev, test | Not in the scope | 2026-11-14 |
| media.cms-test-staging.soundcloud.comadmin, staging, test | Not in the scope | 2026-11-14 |
343 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-15.