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 |
|---|---|---|
| a1i123.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i124.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i125.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i126.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i127.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i128.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i129.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i13.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i130.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i131.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i132.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i133.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i134.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i135.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i136.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i137.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i138.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i139.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i14.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i140.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i141.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i142.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i143.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i144.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i145.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i146.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i147.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i148.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i149.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i15.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i150.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i151.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i152.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i153.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i154.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i155.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i156.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i157.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i158.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i159.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i16.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i160.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i161.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i162.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i163.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i164.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i165.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i166.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i167.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i168.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i169.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i17.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i170.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i171.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i172.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i173.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i174.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i175.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i176.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i177.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i178.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i179.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i18.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i180.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i181.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i182.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i183.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i184.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i185.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i186.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i187.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i188.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i189.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i19.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i190.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i191.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i192.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i193.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i194.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i195.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i196.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i197.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i198.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i199.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i2.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i20.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i200.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i201.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i202.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i203.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i204.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i205.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i206.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i207.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i208.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i209.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i21.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i210.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i211.smtp2go.com | Not in the scope | 2026-11-14 |
| a1i212.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.