Bug bounty program
Lime
- Platform
- Bugcrowd
- Bounties
- Pays
- Assets in scope
- 20
- Disclosed reports
- 0
- Subdomains
- 173
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains173
| Name | Scope | First seen |
|---|---|---|
| www.li.me | In scope | 2026-11-14 |
| admintool.lime.bike | In scope | 2026-11-14 |
| data.lime.bike | In scope | 2026-11-14 |
| external-api.lime.bikeapi | In scope | 2026-11-14 |
| gpt.lime.bike | In scope | 2026-11-14 |
| help.lime.bike | In scope | 2026-11-14 |
| juicer.lime.bike | In scope | 2026-11-14 |
| lp.lime.bike | In scope | 2026-11-14 |
| ops.lime.bike | In scope | 2026-11-14 |
| proxy-production.lime.bike | In scope | 2026-11-14 |
| web-production.lime.bike | In scope | 2026-11-14 |
| data.limeinternal.com | In scope | 2026-11-14 |
| orchard.limeinternal.com | In scope | 2026-11-14 |
13 names are covered by the program's own scope; 1 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.