Bug bounty program
Amazon Vulnerability Research Program
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains90,561
| Name | Scope | First seen |
|---|---|---|
| api.amazon.caapi | In scope | 2026-11-14 |
| soap.amazon.caapi | In scope | 2026-11-14 |
| a9g-api.amazon.caapi | In scope | 2026-11-14 |
| api-key.amazon.caapi | In scope | 2026-11-14 |
| ramp-api.amazon.caapi | In scope | 2026-11-14 |
| gql.music.amazon.caapi | In scope | 2026-11-14 |
| api.social.amazon.caapi | In scope | 2026-11-14 |
| gaming-api.amazon.caapi | In scope | 2026-11-14 |
| webservices.amazon.caapi | In scope | 2026-11-14 |
| eu-api-alexa.amazon.caapi | In scope | 2026-11-14 |
| fe-api-alexa.amazon.caapi | In scope | 2026-11-14 |
| na-api-alexa.amazon.caapi | In scope | 2026-11-14 |
| pinnacle-api.amazon.caapi | In scope | 2026-11-14 |
| api.app.social.amazon.caapi | In scope | 2026-11-14 |
| beta.gql.music.amazon.caapi, staging | In scope | 2026-11-14 |
| eu-api-avs-idrs.amazon.caapi | In scope | 2026-11-14 |
| fe-api-avs-idrs.amazon.caapi | In scope | 2026-11-14 |
| na-api-avs-idrs.amazon.caapi | In scope | 2026-11-14 |
| api-amazondevices.amazon.caapi | In scope | 2026-11-14 |
| sha256.webservices.amazon.caapi | In scope | 2026-11-14 |
| useast-api.business.amazon.caapi | In scope | 2026-11-14 |
| eu-south-2-api-alexa.amazon.caapi | In scope | 2026-11-14 |
| sophap.beta.gql.music.amazon.caapi, staging | In scope | 2026-11-14 |
| egitelma.beta.gql.music.amazon.caapi, staging | In scope | 2026-11-14 |
| hop-useast-api.business.amazon.caapi | In scope | 2026-11-14 |
| gamma-apigateway-fips.us-east-1.amazon.caapi | In scope | 2026-11-14 |
90,560 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.