Website & app testing · source-based site guide

HackerOne logo

Is HackerOne a good fit for you?

Advanced security research through authorised vulnerability programmes. Bounties depend on valid, eligible findings and the programme’s award decision, not time spent testing.

Offer a skillOfficial programme found

By FunSurveys editorial team · Sources checked 1 Nov 2026 · Guide expanded 1 Nov 2026
We reviewed public documentation. We did not open an account, complete assignments or test withdrawals.

Visit official site ↗

Official domain: hackerone.com · No referral parameters added.

Illustration of a person giving spoken feedback while testing a mobile app
AI-generated illustration of website & app testing; not a provider screenshot or evidence of earnings.

Who it may suit

Experienced security researchers who can interpret written programme scope and submit clear, responsible reports.

The trade-off to consider

Duplicate, out-of-scope or non-rewarded reports can earn nothing. This work requires specialist skills and should not be treated as a predictable stream of simple app tests.

Fees & deductions

A universal all-in researcher fee schedule was not established from the reviewed pages. Receiving-provider charges and the time spent on unrewarded research still affect the result.

How payment works

The payment guide documents PayPal and bank-transfer options, subject to setup and local conditions. Identity verification and required tax information precede reward payment.

Minimum & timing

The payment-preferences guide describes no PayPal payout minimum, with different conditions for other methods. An advertised bounty range is not a guaranteed award or a withdrawal threshold.

Who can apply

Bug bounty submission and reward eligibility require current identity verification under the reviewed guide. Each programme’s written scope, rules and reward terms independently apply.

A practical guide to HackerOne

Our interpretation of the linked provider documentation, with steps to help you assess the fit. These are not results from account testing.

Read the written authorisation before any testing

A public company name or a platform account is not blanket permission to test every service that company operates. Use the specific programme’s authorised assets and rules, and stop when the scope is unclear. Our recommendation is to develop skills in approved training environments before considering live programmes. This directory entry describes an earning model, not permission to perform security testing.

Evaluate paid findings rather than hours at the keyboard

A technically interesting report can still be a duplicate, outside scope or ineligible for a bounty. Read the award rules and keep programme communications private as required. Complete identity and payment setup through official settings. Track all research time and only record money as received after an actual award and transfer, rather than multiplying a published bounty range into expected weekly income.

Common questions about HackerOne

Is every valid report paid?

No guaranteed award was established. Programme rules, duplicates, eligibility and the owner’s decision affect whether a report receives a bounty.

Is the displayed bounty range my cash-out minimum?

No. An award range and a receiving method’s payout conditions are different. Check the actual award and current payment settings.

Official sources you can check

  1. Researcher payment setup and method-specific conditions ↗
    Documentation checked 1 Nov 2026.
  2. Current identity-verification requirements ↗
    Documentation checked 1 Nov 2026.
  3. How programme owners decide bounty awards ↗
    Documentation checked 1 Nov 2026.

Provider terms can change. A published programme does not establish current task supply, admission or payout health.

Send a correction or a newer source →

Compare other website & app testing options

BetaTesting logo

BetaTesting

Join a research and product-testing panel for software, games and other projects. Apply to suitable invitations and complete the agreed activities for review.

Read the site guide →
Bugcrowd logo

Bugcrowd

Participate in authorised security research programmes and report eligible vulnerabilities. Rewards depend on programme rules, findings and review rather than fixed working hours.

Read the site guide →
PlaytestCloud logo

PlaytestCloud

Give recorded feedback on games through invited playtests. Device-specific onboarding and the reward in each invitation matter more than general play-to-earn advertising.

Read the site guide →

Explore the website & app testing guide →