Pre-access review / five checks

Check the evidence before you open Mars

The highest-value decision happens before the destination loads: whether the route has enough provenance to justify opening it at all.

Pre-access sequence

Five checks in the correct order

01

Identify the source of the address

Record where the candidate route came from and when it was published. Search results, directories and forwarded messages are discovery sources, not identity proof.

02

Establish the signing key separately

Compare the complete fingerprint through an independent path. A public key downloaded beside the address can authenticate only itself.

03

Verify the signed statement

Confirm that the exact hostname appears inside the signed bytes and that the verifier reports the fingerprint you established in step two.

04

Isolate the browser session

Use a current Tor Browser, avoid extensions and keep unrelated identities out of the session. Browser hygiene reduces cross-context exposure but does not authenticate the site.

05

Inspect before entering credentials

Re-read the full hostname, note unexpected redirects and stop at any recovery, deposit or login flow that conflicts with the evidence you checked.

What opening proves

Reachability is a transport result

If a page loads, you have learned that a route responded. You have not proved who operates it, whether the interface is original, whether its policies are current or whether future actions are safe.

A phishing clone can be faster, cleaner and more available than the intended service. That is why route status belongs after provenance, not before it.

LoadsThe network found a responding service.
Looks rightVisual assets may have been copied.
Accepts loginA form can collect credentials without proving identity.
Matches evidenceOnly an exact, independently verified chain improves confidence.

Common mistakes

Shortcuts that break the check

Similarity

Checking only the first characters

Vanity prefixes are easy to imitate. Compare the entire hostname from the signed statement.

Circular proof

Taking the key from the route

A clone can publish its own key and produce valid signatures. Provenance must come from elsewhere.

Session risk

Reusing identities or passwords

Verification cannot rescue a credential already exposed to another route or service.

Explicit handoff

Continue only after reviewing the evidence

This publication does not display a destination address. The route starts in this tab only after you press the button below.

Check the hostname. A familiar design is not proof of identity.

Protect credentials. Stop if the route or login flow differs from your evidence.

Keep claims separate. Reachability does not establish legitimacy or safety.