Skip to content

Bug bounty program

Platform
HackerOne
Bounties
Pays
Assets in scope
8
Disclosed reports
0
Subdomains
1,696

Most upvoted reports0

No report of this program is publicly disclosed

Subdomains1,696

Subdomains of Tinder
NameScopeFirst seen
db.datadev1.tinderops.netdataIn scope2026-11-14
kafka.prometheus.tinderops.netdata, monitoringIn scope2026-11-14
redis.prometheus.tinderops.netdata, monitoringIn scope2026-11-14
dev-redis.datadev1.tinderops.netdata, devIn scope2026-11-14
kafka-dev.datadev1.tinderops.netdata, devIn scope2026-11-14
prod-redis.datadev1.tinderops.netdataIn scope2026-11-14
rundeck-db.datadev1.tinderops.netdataIn scope2026-11-14
rundeck-ops-db.ue1az.tinderops.netdataIn scope2026-11-14
elasticsearch.prometheus.tinderops.netdata, monitoringIn scope2026-11-14
rundeck-reporting-db.ue1.tinderops.netdataIn scope2026-11-14
kafka-cruise-control.ue1.d2.tstaging.toolsdataIn scope2026-11-14

1,693 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