Bug bounty program
LO
Logitech
Most upvoted reports15
All reportsSubdomains7,102
| Name | Scope | First seen |
|---|---|---|
| dev.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev01.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev02.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev03.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev04.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev05.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev06.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev07.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev08.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev09.astrogaming.comdev | Not in the scope | 2026-11-14 |
| dev10.astrogaming.comdev | Not in the scope | 2026-11-14 |
| development.astrogaming.comdev | Not in the 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.