Bug bounty program
AV
AWS VDP
Most upvoted reports61
All reportsSubdomains3,037
| Name | Scope | First seen |
|---|---|---|
| mx-central-1.awsc-integ.aws.amazon.commail | In scope | 2026-11-14 |
| wildcard.mx-central-1.awsc-integ.aws.amazon.commail | In scope | 2026-11-14 |
| mx-central-1.awsc-preprod.aws.amazon.commail, staging | In scope | 2026-11-14 |
| wildcard.mx-central-1.awsc-preprod.aws.amazon.commail, staging | In scope | 2026-11-14 |
| mx-central-1.gamma.api.console.aws.amazon.comadmin, api, mail | In scope | 2026-11-14 |
| mx-central-1.api.console.aws.amazon.comadmin, api, mail | In scope | 2026-11-14 |
| mx-central-1.console.aws.amazon.comadmin, mail | In scope | 2026-11-14 |
| wildcard.mx-central-1.console.aws.amazon.comadmin, mail | In scope | 2026-11-14 |
| mx-central-1.lightsail-devo.aws.amazon.commail | In scope | 2026-11-14 |
| mx-central-1.lightsail-preprod.aws.amazon.commail, staging | In scope | 2026-11-14 |
| mx-central-1.lightsail.aws.amazon.commail | In scope | 2026-11-14 |
| mail.aws.amazon.commail | In scope | 2026-11-14 |
| kovid-mail.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| kovid-mail2.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| kovid-mx.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| owa.kovid.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| webmail.kovid.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| kovid.mail.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| mx-kovid.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| owa-kovid.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| kovid.webmail.signin.aws.amazon.comauth, mail | In scope | 2026-11-14 |
| webmail.aws.amazon.commail | In scope | 2026-11-14 |
3,036 names are covered by the program's own scope; 1 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.