Protocol role
The address is used within the onion-service system to identify a service destination.
What it cannot prove
It does not independently establish the operator’s real-world identity, honesty or current control.
Verification limit
A copied address can be mistyped, altered or misrepresented. A familiar name is not cryptographic proof of legitimacy.
Address-versus-identity test
The following scenario is fictional and is included to demonstrate the method. It is not a factual allegation about BLACKOPS, BLACKOPS DARKNET, BLACKOPS MARKET, BLACKOPS LINK or any real service.
A syntactically valid onion address is presented as proof that a publisher is legitimate.
Separate address format, cryptographic service identity and real-world operator identity. A valid address does not certify the service's honesty, safety or legality.
From observation to a defensible publication
A repeatable sequence makes the reasoning visible. Each stage should leave a record that the next reviewer can inspect.
- 01DefineName the protocol component
- 02ExplainDescribe the documented mechanism
- 03BoundIdentify assumptions and exclusions
- 04ReviewCheck endpoint and threat-model limits
| Technical question | Required distinction |
|---|---|
| Claim scope | Which protocol layer or component is being described |
| Mechanism | What official documentation says the component does |
| Boundary | What the mechanism does not guarantee |
| Endpoint factor | Application, device and destination behavior outside the narrow claim |
What this page can—and cannot—establish
For “An address is not an identity certificate.”, the strongest defensible output is a traceable description of the available record: what was observed, how it was sourced, when it was recorded and which interpretation follows from it.
This page cannot establish facts that are absent from its cited material. It does not authenticate a similarly named service, identify an operator, prove current availability or certify the safety or legality of a destination.
A future update should change the conclusion only when new, attributable evidence changes the record. Corrections should identify the earlier wording, the new evidence and the date of revision.
Primary references and further reading
These sources support the general method or technical background described here. They do not independently verify a claim about a BLACKOPS-named service.
- Tor Project — How do Onion Services work? — Official high-level description of introduction points, descriptors and rendezvous.
- Tor Specifications — A short introduction to Tor — Protocol-level introduction to relays and Tor's distributed overlay design.