Bug bounty program
LO
Logitech
Most upvoted reports15
All reportsSubdomains7,102
| Name | Scope | First seen |
|---|---|---|
| api.configurator.logitech.comapi | In scope | 2026-11-14 |
| wss-dev-api.dev.vc.logitech.comapi, dev | In scope | 2026-11-14 |
| wss-dev1-api.dev.vc.logitech.comapi, dev | In scope | 2026-11-14 |
| api-creatorcommunity.logitech.comapi | In scope | 2026-11-14 |
| api.create-your-space.logitech.comapi | In scope | 2026-11-14 |
| wss-stable-api.dev.vc.logitech.comapi, dev | In scope | 2026-11-14 |
| wss-sandbox-api.dev.vc.logitech.comapi, dev, test | In scope | 2026-11-14 |
| staging-api.configurator.logitech.comapi, staging | In scope | 2026-11-14 |
| wss-dev-api.dev.configurator.logitech.comapi, dev | 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.