- Top reward
- Not published
- 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.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
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
As a token of our gratitude for your assistance, new and accepted security reports will qualify for a reward.
- Response
-
Within 5 days
We will respond to your valid report within five business days with our evaluation of the report and an expected resolution date.
- Safe harbor
-
Full
If you have followed the instructions above, we will not take any legal action against you in regard to the report.
- Hall of fame
-
Yes
In the public information concerning the problem reported, we will give your name as the discoverer of the problem in our hall of fame (unless you desire otherwise)
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 2
- greenhost.net
- greenhost.nl
Out of scope (5)
- any system of a customer on a Greenhost network
- E-mail policies such as SPF, DKIM and DMARC
- HTTP headers policies such as X-Frame-Options, HSTS, Host headers injections
- Social engineering (e.g. phishing, vishing, smishing)
- Vulnerability in another project/software that Greenhost depends on
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Greenhost's policy. "We" in these lines means the program, not this site.
While testing
-
Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people’s data.
-
Do not reveal the problem to others until it has been resolved.
-
Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties .
-
Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible.
Not accepted
-
Security advice or best practices
-
Configuration disclosures and path disclosures
-
Tampering: Temporary modification of data in a specific scenario that does not persist, requiring user interaction to be exploitable.
-
Security vulnerabilities that are already reported or currently in a disclosure process (duplicate).
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.