Current directory
No services published yet
The directory starts empty. Editors can add a record only after documenting the operator’s first-party source, exact hostname, review date, and public-interest purpose.
Why the directory starts small
A directory with no unsupported records is more useful than a large copied list. Every future entry must be traceable to an established first-party HTTPS source and must fit the publication’s public-interest scope. The number of listings is not a quality target.
Eligible service types
- official newsroom and publisher onion counterparts;
- reviewed SecureDrop instances and source-communication projects;
- human-rights and civil-society organizations;
- censorship-resistance and nonprofit privacy projects;
- official software documentation and authenticated project mirrors;
- academic, archival, or research resources with a clear public-interest purpose.
Commercial anonymity alone is not a public-interest purpose. The directory does not accept anonymous markets, vendor submissions, affiliate links, paid placement, or services whose central function appears to facilitate harm or unlawful trade.
Evidence required before publication
| Field | Minimum requirement |
|---|---|
| Operator | A recognizable organization or project identity |
| First-party source | An established HTTPS page controlled by that operator |
| Onion hostname | A complete valid v3 hostname matching the source |
| Purpose | A neutral explanation of the public-interest function |
| Review date | The real date the evidence was checked |
| Status | Ownership and operation described separately |
| Correction route | A way to report an error or replacement |
What a published record means
An entry means that the available evidence connected the exact address to the stated operator and that the service fitted the directory scope when reviewed. It does not guarantee uninterrupted availability, perfect security, legal compliance in every jurisdiction, or agreement with every statement published by the operator.
Maintenance rules
- Review a record after an authenticated address-change announcement.
- Recheck after a credible clone report, extended outage, or change in service purpose.
- Move obsolete addresses to history rather than silently replacing them.
- Remove records that can no longer be maintained responsibly.
- Record material changes in the public update log.
How to propose a service
Read the submission criteria and include the first-party source, exact hostname, purpose, announcement date, and correction contact. A submission is a request for review, not a promise of inclusion.