Bug bounty program
Bitdefender
- Platform
- Bugcrowd
- Bounties
- Pays
- Assets in scope
- 5
- Disclosed reports
- 0
- Subdomains
- 2,379
- Vendor on CyberSIXT
- Bitdefender (104 CVEs, 0 exploited)
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains2,379
| Name | Scope | First seen |
|---|---|---|
| beta-login.bitdefender.comauth, staging | In scope | 2026-11-14 |
| api.beta-login.bitdefender.comapi, auth, staging | In scope | 2026-11-14 |
| www.api.beta-login.bitdefender.comapi, auth, staging | In scope | 2026-11-14 |
| www.beta-login.bitdefender.comauth, staging | In scope | 2026-11-14 |
| login.bitdefender.comauth | In scope | 2026-11-14 |
| api.login.bitdefender.comapi, auth | In scope | 2026-11-14 |
| www.api.login.bitdefender.comapi, auth | In scope | 2026-11-14 |
| www.login.bitdefender.comauth | In scope | 2026-11-14 |
| auth.mdr.bitdefender.comauth | In scope | 2026-11-14 |
| auth.mdrt.bitdefender.comauth | In scope | 2026-11-14 |
| oem-login.bitdefender.comauth | In scope | 2026-11-14 |
| www.oem-login.bitdefender.comauth | In scope | 2026-11-14 |
| oem-us-login.bitdefender.comauth | In scope | 2026-11-14 |
| login.athena.bitdefender.netauth | In scope | 2026-11-14 |
| okta.m-vpn.in.test.vdc.sandbox.2d7dd.cdn.bitdefender.netauth, test, vpn | In scope | 2026-11-14 |
| 228199119575-signin.kdn.kdn.my.2d8cd.cdn.bitdefender.netauth | In scope | 2026-11-14 |
| 8199119575-signin.kdn.kdn.my.2d8cd.cdn.bitdefender.netauth | In scope | 2026-11-14 |
| login.bitdefender.netauth | In scope | 2026-11-14 |
| login-lb.bitdefender.netauth | In scope | 2026-11-14 |
| beta.login.bitdefender.netauth, staging | In scope | 2026-11-14 |
| www.beta.login.bitdefender.netauth, staging | In scope | 2026-11-14 |
| www.login.bitdefender.netauth | In scope | 2026-11-14 |
| oem-login.bitdefender.netauth | In scope | 2026-11-14 |
| threeuk-login.bitdefender.netauth | In scope | 2026-11-14 |
| windtre-login.bitdefender.netauth | In scope | 2026-11-14 |
2,355 names are covered by the program's own scope; 5 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.