Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
3
Disclosed reports
1
Subdomains
8,693
Vendor on CyberSIXT
SMTP2GO (3 CVEs, 0 exploited)

Most upvoted reports1

Most upvoted reports of SMTP2GO BBP
ReportWeaknessDisclosedBountyVotes
Origin IP found, WAF Cloudflare BypassAnalysed#1536299No weakness recorded2022-05-15$10053

Subdomains8,693

Subdomains of SMTP2GO BBP
NameScopeFirst seen
mx.smtp2go.commailNot in the scope2026-11-14
owa.smtp2go.commailNot in the scope2026-11-14
imap.smtp2go.commailNot in the scope2026-11-14
mail.smtp2go.commailNot in the scope2026-11-14
pop3.smtp2go.commailNot in the scope2026-11-14
smtp.smtp2go.commailNot in the scope2026-11-14
mail1.smtp2go.commailNot in the scope2026-11-14
mail2.smtp2go.commailNot in the scope2026-11-14
40mail.smtp2go.commailNot in the scope2026-11-14
mail-eu.smtp2go.commailNot in the scope2026-11-14
webmail.smtp2go.commailNot in the scope2026-11-14
exchange.smtp2go.commailNot in the scope2026-11-14
mail-in1.smtp2go.commailNot in the scope2026-11-14
mail-in2.smtp2go.commailNot in the scope2026-11-14
mail-in3.smtp2go.commailNot in the scope2026-11-14
mail-in4.smtp2go.commailNot in the scope2026-11-14
mail-in5.smtp2go.commailNot in the scope2026-11-14
mail-in6.smtp2go.commailNot in the scope2026-11-14
mail-in7.smtp2go.commailNot in the scope2026-11-14
mail-in8.smtp2go.commailNot in the scope2026-11-14
mail-in9.smtp2go.commailNot in the scope2026-11-14
old-mail.smtp2go.comlegacy, mailNot in the scope2026-11-14
alt.mail4.smtp2go.commailNot in the scope2026-11-14
mail-in10.smtp2go.commailNot in the scope2026-11-14
mail-in11.smtp2go.commailNot in the scope2026-11-14
mail-in12.smtp2go.commailNot in the scope2026-11-14
mail-in13.smtp2go.commailNot in the scope2026-11-14
mail-in14.smtp2go.commailNot in the scope2026-11-14
mail-in22.smtp2go.commailNot in the scope2026-11-14
mail-in23.smtp2go.commailNot in the scope2026-11-14
autodiscover.smtp2go.commailNot in the scope2026-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.