Bug bounty program
NE
Newegg
Most upvoted reports1
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Endpoint disclosing user password#1986731 | No weakness recorded | – | $250 | 64 |
Subdomains19,743
| Name | Scope | First seen |
|---|---|---|
| metrics.newegg.camonitoring | In scope | 2026-11-14 |
| elk.newegg.commonitoring | In scope | 2026-11-14 |
| logging.newegg.commonitoring | In scope | 2026-11-14 |
| logs.newegg.commonitoring | In scope | 2026-11-14 |
| metrics.newegg.commonitoring | In scope | 2026-11-14 |
| metrics-staging.newegg.commonitoring, staging | In scope | 2026-11-14 |
| metrics1-staging.newegg.commonitoring, staging | In scope | 2026-11-14 |
| monitor.newegg.commonitoring | In scope | 2026-11-14 |
| www.monitor.newegg.commonitoring | In scope | 2026-11-14 |
| monitor1.newegg.commonitoring | In scope | 2026-11-14 |
| monitor2.newegg.commonitoring | In scope | 2026-11-14 |
| monitor3.newegg.commonitoring | In scope | 2026-11-14 |
| monitoring.newegg.commonitoring | In scope | 2026-11-14 |
| www.monitoring.newegg.commonitoring | In scope | 2026-11-14 |
| monitoring2.newegg.commonitoring | In scope | 2026-11-14 |
| nagios.newegg.commonitoring | In scope | 2026-11-14 |
| nagios2.newegg.commonitoring | In scope | 2026-11-14 |
| prometheus.newegg.commonitoring | In scope | 2026-11-14 |
| sentry.newegg.commonitoring | In scope | 2026-11-14 |
| splunk.newegg.commonitoring | In scope | 2026-11-14 |
| status.newegg.commonitoring | In scope | 2026-11-14 |
| www.status.newegg.commonitoring | In scope | 2026-11-14 |
| zabbix.newegg.commonitoring | In scope | 2026-11-14 |
| www.zabbix.newegg.commonitoring | In scope | 2026-11-14 |
| zabbix2.newegg.commonitoring | In scope | 2026-11-14 |
| metrics.neweggbusiness.commonitoring | Listed out of scope | 2026-11-14 |
| metrics1.neweggbusiness.commonitoring | Listed out of scope | 2026-11-14 |
19,688 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.