Bug bounty program
Blend Labs
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 1
- Disclosed reports
- 0
- Subdomains
- 3,066
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains3,066
| Name | Scope | First seen |
|---|---|---|
| grafana.k8s.beta.blend.commonitoring, staging, tools | Not in the scope | 2026-11-14 |
| prometheus.k8s.beta.blend.commonitoring, staging, tools | Not in the scope | 2026-11-14 |
| enologist.logs.dash.blend.commonitoring | Not in the scope | 2026-11-14 |
| splunk.dash.blend.commonitoring | Not in the scope | 2026-11-14 |
| grafana.k8s.preprod.blend.commonitoring, staging, tools | Not in the scope | 2026-11-14 |
| prometheus.k8s.preprod.blend.commonitoring, staging, tools | Not in the scope | 2026-11-14 |
| github-splunk-proxy.k8s.prod.blend.comgit, monitoring, tools | Not in the scope | 2026-11-14 |
| grafana.k8s.prod.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| metrics.k8s.prod.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| prometheus.k8s.prod.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| status.k8s.prod.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| status.blend.commonitoring | Not in the scope | 2026-11-14 |
| grafana.k8s.tools.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| prometheus.k8s.tools.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| sentry.k8s.tools.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| sentry-proxy.k8s.tools.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| sentry-relay.k8s.tools.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| sentry-relay-proxy.k8s.tools.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| sentry-proxy.k8s.tools.us-east-1.blend.commonitoring, tools | Not in the scope | 2026-11-14 |
| logs-vpc2.preprod.blendlabs.commonitoring, staging | Not in the scope | 2026-11-14 |
| logs.prod.blendlabs.commonitoring | Not in the scope | 2026-11-14 |
1 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.