- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 6
- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 3 days
- As the policy promises.
- Payment
- Proof of identity needed to get paid.
- 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
Accepted reports may be rewarded with money or swag, depending on severity, novelty, and impact.
- Response
-
Within 3 days
We aim to respond to initial reports within 72 hours.
- Safe harbor
-
Partial
Responsible disclosure: Give us a reasonable time to investigate and fix issues before making anything public.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 2 excluded.
Domains 5
- api.elmah.io
- app.elmah.io
- blog.elmah.io
- docs.elmah.io
- elmah.io
Wildcard domains 1
- any other subdomain owned by elmah.io
Out of scope (2)
- demo environments
- staging systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from elmah.io's policy. "We" in these lines means the program, not this site.
While testing
-
Do no harm: Do not exploit vulnerabilities beyond what is necessary to demonstrate them.
-
Respect data: Never access, modify, or delete customer data. Use your own account where possible.
-
Responsible disclosure: Give us a reasonable time to investigate and fix issues before making anything public.
-
No disruption: Do not perform attacks that degrade our service (e.g., DDoS, spam, brute force).
Not accepted
-
Denial of Service (DoS / DDoS)
-
Public API keys used for JavaScript logging
-
Missing CAA DNS configuration
-
Session expiration and invalidation
-
Vulnerabilities in 3rd party services we use
-
Best-practice suggestions without a clear security impact
-
Missing security headers without an exploit scenario
-
Social engineering, phishing, or physical security attacks
-
Generally, issues produced by automated tools like security headers, etc.
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 6 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.