Public information layer
- Resolves through ordinary DNS
- Can be indexed by search engines
- Explains provenance and PGP checks
- Should not request market credentials
- Does not prove a Tor operator’s identity
Threat model · clone detection
A public website can explain verification and provide a deliberate route. It should not be mistaken for the Tor destination, and a clearnet login or payment prompt deserves immediate scrutiny.
Different network roles
Phishing-clone signals
A public page asking for destination credentials collapses the boundary between information and authentication. Leave rather than testing the form.
A hostname labelled “official” is still an assertion. Look for an original signed statement and a separately established fingerprint.
Claims that an address must be used immediately can discourage comparison. Verify replacement language before treating a new route as current.
Instructions to compare only the first or last characters normalize lookalikes. Match the full hostname from verified text.
A clone can provide its own key and valid signature. The fingerprint needs independent provenance outside that bundle.
Extra domains or altered hostnames break the evidence chain. Do not enter credentials after a destination changes unexpectedly.
A common misconception
HTTPS protects transport between your browser and the certificate holder for that clearnet hostname. It does not establish that the site is affiliated with a separate onion service, nor does it validate an onion hostname displayed on the page.
Use TLS as one transport control, not as an identity bridge between unrelated domains.
When something does not match
Close the page, preserve the hostname and source for comparison, and restart from independently established evidence. Do not enter test credentials, reuse a recovery phrase or send a small payment to “confirm” a route.
Build the evidence chain
Learn how a fingerprint, signature, publication context and exact hostname work together.
Click-only route
This reference does not publish a destination address. The handoff starts in this tab only after you press the button.
A route is not a guarantee of availability, identity or safety.