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 |
|---|---|---|
| s3-hws-test2lan.chefblog.marriott.comdata, test | Not in the scope | 2026-11-14 |
| elevate-ftp2.tools.cloud.marriott.comdata | Not in the scope | 2026-11-14 |
| emp.hotel-ops-kafka-connector-dev.gxp.marriott.comdata, dev | Not in the scope | 2026-11-14 |
| sts-upload.marriott.comdata | Not in the scope | 2026-11-14 |
| sts-upload-service.marriott.comdata | Not in the scope | 2026-11-14 |
| kafka-jenkins.tools.marriott.comci, data | Not in the scope | 2026-11-14 |
| db.ritzcarlton.comdata | Listed out of scope | 2026-11-14 |
| sftp.starwoodhotels.comdata | 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-14.