Bug bounty program
Marriott Bug Bounty Program
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 59
- Disclosed reports
- 0
- Subdomains
- 5,220
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains5,220
| Name | Scope | First seen |
|---|---|---|
| artifactory-old.marriott.comlegacy, tools | Not in the scope | 2026-11-14 |
| dtr-old.tools.cloud.marriott.comlegacy | Not in the scope | 2026-11-14 |
| legacy.devowa.marriott.comlegacy | Not in the scope | 2026-11-14 |
| legacy.owa.marriott.comlegacy, mail | Not in the scope | 2026-11-14 |
| legacy.secmail.marriott.comlegacy | Not in the scope | 2026-11-14 |
| dev-legacy-1.shop.marriott.comdev, legacy | Not in the scope | 2026-11-14 |
| dev-legacy-2.shop.marriott.comdev, legacy | Not in the scope | 2026-11-14 |
| dev-legacy-3.shop.marriott.comdev, legacy | Not in the scope | 2026-11-14 |
97 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.