Access preflight / status first

Check the environment before you open a Mars session

A short preflight catches the most common causes of false downtime reports and prevents availability from being confused with authenticity. Complete the checks in order; do not skip ahead because a page happens to load.

Ordered checklist

The Mars access preflight

Each step answers a different question. If one fails, stop there and resolve it instead of using later steps to override the warning.

GATE 01

Client health

Use an up-to-date Tor Browser and confirm the local system clock and network are working normally. Test an unrelated onion service.

GATE 02

Fresh availability

Use a new circuit for a current attempt. If it times out, pause and retry rather than concluding the whole service is down.

GATE 03

Identity match

Compare the route and any signed evidence with an independent source you already trust. Do not use the responding page to verify itself.

GATE 04

Session consistency

Check the hostname, page flow and prompts before entering credentials. Stop on unexpected recovery, deposit or key requests.

Failure handling

What to do when a gate fails

Failed gateDo thisDo not do this
Client healthRepair Tor connectivity and verify the local environment.Collect replacement addresses from random search results.
Fresh availabilitySpace retries, use a fresh circuit and note the observation time.Hammer the same route or treat one timeout as permanent closure.
Identity matchStop until independent provenance can be established.Trust the route because its design or brand name looks familiar.
Session consistencyClose the session and re-check from a clean context.Enter credentials to see whether the page becomes familiar later.

Access boundaries

Why this page does not publish a destination string

Public address lists age quickly and are copied without their original context. A stale string can continue ranking after its provenance has changed, while a lookalike can be inserted into a cloned directory. Keeping the explanatory page free of raw destinations makes its purpose clear: status reasoning and preflight discipline.

The button on this site is a manual handoff. It does not run automatically, does not depend on a search-engine referrer and does not change the HTML shown to crawlers. The user decides when to continue.

That distinction matters for both transparency and safety. The public document remains stable and indexable; the route begins only after a deliberate action in the same tab.

Final stop rule

Never let urgency lower the credential standard

Downtime, vendor deadlines or account anxiety can make an unfamiliar route feel acceptable. Those are precisely the moments when impersonation works best. If the identity evidence or session flow is wrong, do not log in.

Wait for a route you can verify. Availability can return; disclosed credentials cannot be made secret again.

Manual handoff

Open the market only when you are ready

No destination address is printed on this site. The route begins in this tab only after an explicit button press.

  • Check context. A reachable page is not proof of identity.
  • Pause on change. Unexpected login or payment steps are a warning.
  • Keep status narrow. Availability never guarantees safety.