Bug bounty program
Nominet
- Platform
- HackerOne
- Bounties
- None
- Assets in scope
- 3
- Disclosed reports
- 0
- Subdomains
- 8,163
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains8,163
| Name | Scope | First seen |
|---|---|---|
| api.nominet.org.ukapi | In scope | 2026-11-14 |
| test-api.nominet.org.ukapi, test | In scope | 2026-11-14 |
| api.nominet.ukapi | In scope | 2026-11-14 |
| dns.api.nominet.ukapi | In scope | 2026-11-14 |
| www.api.nominet.ukapi | In scope | 2026-11-14 |
| zdns-api.nominet.ukapi | In scope | 2026-11-14 |
| beta-zdns-api.nominet.ukapi, staging | In scope | 2026-11-14 |
| domainhealth-api.nominet.ukapi | In scope | 2026-11-14 |
| beta-domainhealth-api.nominet.ukapi, staging | In scope | 2026-11-14 |
8,163 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.