Bug bounty program
Grindr
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 9
- Disclosed reports
- 0
- Subdomains
- 221
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains221
| Name | Scope | First seen |
|---|---|---|
| lite-test.grindr.comtest | In scope | 2026-11-14 |
| yass-test.grindr.comtest | In scope | 2026-11-14 |
| extra-test.grindr.comtest | In scope | 2026-11-14 |
| www.lite-test.grindr.comtest | In scope | 2026-11-14 |
| g3-beta-upload-test.grindr.comdata, staging, test | In scope | 2026-11-14 |
| test.grindr.iotest | In scope | 2026-11-14 |
| lite-qa.dev.grindr.iodev, test | In scope | 2026-11-14 |
| atlantis.test.grindr.iotest | In scope | 2026-11-14 |
212 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.