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 |
|---|---|---|
| a1i304.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i305.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i306.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i307.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i308.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i309.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i31.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i310.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i311.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i312.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i313.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i314.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i315.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i316.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i317.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i318.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i319.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i32.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i320.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i321.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i322.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i323.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i324.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i325.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i326.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i327.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i328.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i329.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i33.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i330.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i331.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i332.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i333.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i334.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i335.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i336.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i337.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i338.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i339.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i34.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i340.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i341.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i342.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i343.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i344.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i345.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i346.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i347.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i348.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i349.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i35.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i350.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i351.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i352.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i353.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i354.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i355.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i356.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i357.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i358.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i359.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i36.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i360.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i361.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i362.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i363.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i364.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i365.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i366.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i367.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i368.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i369.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i37.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i370.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i371.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i372.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i373.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i374.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i375.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i376.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i377.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i378.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i379.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i38.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i380.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i381.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i382.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i383.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i384.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i385.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i386.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i387.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i388.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i389.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i39.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i390.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i391.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i392.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i393.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i394.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.