Bug bounty program
Optimizely
- Platform
- Bugcrowd
- Bounties
- Pays
- Assets in scope
- 15
- Disclosed reports
- 0
- Subdomains
- 14,957
- Vendor on CyberSIXT
- Optimizely (15 CVEs, 0 exploited)
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains14,957
| Name | Scope | First seen |
|---|---|---|
| metrics.app.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| metrics.cdn-pci.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| metrics.cdn.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| grafana-opentsdb.dz.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| monitoring.dz.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| api.exp-metrics.optimizely.comapi, monitoring | Not in the scope | 2026-11-14 |
| inte.api.exp-metrics.optimizely.comapi, monitoring | Not in the scope | 2026-11-14 |
| prep.api.exp-metrics.optimizely.comapi, monitoring | Not in the scope | 2026-11-14 |
| prod.api.exp-metrics.optimizely.comapi, monitoring | Not in the scope | 2026-11-14 |
| migrator.exp-metrics.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| inte.migrator.exp-metrics.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| prep.migrator.exp-metrics.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| ui.exp-metrics.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| inte.ui.exp-metrics.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| prep.ui.exp-metrics.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| kibana.prod.optimizely.commonitoring | Not in the scope | 2026-11-14 |
| status.optimizely.commonitoring | Not in the scope | 2026-11-14 |
6 names are covered by the program's own scope; 3 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.