Hornetsecurity
Bug bounty on security.txt hornetsecurity.com
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 4
- 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 through their form
- hornetsecurity.com/.well-known/security.txt
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 14 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
At our own discretion, bug bounties are offered for meaningful reports that enhance the security posture of our systems.
- Response
-
Within 14 days
Hornetsecurity will triage your report and confirm, request more information or reject the report within 14 days.
- Safe harbor
-
Full
Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 3 excluded.
Domains 3
- altaro.com
- antispameurope.com
- hornetsecurity.com
Products and areas 1
- any digital assets owned, operated, or maintained by Hornetsecurity
Out of scope (3)
- Assets or other equipment not owned or operated by Hornetsecurity.
- Third party tools or software not hosted by Hornetsecurity.
- Vulnerabilities in open source components that have been released to the public within the last 14 days.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Hornetsecurity's policy. "We" in these lines means the program, not this site.
While testing
-
Limit your testing and exploitation of vulnerabilities to the absolute minimum required, i.e. instead of dumping a whole database, only query for single entries to perform spot checks.
-
Whenever possible, exploit accounts that you yourself own and operate. Do not try to access other people’s data.
-
Only use non-destructive payloads.
-
Do not test for (D)DoS.
-
Do not perform test that put heavy load on our systems.
-
Do not perform tests on third-party systems that are not hosted by Hornetsecurity.
-
Do not perform non-technical attacks (e.g. Phishing) against our employees, customers or users.
-
Do not use any of Hornetsecurity’s trademarks, brands or likeliness without prior written approval for any tests.
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 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.