Skip to content

Bug bounty program

OP

Opera Public Bug Bounty

Platform
Bugcrowd
Bounties
Pays
Assets in scope
89
Disclosed reports
0
Subdomains
4,997
Vendor on CyberSIXT
Opera (311 CVEs, 0 exploited)

Most upvoted reports0

No report of this program is publicly disclosed

Subdomains4,997

Subdomains of Opera Public Bug Bounty
NameScopeFirst seen
test.opera.softwaretestIn scope2026-11-14
le-test.opera.softwaretestIn scope2026-11-14
syslog-test.opera.softwaretestIn scope2026-11-14
opensearch-test.opera.softwaretestIn scope2026-11-14
airflow-test.osp.opera.softwaretest, toolsIn scope2026-11-14
am4-lvs-test.osp.opera.softwaretestIn scope2026-11-14
lvs-ash-test.osp.opera.softwaretestIn scope2026-11-14
ospstatus-test.osp.opera.softwaretestIn scope2026-11-14
revenueapi-test.osp.opera.softwaretestIn scope2026-11-14
influxdb-test-ash.osp.opera.softwaretestIn scope2026-11-14
swolowski-test-01.osp.opera.softwaretestIn scope2026-11-14
ospsubmit-test-ams.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-1.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-2.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-3.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-4.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-5.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-6.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-7.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-01.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-02.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-03.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-04.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-05.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-07.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-12.osp.opera.softwaretestIn scope2026-11-14
forsberg-test-cmdline-13.osp.opera.softwaretestIn scope2026-11-14

4,983 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.