Bug bounty program
BitMEX
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 4
- Disclosed reports
- 0
- Subdomains
- 284
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains284
| Name | Scope | First seen |
|---|---|---|
| api.direct.bitmex.comapi | In scope | 2026-11-14 |
| api.testnet.bitmex.comapi | In scope | 2026-11-14 |
| api2.direct.bitmex.comapi | In scope | 2026-11-14 |
| api.analytics.bitmex.comapi | In scope | 2026-11-14 |
| api.devhk.direct.bitmex.comapi | In scope | 2026-11-14 |
| api.direct.devhk.bitmex.comapi | In scope | 2026-11-14 |
| api2.devhk.direct.bitmex.comapi | In scope | 2026-11-14 |
| api.devhk.services.bitmex.comapi | In scope | 2026-11-14 |
| api.direct.testnet.bitmex.comapi | In scope | 2026-11-14 |
| api.testnet.direct.bitmex.comapi | In scope | 2026-11-14 |
| api2.testnet.direct.bitmex.comapi | In scope | 2026-11-14 |
276 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.