- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 7
- 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]
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
Scope
7 assets you may test, 1 excluded.
Domains 4
- ravelin.click
- ravelin.com
- ravelin.net
- www.ravelin.com
Wildcard domains 3
- *.ravelin.click
- *.ravelin.com
- *.ravelin.net
Out of scope (1)
- Any host not specifically mentioned
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Ravelin's policy. "We" in these lines means the program, not this site.
While testing
-
All submissions should be made by emailing [email protected] using the PGP key below to encrypt the content.
-
Any other form of reporting will not receive a response and repeated attempts to use other emails may result in the email being flagged and the address blocked.
-
Your report should include a detailed summary of the vulnerability, including the target, steps, tools and artefacts used during the discovery that will allow us to reproduce the vulnerability.
Not accepted
-
Security Practices where other mitigating controls exist i.e. missing security headers, etc.
-
Sender Policy Framework (SPF), DKIM and DMARC configuration suggestions
-
Social Engineering e.g. Phishing
-
Physical Attacks
-
Missing Cookie Flags
-
CSRF with minimal impact i.e. Login CSRF, Logout CSRF, etc.
-
Content Spoofing
-
Stack Traces, Path Disclosure, Directory Listings
-
SSL/TLS controls where other mitigating controls exist
-
Banner Grabbing
-
CSV Injection
-
Reflected File Download
-
Reports on out dated browsers
-
DOS/DDOS
-
Host header Injection without a demonstrable impact
-
Scanner outputs without any proof-of-concept attack
-
Vulnerabilities on Third-Party Products
-
User Enumeration
-
Password Complexity
-
HTTP Trace Method
-
Tokens/Keys that are intended to be public
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.