Bug bounty program
Allegion
- Platform
- HackerOne
- Bounties
- None
- Assets in scope
- 130
- Disclosed reports
- 0
- Subdomains
- 9,274
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains9,274
| Name | Scope | First seen |
|---|---|---|
| 191.120-repo.119.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 133-207-gitlab.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 236.13scm.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 168.236.13scm.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 15998-gitlab.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 177-101-git.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| bitbucket.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| ww25.bitbucket.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 16-124.krytonitelock.gitlab.com.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 163.krytonitelock.scm.com.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| gitlab.internal.privacy.docs.krytonitelock.comgit, internal | Not in the scope | 2026-11-14 |
| ww25.gitlab.internal.privacy.docs.krytonitelock.comgit, internal | Not in the scope | 2026-11-14 |
| git.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| ww25.git.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| github.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| gitlab.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 236.gitlab13.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| 168.236.gitlab13.krytonitelock.comgit | Not in the scope | 2026-11-14 |
| gitlab.internal.de.v220190810283696009.krytonitelock.comgit, internal | Not in the scope | 2026-11-14 |
| ww25.gitlab.internal.de.v220190810283696009.krytonitelock.comgit, internal | Not in the scope | 2026-11-14 |
1,157 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.