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 |
|---|---|---|
| mobile-config.testnet.services.bitmex.com | In scope | 2026-11-14 |
| open.testnet.services.bitmex.com | In scope | 2026-11-14 |
| fbnotify.open.testnet.services.bitmex.com | In scope | 2026-11-14 |
| fbnotify.public.testnet.services.bitmex.com | In scope | 2026-11-14 |
| rescue.testnet.services.bitmex.com | In scope | 2026-11-14 |
| support.rescue.testnet.services.bitmex.com | In scope | 2026-11-14 |
| ws.rescue.testnet.services.bitmex.com | In scope | 2026-11-14 |
| www.rescue.testnet.services.bitmex.com | In scope | 2026-11-14 |
| sentry.testnet.services.bitmex.commonitoring | In scope | 2026-11-14 |
| support.testnet.services.bitmex.com | In scope | 2026-11-14 |
| vasp.testnet.services.bitmex.com | In scope | 2026-11-14 |
| wildcard.testnet.services.bitmex.com | In scope | 2026-11-14 |
| ws.testnet.services.bitmex.com | In scope | 2026-11-14 |
| aws.ws-eks.testnet.services.bitmex.com | In scope | 2026-11-14 |
| cf.ws-eks.testnet.services.bitmex.com | In scope | 2026-11-14 |
| aws.ws.testnet.services.bitmex.com | In scope | 2026-11-14 |
| cf.ws.testnet.services.bitmex.com | In scope | 2026-11-14 |
| www.testnet.services.bitmex.com | In scope | 2026-11-14 |
| token.services.bitmex.com | In scope | 2026-11-14 |
| vasp.services.bitmex.com | In scope | 2026-11-14 |
| ws.services.bitmex.com | In scope | 2026-11-14 |
| aws.ws.services.bitmex.com | In scope | 2026-11-14 |
| cf.ws.services.bitmex.com | In scope | 2026-11-14 |
| www.services.bitmex.com | In scope | 2026-11-14 |
| static.bitmex.com | In scope | 2026-11-14 |
| status.bitmex.commonitoring | Listed out of scope | 2026-11-14 |
| status-test.bitmex.commonitoring, test | In scope | 2026-11-14 |
| www.status.bitmex.commonitoring | In scope | 2026-11-14 |
| support.bitmex.com | Listed out of scope | 2026-11-14 |
| testnet.bitmex.com | In scope | 2026-11-14 |
| testnet-dev.bitmex.comdev | In scope | 2026-11-14 |
| testnet-dtc.bitmex.com | In scope | 2026-11-14 |
| testnet-internal.bitmex.cominternal | In scope | 2026-11-14 |
| testnet-static.bitmex.com | In scope | 2026-11-14 |
| account-closure.testnet.bitmex.com | In scope | 2026-11-14 |
| api.testnet.bitmex.comapi | In scope | 2026-11-14 |
| auth.testnet.bitmex.comauth | In scope | 2026-11-14 |
| direct.testnet.bitmex.com | In scope | 2026-11-14 |
| api.direct.testnet.bitmex.comapi | In scope | 2026-11-14 |
| documents.testnet.bitmex.com | In scope | 2026-11-14 |
| fix.testnet.bitmex.com | In scope | 2026-11-14 |
| l.m.testnet.bitmex.com | In scope | 2026-11-14 |
| onfido.testnet.bitmex.com | In scope | 2026-11-14 |
| eu.onfido.testnet.bitmex.com | In scope | 2026-11-14 |
| privatelink.testnet.bitmex.com | In scope | 2026-11-14 |
| static.testnet.bitmex.com | In scope | 2026-11-14 |
| support.testnet.bitmex.com | In scope | 2026-11-14 |
| trading-view.testnet.bitmex.com | In scope | 2026-11-14 |
| trading-view-gateway.testnet.bitmex.com | In scope | 2026-11-14 |
| upload.testnet.bitmex.comdata | In scope | 2026-11-14 |
| vasp.testnet.bitmex.com | In scope | 2026-11-14 |
| web-ws.testnet.bitmex.com | In scope | 2026-11-14 |
| wechat.testnet.bitmex.com | In scope | 2026-11-14 |
| ws.testnet.bitmex.com | In scope | 2026-11-14 |
| open.ws-services.testnet.bitmex.com | In scope | 2026-11-14 |
| wildcard.open.ws-services.testnet.bitmex.com | In scope | 2026-11-14 |
| trading-view.ws-services.testnet.bitmex.com | In scope | 2026-11-14 |
| web.ws-services.testnet.bitmex.com | In scope | 2026-11-14 |
| www.testnet.bitmex.com | In scope | 2026-11-14 |
| testnet2.bitmex.com | In scope | 2026-11-14 |
| theinternetmarketingmaven.bitmex.com | In scope | 2026-11-14 |
| token.bitmex.com | In scope | 2026-11-14 |
| trade.bitmex.com | In scope | 2026-11-14 |
| trading-view.bitmex.com | In scope | 2026-11-14 |
| trading-view-gateway.bitmex.com | In scope | 2026-11-14 |
| ts.bitmex.com | In scope | 2026-11-14 |
| u003eblog.bitmex.com | In scope | 2026-11-14 |
| u003ewww.bitmex.com | In scope | 2026-11-14 |
| upload.bitmex.comdata | In scope | 2026-11-14 |
| vasp.bitmex.com | In scope | 2026-11-14 |
| video.bitmex.com | In scope | 2026-11-14 |
| webmail.videomarketing.bitmex.commail | In scope | 2026-11-14 |
| w3.bitmex.com | In scope | 2026-11-14 |
| web-ws.bitmex.com | In scope | 2026-11-14 |
| whosonleave.bitmex.com | In scope | 2026-11-14 |
| ws.bitmex.com | In scope | 2026-11-14 |
| direct.ws-services.bitmex.com | In scope | 2026-11-14 |
| trading-view.ws-services.bitmex.com | In scope | 2026-11-14 |
| web.ws-services.bitmex.com | In scope | 2026-11-14 |
| ww.bitmex.com | In scope | 2026-11-14 |
| www.bitmex.com | In scope | 2026-11-14 |
| www2.bitmex.com | In scope | 2026-11-14 |
| xcoajvlkty.bitmex.com | In scope | 2026-11-14 |
| znc-internal.bitmex.cominternal | 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-15.