Subdomains of Amazon Vulnerability Research Program
Host names under public bug bounty programs' domains, from ProjectDiscovery's Chaos dataset. Search what the names suggest across every program, then open one program's names.
| Name | Scope | First seen |
|---|---|---|
| dev-business.amazon.caDevelopment | In scope | 2026-11-14 |
| dev.music.amazon.caDevelopment | In scope | 2026-11-14 |
| local.music.amazon.caDevelopment | In scope | 2026-11-14 |
| primenow-preprod-dev.amazon.caDevelopment, Staging | In scope | 2026-11-14 |
| dev.fe.s.advertising.amazon.cnDevelopment | In scope | 2026-11-14 |
| dev.hub.s.advertising.amazon.cnDevelopment | In scope | 2026-11-14 |
| dev.m.s.advertising.amazon.cnDevelopment | In scope | 2026-11-14 |
| dev.ma.s.advertising.amazon.cnDevelopment | In scope | 2026-11-14 |
| dev.static.s.advertising.amazon.cnDevelopment | In scope | 2026-11-14 |
| a.cdn.console-alpha.aws-dev.amazon.cnAdmin, Development, Staging | In scope | 2026-11-14 |
| turtle-bridge-cn-amazon-local.amazon.cnDevelopment | In scope | 2026-11-14 |
| wrcs.prod.waldo-dev.amazon.cnDevelopment | In scope | 2026-11-14 |
| dev-business.amazon.co.jpDevelopment | In scope | 2026-11-14 |
| dev.music.amazon.co.jpDevelopment | In scope | 2026-11-14 |
| local.music.amazon.co.jpDevelopment | In scope | 2026-11-14 |
| dev-business.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| local.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| local-mobile.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| local-sfis.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| local-sfis-integ.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| www.local.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| dev.music.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| local.music.amazon.co.ukDevelopment | In scope | 2026-11-14 |
| beacon.dev.studios.a2z.amazon.comDevelopment | In scope | 2026-11-14 |
| dev.assets.ads.amazon.comDevelopment | In scope | 2026-11-14 |
| eider-dev-corp.aea.amazon.comDevelopment, Internal | In scope | 2026-11-14 |
| aiv-eu-blr-dev.amazon.comDevelopment | In scope | 2026-11-14 |
| amazonfreight-hub-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| brdeveloper-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| cat-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| chime-opscon-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| choc-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| cortexweb-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| dev-dsk-dora.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| dev-dsk-sjye-starmap.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| development-shrub-us.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| dogfish-dev-brialiu.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| dogfish-dev-deenacs.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| dogfish-dev-wthompsn.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| dr-dre-aapi-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| ec2-cep-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| eink-dev-sonarqube-dashboard.aka.amazon.comAdmin, Development, Tools | In scope | 2026-11-14 |
| foundry-alpha-dev1.aka.amazon.comDevelopment, Staging | In scope | 2026-11-14 |
| foundry-alpha-dev2.aka.amazon.comDevelopment, Staging | In scope | 2026-11-14 |
| geminiportal-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| go-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| gouda-dashboard-dev.aka.amazon.comAdmin, Development | In scope | 2026-11-14 |
| idas-qotd-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| jam-gamma-iad-develop.aka.amazon.comDevelopment | In scope | 2026-11-14 |
| k4w-dev.aka.amazon.comDevelopment | In scope | 2026-11-14 |
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. Across programs the counts come from each program's index of name words and root domains, so a name with two matching words counts twice; scope and first-seen pick programs that have such names, and a program's own list applies them to every name. Source: ProjectDiscovery Chaos. Data as of 2026-11-15.