Bug bounty program
Amazon Vulnerability Research Program
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains90,563
| Name | Scope | First seen |
|---|---|---|
| api.amazon.co.jpapi | In scope | 2026-11-14 |
| soap.amazon.co.jpapi | In scope | 2026-11-14 |
| a9g-api.amazon.co.jpapi | In scope | 2026-11-14 |
| api-key.amazon.co.jpapi | In scope | 2026-11-14 |
| ramp-api.amazon.co.jpapi | In scope | 2026-11-14 |
| gql.music.amazon.co.jpapi | In scope | 2026-11-14 |
| api-sandbox.amazon.co.jpapi, test | In scope | 2026-11-14 |
| api.sandbox.amazon.co.jpapi, test | In scope | 2026-11-14 |
| webservices.amazon.co.jpapi | In scope | 2026-11-14 |
| eu-api-alexa.amazon.co.jpapi | In scope | 2026-11-14 |
| fe-api-alexa.amazon.co.jpapi | In scope | 2026-11-14 |
| merchant-api.amazon.co.jpapi | In scope | 2026-11-14 |
| na-api-alexa.amazon.co.jpapi | In scope | 2026-11-14 |
| pinnacle-api.amazon.co.jpapi | In scope | 2026-11-14 |
| beta.gql.music.amazon.co.jpapi, staging | In scope | 2026-11-14 |
| eu-api-avs-idrs.amazon.co.jpapi | In scope | 2026-11-14 |
| fe-api-avs-idrs.amazon.co.jpapi | In scope | 2026-11-14 |
| na-api-avs-idrs.amazon.co.jpapi | In scope | 2026-11-14 |
| accesspoints-api.amazon.co.jpapi | In scope | 2026-11-14 |
| api-amazondevices.amazon.co.jpapi | In scope | 2026-11-14 |
| sha256.webservices.amazon.co.jpapi | In scope | 2026-11-14 |
| uswest-api.business.amazon.co.jpapi | In scope | 2026-11-14 |
| advertising-api-test.amazon.co.jpapi, test | In scope | 2026-11-14 |
| eu-south-2-api-alexa.amazon.co.jpapi | In scope | 2026-11-14 |
| hop-uswest-api.business.amazon.co.jpapi | In scope | 2026-11-14 |
| origin-accesspoints-api.amazon.co.jpapi | In scope | 2026-11-14 |
90,562 names are covered by the program's own scope; 2 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.