PGP · provenance · exact comparison

Verify a Mars Market link before you trust it

A valid-looking onion hostname, a familiar layout and a page that loads are not proof of identity. This reference explains how to connect a Mars Market link to a signed statement and an independently established key.

Four separate checks must agree

PGP verification is useful only when the message, signature, public key and key provenance are evaluated together. Skipping one layer can produce a technically valid result for the wrong identity.

01

Recover the original statement

Find the announcement in its original context. Screenshots, snippets and forwarded messages can omit dates, signatures or replacement notices.

02

Establish the key separately

Compare the complete fingerprint through an independent path. A key bundled with the same untrusted mirror list does not establish identity.

03

Verify the signed bytes

Use GnuPG or another maintained OpenPGP implementation. Confirm a good signature and inspect which fingerprint produced it.

04

Compare the full hostname

Match every character from the signed statement. A similar prefix, suffix or visual shape is deliberately easy to fake.

Integrity is not the same as trust

A valid signature shows that a particular private key signed a particular message and that the signed text was not changed afterward. It does not prove that the key belongs to the operator you intended unless you already established the fingerprint from an independent source.

It also does not certify uptime, future conduct, platform security or the safety of any transaction. Those are different claims requiring different evidence.

Good signatureMessage matches the signing key
Known fingerprintKey identity was checked elsewhere
Signed hostnameAddress appeared in that statement
Page respondsRoute is reachable right now

A practical verification sequence

1

Save the evidence

Keep the signed message, detached signature when used, publication location and claimed fingerprint together. Verification without the original bytes is not reproducible.

2

Import deliberately

Inspect a key before trusting it. Keyserver presence, creation date or a convincing user ID are metadata, not proof of ownership.

3

Read the verifier output

Confirm the signature is cryptographically good, then compare the reported fingerprint. A “good signature” from an unexpected key is still the wrong result.

4

Re-check after rotation

A new mirror is a new value. Repeat the source, fingerprint, signature and exact-hostname checks instead of extending trust from an older address.

Do not let one strong signal replace the whole chain

Phishing pages can use valid onion syntax, polished design, TLS on a clearnet pre-landing page and even a perfectly valid signature made by an attacker-controlled key. Verification succeeds only when the complete fingerprint is already tied to the identity you meant to reach.

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.