Bug bounty program
LO
Logitech
Most upvoted reports15
All reportsSubdomains7,102
| Name | Scope | First seen |
|---|---|---|
| metrics.astrogaming.commonitoring | Not in the scope | 2026-11-14 |
| status.challonge.commonitoring | Not in the scope | 2026-11-14 |
| prometheus-lan.challonge.commonitoring | Not in the scope | 2026-11-14 |
| grafana.dev.mlops.logi.comdev, monitoring | In scope | 2026-11-14 |
| kibana-eu.logs.cto.logi.commonitoring | In scope | 2026-11-14 |
| opensearch.logs.cto.logi.commonitoring | In scope | 2026-11-14 |
| grafana-dev.dev.mlops.logi.comdev, monitoring | In scope | 2026-11-14 |
| redash-monitoring.cto.logi.commonitoring, tools | In scope | 2026-11-14 |
| opensearch-eu.logs.cto.logi.commonitoring | In scope | 2026-11-14 |
| splunk.logitech.commonitoring | In scope | 2026-11-14 |
| status.logitech.commonitoring | In scope | 2026-11-14 |
| prometheus.logitech.commonitoring | In scope | 2026-11-14 |
| opensearch-logs.logitech.commonitoring | In scope | 2026-11-14 |
| status-escalations.vc.logitech.commonitoring | In scope | 2026-11-14 |
| grafana.dcg.logitech.iomonitoring | In scope | 2026-11-14 |
| prometheus.cmp.logitech.iomonitoring | In scope | 2026-11-14 |
| prometheus.dcg.logitech.iomonitoring | In scope | 2026-11-14 |
| alertmanager.dcg.logitech.iomonitoring | In scope | 2026-11-14 |
| prometheus.devops.logitech.iomonitoring | In scope | 2026-11-14 |
| logs-relay-ext.devops.logitech.iomonitoring | In scope | 2026-11-14 |
| grafana-datacatalog.np.logitech.iomonitoring | In scope | 2026-11-14 |
| opensearch-logs.devops.logitech.iomonitoring | In scope | 2026-11-14 |
| prometheus-datacatalog.np.logitech.iomonitoring | In scope | 2026-11-14 |
| alertmanager-datacatalog.np.logitech.iomonitoring | In scope | 2026-11-14 |
| logging.dhg.myharmony.commonitoring | In scope | 2026-11-14 |
| status.streamlabs.commonitoring | In scope | 2026-11-14 |
1,405 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.