$500 awarded on Verisign Bug Bounty, against www.verisign.com (Website; non-DNS related).
Everything Bugcrowd published about this
- Programme
- Verisign Bug Bounty In our directory, so it has reviews and a grade.
- Platform handle
- verisign
- Asset
- www.verisign.com (Website; non-DNS related) The specific asset the finding landed against, as the platform named it.
- Severity
- low Bugcrowd rates P1–P5; this is that rating in HackerOne's words so the two feeds can sit in one table.
- Award
- $500 What the platform printed. Where a report carried more than one payment they are summed.
- Found by
- ferreira Named because the finder allowed the platform to name them.
- State
- resolved — the programme has fixed it
- Accepted
- 27 March 2026 6 months ago. This is the date the programme accepted the finding.
- First seen here
- 16 August 2026 When our sweep first read this entry. It says nothing about the finding, only about us.
- Platform reference
- aaab3af4-6251-41e1-9d74-119dba644edc
Where this award sits
A single large number tells you nothing on its own. What matters is whether this programme pays like this routinely or whether this was the one time it did.
It is the 4th largest of 6 awards this programme has published. It sits below this programme's median, so larger figures are routine here.
Every figure here is drawn only from awards a platform chose to publish, which is a minority of what gets paid. Read the median as "of the payouts made public", never as "what this programme pays".
What else ferreira has published on Bugcrowd
- Cisco Responsible Disclosure critical · Cisco Systems operational infrastructure · 1 month ago —
- State of California VDP medium · *.ca.gov · 1 month ago —
- Atlassian low · Any associated *.atlassian.com or *.atl-paas.net domain that can be exploited DIRECTLY from the *.atlassian.net instance · 2 months ago $250
Counted within Bugcrowd only. The same handle on another platform may or may not be the same person, and this page will not assume it is.
What else Verisign Bug Bounty has published
- *.verisign.com low · unresolved · vortex_77 · 15 days ago $100
- *.verisign.com critical · unresolved · withheld · 15 days ago $2,500
- Finding accepted medium · unresolved · withheld · 2 months ago —
- *.verisign.com low · unresolved · withheld · 3 months ago —
- *.verisign.com low · unresolved · withheld · 3 months ago —
- *.verisign.com low · resolved · withheld · 4 months ago —
- epptool-ctld.verisign-grs.com (EPP service; DNS related) low · unresolved · withheld · 4 months ago —
- *.verisign.com critical · resolved · AbuElkhair · 6 months ago —
Where this came from. One row of a public platform feed, stored as published and never edited. We hold no report title, no write-up and no reproduction steps, because the feeds do not carry them and we do not go looking for them. A withheld name stays withheld; if a finder later asks the platform to un-name them, the next sweep un-names them here. Absence of an award figure is publication policy, not evidence a programme did not pay.