Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
8
Disclosed reports
2
Subdomains
420

Most upvoted reports2

Most upvoted reports of Chainlink
ReportWeaknessDisclosedBountyVotes
No Valid SPF Records.Analysed#629087Authentication2019-07-18–52
Testnet address being sent in cleartext as http://rinkeby.chain.link/ is missing SSL certificate#576288Cryptography2019-07-17–19

Subdomains420

Subdomains of Chainlink
NameScopeFirst seen
ace.api.chain.linkapiNot in the scope2026-11-14
api.cre.chain.linkapiNot in the scope2026-11-14
fms-rpc.chain.linkapiNot in the scope2026-11-14
api.ccip.chain.linkapiNot in the scope2026-11-14
gql.graph.chain.linkapiNot in the scope2026-11-14
markets.api.chain.linkapiNot in the scope2026-11-14
api.dataengine.chain.linkapiNot in the scope2026-11-14
fast-stake-api.chain.linkapiNot in the scope2026-11-14
cre-connect.api.chain.linkapiNot in the scope2026-11-14
api.testnet-dataengine.chain.linkapiNot in the scope2026-11-14
grpc.staging.telemetry.chain.linkapi, stagingNot in the scope2026-11-14
api.data-streams-portal.chain.linkapiNot in the scope2026-11-14

192 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-15.