Bug bounty program
KU
Kubernetes
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 82
- Disclosed reports
- 77
- Subdomains
- 662
- Vendor on CyberSIXT
- Kubernetes (120 CVEs, 0 exploited)
Most upvoted reports77
All reportsSubdomains662
| Name | Scope | First seen |
|---|---|---|
| k8s.gcr.iotools | In scope | 2026-11-14 |
| wiki.gcr.iotools | Not in the scope | 2026-11-14 |
| dl.k8s.gcr.iotools | Not in the scope | 2026-11-14 |
| docker.gcr.iotools | Not in the scope | 2026-11-14 |
| www.k8s.gcr.iotools | Not in the scope | 2026-11-14 |
| registry.gcr.iotools | Not in the scope | 2026-11-14 |
| kubernetes.gcr.iotools | Not in the scope | 2026-11-14 |
| k8s-staging.gcr.iostaging, tools | Not in the scope | 2026-11-14 |
| my-registry.gcr.iotools | Not in the scope | 2026-11-14 |
| rancher1k8s.gcr.iotools | Not in the scope | 2026-11-14 |
| staging-k8s.gcr.iostaging, tools | Not in the scope | 2026-11-14 |
| kube-apiserverk8s.gcr.iotools | Not in the scope | 2026-11-14 |
| fluentdstaging-k8s.gcr.iotools | Not in the scope | 2026-11-14 |
| kube-controller-managerk8s.gcr.iotools | Not in the scope | 2026-11-14 |
| xn--k8s-628dp2nm3azzu2ja3251b4jva.gcr.iotools | Not in the scope | 2026-11-14 |
| registry.k8s.iotools | Not in the scope | 2026-11-14 |
| cdn.registry.k8s.iotools | Not in the scope | 2026-11-14 |
| k8s-infra-prow.k8s.iotools | Not in the scope | 2026-11-14 |
| registry-sandbox.k8s.iotest, tools | Not in the scope | 2026-11-14 |
| kubernetes.submit-queue.k8s.iotools | Not in the scope | 2026-11-14 |
| kube-network-policies.sigs.k8s.iotools | Not in the scope | 2026-11-14 |
| k8s-infra-cdn-cf-sandbox-ame.k8s.iotest, tools | Not in the scope | 2026-11-14 |
| kube-agentic-networking.sigs.k8s.iotools | Not in the scope | 2026-11-14 |
| kube-network-policies.sigs.canary.k8s.iostaging, tools | Not in the scope | 2026-11-14 |
| virus0316dev2-k8s-876543210z-www.27654.service.now.com2-logindevticketingfoia-dot-gov.appv1-7.docs.k8s.iodev, tools | Not in the scope | 2026-11-14 |
2 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.