Bug bounty program
UB
Uber
Most upvoted reports239
All reportsSubdomains11,395
| Name | Scope | First seen |
|---|---|---|
| api.uber.comapi | Not in the scope | 2026-11-14 |
| api-an-settlement.uber.comapi | Not in the scope | 2026-11-14 |
| api-asterisk.uber.comapi | Not in the scope | 2026-11-14 |
| api-influencer.uber.comapi | Not in the scope | 2026-11-14 |
| api-maps.uber.comapi | Not in the scope | 2026-11-14 |
| api-sandbox.uber.comapi, test | Not in the scope | 2026-11-14 |
| api-staging.uber.comapi, staging | Not in the scope | 2026-11-14 |
| api1.uber.comapi | Not in the scope | 2026-11-14 |
| api2.uber.comapi | Not in the scope | 2026-11-14 |
| api3.uber.comapi | Not in the scope | 2026-11-14 |
| cpg-api-19208a97.uber.comapi | Not in the scope | 2026-11-14 |
| cpg-api-b27c7352.uber.comapi | Not in the scope | 2026-11-14 |
| cpg-api-ef83c3b4.uber.comapi | Not in the scope | 2026-11-14 |
| cpg-api-staging-95a6cbf0.uber.comapi, staging | Not in the scope | 2026-11-14 |
| api.delivery.uber.comapi | Not in the scope | 2026-11-14 |
| api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| api-dashboard.dev.uber.comadmin, api, dev | Not in the scope | 2026-11-14 |
| api-mez.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| api-sim.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| api-weiwang.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| hqdeng-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| api.hummer-insight-3.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| jian-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| jlu-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| mu-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| mu-api2.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| mu-api3.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| full-api1.rue.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| shamim-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| sim-server-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| sweeney-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| sweeney-api2.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| sweeney-api3.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| the-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| tiffanyc-api.dev.uber.comapi, dev | Not in the scope | 2026-11-14 |
| web-riders-test-api.dev.uber.comapi, dev, test | Not in the scope | 2026-11-14 |
| grpc-test.uber.comapi, test | Not in the scope | 2026-11-14 |
| api.helix-go-webview.uber.comapi | Not in the scope | 2026-11-14 |
| api.help.uber.comapi | Not in the scope | 2026-11-14 |
| kiosk-api.uber.comapi | Not in the scope | 2026-11-14 |
| kiosk-node-api-staging.uber.comapi, staging | Not in the scope | 2026-11-14 |
| metro-api.uber.comapi | Not in the scope | 2026-11-14 |
| sandbox-api.uber.comapi, test | Not in the scope | 2026-11-14 |
| sandbox-api-staging.uber.comapi, staging, test | Not in the scope | 2026-11-14 |
| sandbox-api-v2.uber.comapi, test | Not in the scope | 2026-11-14 |
| api01.syd1.uber.comapi | Not in the scope | 2026-11-14 |
| pre-api01.syd1.uber.comapi | Not in the scope | 2026-11-14 |
| test-api.uber.comapi, test | Not in the scope | 2026-11-14 |
| uas-api.uber.comapi | Not in the scope | 2026-11-14 |
| uview-node-api.uber.comapi | Not in the scope | 2026-11-14 |
| video-support-api-staging.uber.comapi, staging | Not in the scope | 2026-11-14 |
| vip-internal-api.uber.comapi, internal | Not in the scope | 2026-11-14 |
| vip-internal-api-staging.uber.comapi, internal, staging | Not in the scope | 2026-11-14 |
| web-restaurant-graphql.uber.comapi | Not in the scope | 2026-11-14 |
0 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.