Threat model · clone detection

Mars onion vs clearnet: separate reference from destination

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.

The same brand name does not make two pages equivalent

Clearnet reference

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
Onion destination

Tor-resolved service layer

  • Uses a v3 onion hostname
  • Resolves inside the Tor network
  • Must be tied to independently checked evidence
  • Can be imitated by another onion service
  • Needs a full-hostname comparison every time it changes

Presentation can be copied; provenance is harder to fake

Credentials on clearnet

A public page asking for destination credentials collapses the boundary between information and authentication. Leave rather than testing the form.

Address shown without evidence

A hostname labelled “official” is still an assertion. Look for an original signed statement and a separately established fingerprint.

Urgency and replacement pressure

Claims that an address must be used immediately can discourage comparison. Verify replacement language before treating a new route as current.

Partial-match reassurance

Instructions to compare only the first or last characters normalize lookalikes. Match the full hostname from verified text.

Bundled key and statement

A clone can provide its own key and valid signature. The fingerprint needs independent provenance outside that bundle.

Unexpected redirect chain

Extra domains or altered hostnames break the evidence chain. Do not enter credentials after a destination changes unexpectedly.

HTTPS does not turn a clearnet clone into the Tor service

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.

PadlockEncrypted clearnet connection
Valid certificateControl of that DNS hostname
Matching logoReusable visual asset
Verified signatureMessage integrity for a known key

Do not troubleshoot through a suspicious form

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.

Start with the signed mirror method

Learn how a fingerprint, signature, publication context and exact hostname work together.

Verify a Mars mirror announcement

Open the Mars Market route

This reference does not publish a destination address. The handoff starts in this tab only after you press the button.

  • Compare the loaded hostname with independently verified evidence.
  • Do not treat a working page as proof of operator identity.
  • Leave if the destination or login flow differs from what you checked.

A route is not a guarantee of availability, identity or safety.