Bug bounty program
SB
SMTP2GO BBP
Most upvoted reports1
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Origin IP found, WAF Cloudflare BypassAnalysed#1536299 | No weakness recorded | 2022-05-15 | $100 | 53 |
Subdomains8,693
| Name | Scope | First seen |
|---|---|---|
| a1i213.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i214.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i215.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i216.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i217.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i218.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i219.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i22.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i220.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i221.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i222.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i223.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i224.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i225.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i226.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i227.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i228.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i229.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i23.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i230.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i231.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i232.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i233.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i234.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i235.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i236.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i237.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i238.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i239.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i24.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i240.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i241.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i242.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i243.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i244.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i245.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i246.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i247.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i248.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i249.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i25.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i250.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i251.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i252.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i253.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i254.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i255.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i256.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i257.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i258.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i259.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i26.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i260.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i261.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i262.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i263.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i264.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i265.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i266.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i267.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i268.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i269.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i27.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i270.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i271.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i272.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i273.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i274.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i275.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i276.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i277.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i278.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i279.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i28.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i280.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i281.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i282.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i283.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i284.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i285.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i286.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i287.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i288.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i289.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i29.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i290.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i291.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i292.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i293.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i294.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i295.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i296.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i297.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i298.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i299.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i30.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i300.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i301.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i302.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i303.smtp2go.com | Not in the scope | 2026-11-14 |
2 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.