Bug bounty program
Upwork
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains452
| Name | Scope | First seen |
|---|---|---|
| auth.upwork.comauth | Not in the scope | 2026-11-14 |
| auth-ns.workspace.agate.upwork.comauth | Not in the scope | 2026-11-14 |
| teredo.auth-ns.workspace.agate.upwork.comauth | Not in the scope | 2026-11-14 |
| auth-ns.auth-ns.workspace.agate.upwork.comauth | Not in the scope | 2026-11-14 |
| covid19.auth-ns.workspace.agate.upwork.comauth | Not in the scope | 2026-11-14 |
| teredo.teredo.auth-ns.workspace.agate.upwork.comauth | Not in the scope | 2026-11-14 |
| covid19auth-ns.auth-ns.workspace.agate.upwork.comauth | Not in the scope | 2026-11-14 |
2 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-15.