Pre-access verification

Check the Mars onion before access

Navigation should be the last step, not the first. Establish the address from signed evidence, compare it exactly and decide in advance which inconsistencies will make you stop.

Five questions with yes-or-stop answers

01

Do I know where this hostname came from?

Use the original publication rather than a search snippet, chat message, screenshot or shortened link. Preserve enough context to identify the issuer and version.

02

Did I establish the signing fingerprint independently?

Compare the complete fingerprint through a separate trusted path. The key delivered with an untrusted hostname cannot authenticate itself.

03

Did the exact statement verify?

Confirm the cryptographic result against the original bytes. Read both the signature status and the fingerprint that produced it.

04

Does every hostname character match?

Compare the entire v3 value. Partial visual matches do not transfer trust, and one changed character identifies a different destination.

05

Is there any unresolved conflict?

Stop if sources disagree, the fingerprint is uncertain, the statement is superseded or the destination changes unexpectedly.

Verification continues at the destination

Compare the loaded hostname again before entering credentials. Leave if you see an unexpected redirect, a changed recovery flow, a request to reuse sensitive information or pressure to skip a verification step.

A polished interface can be copied. Reachability says that a service answered; it does not say who answered.

This is a verification checklist, not an endorsement

Cryptographic checks can reduce address-substitution risk. They do not guarantee the destination’s availability, security, legality or future conduct. Evaluate those questions separately and follow the laws that apply to you.

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.