- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 2
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 5 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
Dentsu does not operate a public bug bounty program and will not provide a reward or compensation in exchange for reporting potential issues.
- Response
-
Within 5 days
dentsu commits to provide prompt acknowledgement of receipt of all reports (in any event, within 5 business days of submission).
- Safe harbor
-
Partial
By acting in accordance with the guidelines above and responsibly submitting your findings to dentsu, Dentsu agrees not to pursue legal action against you unless it is compelled to do so by a regulatory authority, other third party, or applicable laws
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 5 excluded.
Domains 1
- dentsu.com
Products and areas 1
- any product, system, or asset belonging to dentsu
Out of scope (5)
- Denial of service attacks
- Phishing
- Physical testing of premises
- Resource Exhaustion Attacks
- Social engineering. For example, attempts to steal cookies, fake login pages to collect credentials
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Dentsu's policy.
While testing
-
Do not engage in any activity that can cause potential or actual harm to dentsu, dentsu customers, or dentsu employees.
-
Do not engage in any activity that can potentially or actually degrade dentsu services or assets or cause them to stop entirely.
-
Do not store, share, compromise or destroy dentsu or any customer data.
-
Do not initiate a fraudulent financial transaction.
-
Do not disclose any reported issues to third parties, or publish such reported issues publicly
Not accepted
-
Physical testing of premises
-
Social engineering. For example, attempts to steal cookies, fake login pages to collect credentials
-
Phishing
-
Denial of service attacks
-
Resource Exhaustion Attacks
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.