ignitioncasino.eu
Bug bounty on security.txt ignitioncasino.eu
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Replies within 2 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
The types of vulnerabilities that we reward the highest for are critical vulnerabilities, such as remote code execution, access to server source code or data, and cheating on games leading to financial gain.
- Response
-
Within 2 days
A member of our Cyber Security team will respond to your report as soon as possible, usually within 2 business days, please take into consideration time zone differences in our response time.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 10 excluded.
Domains 1
- ignitioncasino.eu
Out of scope (10)
- Low Impact Information Disclosure, such as Apache, PHP versions, etc.
- Missing Cookie Flags.
- Missing DMARC/SPF.
- Missing Security Headers.
- Outdated WordPress Core, Plugins, or Themes (unless remotely exploitable).
- Password policy issues.
- Self-Cross-Site Scripting (XSS).
- Session Handling (unless Medium severity or above).
- SSL/TLS Misconfigurations.
- Username Enumeration.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from ignitioncasino.eu's policy. "We" in these lines means the program, not this site.
While testing
-
In the event that we receive duplicate reports, the first report received will be considered the valid one.
-
Do not attempt any Denial of Service (DoS) attacks.
-
Do not modify any user or system data.
-
Do not disclose the vulnerability to any third-parties, or publicly, until we have remediated the vulnerability.
-
Do not compromise other users' accounts or data.
-
Do not use automated tools, such as web vulnerability scanners.
-
Do not conduct Social Engineering attacks, Phishing, or any physical testing, such as lock picking.
-
Employees and business partners are excluded from the Bug Bounty.
Not accepted
-
Informational or Low severity issues
-
Missing Security Headers.
-
Missing Cookie Flags.
-
SSL/TLS Misconfigurations.
-
Username Enumeration.
-
Outdated WordPress Core, Plugins, or Themes (unless remotely exploitable).
-
Low Impact Information Disclosure, such as Apache, PHP versions, etc.
-
Self-Cross-Site Scripting (XSS).
-
Password policy issues.
-
Missing DMARC/SPF.
-
Session Handling (unless Medium severity or above).
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 12 Nov 2026. Last checked 2 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.