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 |
|---|---|---|
| consul.dev2.grindr.iodev, tools | In scope | 2026-11-14 |
| consul.prod2.grindr.iotools | In scope | 2026-11-14 |
| superset.dsci.grindr.iotools | In scope | 2026-11-14 |
| admin-k8s.prod.grindr.ioadmin, tools | In scope | 2026-11-14 |
| consul.uw2-prod2.grindr.iotools | In scope | 2026-11-14 |
| superset-new.dsci.grindr.iotools | In scope | 2026-11-14 |
| k8s-jenkins-abc.prod.grindr.ioci, tools | In scope | 2026-11-14 |
| airflow-beta-master.dsci.grindr.iostaging, tools | In scope | 2026-11-14 |
| jira-triage-agent.security.grindr.iotools | In scope | 2026-11-14 |
| superset-newpresence-direct-cf.dsci.grindr.iotools | 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-15.