Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
6
Disclosed reports
0
Subdomains
321
Vendor on CyberSIXT
Razorpay (9 CVEs, 0 exploited)

Most upvoted reports0

No report of this program is publicly disclosed

Subdomains321

Subdomains of Razorpay
NameScopeFirst seen
qa-sonar.razorpay.comtest, toolsNot in the scope2026-11-14
test-api.razorpay.comapi, testNot in the scope2026-11-14
uat-cert.razorpay.comtestNot in the scope2026-11-14
ifsc-test.razorpay.comtestNot in the scope2026-11-14
www.uat-cert.razorpay.comtestNot in the scope2026-11-14
jira-uat.corp.razorpay.cominternal, test, toolsNot in the scope2026-11-14
test-blue.k8s.razorpay.comtest, toolsNot in the scope2026-11-14
posrevenue-test.razorpay.comtestNot in the scope2026-11-14
uat.postpayments.razorpay.comtestNot in the scope2026-11-14
yesbank-uat-nonprod.razorpay.comtestNot in the scope2026-11-14
www.uat.postpayments.razorpay.comtestNot in the scope2026-11-14
www.yesbank-uat-nonprod.razorpay.comtestNot in the scope2026-11-14

6 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-14.

Updated AboutDevelopersSign in