Skip to content

Bug bounty program

Platform
HackerOne
Bounties
None
Assets in scope
17
Disclosed reports
0
Subdomains
118

Most upvoted reports0

No report of this program is publicly disclosed

Subdomains118

Subdomains of Ro
NameScopeFirst seen
api-origin.myplenity.comapiIn scope2026-11-14
api-origin-uat.myplenity.comapi, testIn scope2026-11-14
beta.myplenity.comstagingIn scope2026-11-14
dev.myplenity.comdevIn scope2026-11-14
get.myplenity.comIn scope2026-11-14
hcp.myplenity.comIn scope2026-11-14
click.hcp.myplenity.comIn scope2026-11-14
cloud.hcp.myplenity.comIn scope2026-11-14
image.hcp.myplenity.comIn scope2026-11-14
mta.hcp.myplenity.comIn scope2026-11-14
view.hcp.myplenity.comIn scope2026-11-14
local.myplenity.comdevIn scope2026-11-14
origin.myplenity.comIn scope2026-11-14
preprod.myplenity.comstagingIn scope2026-11-14
registration-hcp.myplenity.comIn scope2026-11-14
ssc.myplenity.comIn scope2026-11-14
www.myplenity.comIn scope2026-11-14

64 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.