disclose.io valid

disclose.io

disclose.io is the open, vendor-neutral infrastructure that powers vulnerability disclosure and security reporting, safe, simple, and standardized for everyone.

For agents: Open, vendor-neutral directory of bug bounty and vulnerability disclosure programs, with safe-harbor language, threat archive and open datasets on GitHub.

vulnerability disclosurebug bountysecurity researchsafe harboropen database

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T12:57:24.507Z. Cached copy · Source on disclose.io

# disclose.io

> disclose.io is the open, vendor-neutral infrastructure that powers vulnerability disclosure and security reporting, safe, simple, and standardized for everyone.

We maintain open-source databases, policy templates, tools, and resources to make vulnerability disclosure safe, simple, and standardized for everyone. A fuller machine-readable corpus is available at [llms-full.txt](https://disclose.io/llms-full.txt).

## Open Databases

- [Bug Bounty Platforms](https://disclose.io/platforms/): Community-curated directory of every known bug bounty, vulnerability disclosure, and crowdsourced security platform. Open-source at github.com/disclose/bug-bounty-platforms.
- [VDP Programs](https://directory.disclose.io/): The largest open directory of vulnerability disclosure and bug bounty programs on the public internet. Each entry includes scope, policy URL, and safe-harbor language. Powers lookup.disclose.io.
- [Research Threats](https://disclose.io/threats/): Canonical public archive of legal threats made against security researchers engaged in good-faith vulnerability disclosure. Open-source at github.com/disclose/research-threats.
- [State of Disclosure / Scoreboard](https://state.disclose.io): The evidence-backed safe-harbor scoreboard for the world's biggest companies (state.disclose.io/top-100).

## The Framework

- [Framework Overview](https://disclose.io/framework/): Open-source, public-domain reference for running a vulnerability disclosure program. CC0 1.0 licensed.
- [Legal Terms (dioterms)](https://disclose.io/framework/terms/): Canonical legal terms organizations can drop into their own disclosure policies.
- [VDP terms](https://disclose.io/framework/terms/vdp/): The standard vulnerability disclosure policy terms.
- [VDP with CVD terms](https://disclose.io/framework/terms/vdp-with-cvd/): VDP terms extended with coordinated vulnerability disclosure language.
- [Bug Bounty Program (BBP) terms](https://disclose.io/framework/terms/bbp/): Terms specific to a paid bug bounty program.
- [diostatus Maturity Model](https://disclose.io/framework/maturity/): Six-level ladder (Level 0 → Level 5) measuring program maturity.

## Documentation

- [What is disclose.io](https://disclose.io/docs/what-is-disclose.io/): The open, vendor-neutral infrastructure that powers vulnerability disclosure and security reporting.
- [Vision and Mission](https://disclose.io/docs/vision-and-mission/): Make vulnerability disclosure safe, simple, and standardized for everyone.
- [Design Strategy](https://disclose.io/docs/design-strategy/): Design principles for making secure easy and insecure obvious.
- [Key Objectives](https://disclose.io/docs/key-objectives/): The key objectives driving the disclose.io project.
- [For Finders and Hackers](https://disclose.io/docs/for-finders-and-hackers/): How disclose.io helps security researchers and finders.
- [For Organizations and Legal Teams](https://disclose.io/docs/for-organizations-and-legal-teams/): How disclose.io he
…

Related sites

Other listed sites in Cybersecurity. See the whole category →

Machine-readable: GET /v1/resolve?q=disclose.io · GET /v1/domain/disclose.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for disclose.io:
1. POST https://agentwebmap.com/v1/sites/disclose.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://disclose.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/disclose.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/disclose.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.