Mirror availability / preserved path

A Mars mirror list is useful only when its evidence is fresh

This page preserves the established Mars mirror-list intent while removing raw destination strings. Its purpose is to explain how availability records should be assessed before a route is trusted or opened.

Mirror record anatomy

Four fields a credible availability record needs

A long list is not automatically a good list. The value comes from provenance, recency and a clear account of how each observation was produced.

01 / OBSERVED

Timestamp

The record should state when a route was tested. “Online” without time can remain visible long after the condition changed.

02 / METHOD

Check conditions

The reader should know whether a fresh Tor circuit was used, how long the checker waited and what counted as a response.

03 / RESULT

Narrow outcome

A response, timeout or protocol error is an observation. Labels such as safe, official or verified require different evidence.

04 / PROVENANCE

Independent identity

The source of the route must be checked separately. Availability cannot transform an unknown address into an authentic one.

05 / HISTORY

Repeated pattern

Several observations reveal whether a route is stable, intermittent or consistently silent. A single row cannot show that pattern.

06 / SCOPE

Explicit limits

A responsible directory says what it did not test: login behavior, account safety, payments and operator control.

Compare carefully

Mirror status is not a leaderboard

Response time varies with the circuit, geographic path and load. Small timing differences do not establish that one route is safer or more legitimate.

Prefer repeatability over speed

A route that responded once in two seconds may fail on the next circuit. A slower but repeatedly responsive route can provide stronger availability evidence, but it still needs the same identity check.

Treat silence as a temporary state

A timeout can reflect descriptor propagation, circuit construction or service load. Record the result and retry later rather than permanently declaring a route dead from one attempt.

Reject copied tables

A mirror list copied without timestamps or method inherits none of the original evidence. It is merely a set of strings, and strings are easy to replace.

Mirror list questions

What readers usually need to know

Why are no Mars onion addresses shown here?

The status desk separates public explanatory content from the destination handoff. This reduces stale copied strings and keeps the page focused on availability methodology.

Does an answering mirror prove that it is official?

No. An answer proves only that something responded. Identity must be established through independent, expected evidence.

Should the fastest route always be used?

No. Circuit speed changes from attempt to attempt and is not an authenticity signal. Consistency and provenance matter more.

What if every known route is silent?

Confirm that Tor works elsewhere, retry with spacing, and wait for better evidence. Do not lower the identity standard to find a replacement quickly.

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.