Work at SMTP2GO BBP? Claim it to respond to reviews as the verified owner.
Found a vulnerability?
If you would rather not deal with the vendor yourself, a BugRater analyst will submit it upstream on your behalf, with your explicit permission, and tell you what came back.
Ask BugRater to submit itPrivate. The report body is encrypted at rest; BugRater holds the key, so the analyst working it can read it. Every read is logged.
HackerOne’s own figures for this program, read from its public page, not reported by researchers and not part of the BugRater grade. Captured 22 Sep 2026.
What it pays, by severity
$92,350 paid to researchers in total, $8,900 of it in the last 90 days. Lifetime figure as HackerOne prints it: evidence this program has paid, not a promise about any one report.
Intake & responsiveness · last 90 days
Response targets it sets itself
A target the program declared, not a measurement of it being met.
Getting in the door
Open to submit. Nothing HackerOne publishes stands between a hunter and a first report here.
Over 31 days (17 snapshots): intake down 13 reports; response efficiency down 3 points; 90-day payout down $1,000.
See how this programme’s report load compares to others →
Reviews
0 publishedNo reviews yet.
Who this program credits
87 creditedResearchers HackerOne shows on this program’s public thanks list, best position first. “Recognised” is how many of a hunter’s submissions the program accepted; the ratio is their signal here, not our judgement of them.
| # | Researcher | Reputation | Recognised / submitted |
|---|---|---|---|
| 1 | xploiterr | 3,407 | 119 / 173 69% |
| 2 | iamaby | 1,245 | 38 / 66 58% |
| 3 | rook1337 | 581 | 18 / 25 72% |
| 4 | a_elsawy | 580 | 25 / 95 26% |
| 5 | sezo | 330 | 9 / 20 45% |
| 6 | exploitguru101 | 242 | 6 / 12 50% |
| 7 | quain | 158 | 5 / 11 45% |
| 8 | a_saqr | 154 | 5 / 20 25% |
| 9 | unknownb1bokua | 120 | 5 / 7 71% |
| 9 | b9c8852a88912ed37baee1b | 24 | 1 / 1 100% |
| 10 | codexabhi1 | 106 | 4 / 17 24% |
| 11 | 0xdevsec | 102 | 3 / 4 75% |
| 12 | praveenarshoxxo | 89 | 3 / 5 60% |
| 13 | bad_script3r | 71 | 3 / 4 75% |
| 14 | w2w | 68 | 2 / 2 100% |
| 15 | tess | 61 | 1 / 1 100% |
| 16 | car68 | 59 | 1 / 1 100% |
| 16 | dontcrylabs | 59 | 1 / 1 100% |
| 16 | savitar0x01 | 59 | 1 / 3 33% |
| 18 | boda7x | 58 | 2 / 3 67% |
| 19 | pt200 | 57 | 1 / 1 100% |
| 20 | n1had | 53 | 2 / 7 29% |
| 21 | clight | 50 | 2 / 8 25% |
| 22 | whocallme | 49 | 1 / 3 33% |
| 23 | aqhmal | 48 | 2 / 3 67% |
Showing the top 25 of 87 credited on HackerOne.
Facts published by HackerOne on the program's own page, not reported by researchers, and not part of the BugRater grade. Last checked 16 Sep 2026.
Scope
4 assets| Asset | Type | Eligibility | Max severity |
|---|---|---|---|
| api.smtp2go.com | URL | ✓ bounty | Critical |
| app.smtp2go.com | URL | ✓ bounty | Critical |
| smtp2go.com | URL | ✓ bounty | Critical |
| support.smtp2go.com | URL | out | None |