Bug bounty program
Jora
- Platform
- Bugcrowd
- Bounties
- Pays
- Assets in scope
- 4
- Disclosed reports
- 0
- Subdomains
- 114
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains114
| Name | Scope | First seen |
|---|---|---|
| local.jora.comdev | In scope | 2026-11-14 |
| dev-emp.jora.comdev | In scope | 2026-11-14 |
| assets-dev.jora.comdev | In scope | 2026-11-14 |
| dev-emp-next.jora.comdev | In scope | 2026-11-14 |
| dev-employer.jora.comdev | In scope | 2026-11-14 |
| o3708.e.local.jora.comdev | In scope | 2026-11-14 |
| api-dev.employer.jora.comapi, dev | In scope | 2026-11-14 |
| dev-employer-test.jora.comdev, test | In scope | 2026-11-14 |
| next-dev-employer.jora.comdev | In scope | 2026-11-14 |
| dev-employer-legacy.jora.comdev, legacy | In scope | 2026-11-14 |
| 2a57j784csm1uc4zjvs4osqlgg9azv4.dev-employer.jora.comdev | In scope | 2026-11-14 |
| dev-employer-admin.jora.xyzadmin, dev | In scope | 2026-11-14 |
114 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.