Bug bounty program
SB
SMTP2GO BBP
Most upvoted reports1
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Origin IP found, WAF Cloudflare Bypass#1536299 | No weakness recorded | 2022-05-15 | $100 | 53 |
Subdomains8,693
| Name | Scope | First seen |
|---|---|---|
| db.smtp2go.comdata | Not in the scope | 2026-11-14 |
| ftp.smtp2go.comdata | Not in the scope | 2026-11-14 |
| mongo.smtp2go.comdata | Not in the scope | 2026-11-14 |
| mysql.smtp2go.comdata | Not in the scope | 2026-11-14 |
| upload.smtp2go.comdata | Not in the scope | 2026-11-14 |
| elastic.smtp2go.comdata | Not in the scope | 2026-11-14 |
| mongodb.smtp2go.comdata | Not in the scope | 2026-11-14 |
| ftp.a0i392.smtp2go.comdata | 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-14.