Skip to content

Bug bounty program

PB

PlanetHoster Bug Bounty

Platform
Bugcrowd
Bounties
Pays
Assets in scope
5
Disclosed reports
0
Subdomains
17,024

Most upvoted reports0

No report of this program is publicly disclosed

Subdomains17,024

Subdomains of PlanetHoster Bug Bounty
NameScopeFirst seen
dev.forums.planethoster.comdevNot in the scope2026-11-14
www.dev.forums.planethoster.comdevNot in the scope2026-11-14
dev.planethoster.netdevNot in the scope2026-11-14
dev1.planethoster.netdevNot in the scope2026-11-14
www.dev1.planethoster.netdevNot in the scope2026-11-14
dev2.planethoster.netdevNot in the scope2026-11-14
www.dev2.planethoster.netdevNot in the scope2026-11-14
dev3.planethoster.netdevNot in the scope2026-11-14
dev4.ca.ns.planethoster.netdevNot in the scope2026-11-14
dev4-1.ca.ns.planethoster.netdevNot in the scope2026-11-14
www.dev4.ca.ns.planethoster.netdevNot in the scope2026-11-14
staging-dev.ca.ns.planethoster.netdev, stagingNot in the scope2026-11-14
www.staging-dev.ca.ns.planethoster.netdev, stagingNot in the scope2026-11-14

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