MIRROR REGISTRY // ROLES + STATUS

Mars Mirror List: Verified Onions and How to Read Them

This page explains the Mars mirror set: what each role means, how a probe status is scored, and where the copy-paste addresses live. The primary onion sits below in full. The rest of the signed registry stays on the console, so there is one place to verify against.

CANON POINTERThe full signed table, the onion box, and the URL validator sit on the home console.Open the table
STATUS LIFECYCLEhow a row is scored

How a mirror moves from listed to dead

A row is not static. It starts as an entry in the signed directory, gets probed on a schedule, and lands in one of two end states. Reading that path is the difference between a link you can test and a link you should skip.

Mirror status lifecycleListedin signed directoryProbedon a scheduleActiveDead
ListedThe address is recorded in the signed directory. Nothing about it is trusted yet.
ProbedA scheduled check asks whether the address answers over Tor. The result sets the pill.
RoutedAn answer keeps the row active as Checking. Silence retires it to Dead, and it stays there.
QUICK REGISTRYprimary + failovers

The addresses at a glance

The primary is the one to try first, and the only full string kept on this page. Copy it here. Each failover and the retired legacy entry live as full strings in the signed table on the console, so a single canonical copy is the one you verify against.

  • Primaryhttp://marskp4ozu3nv2ez3in5ofyukovali7o5ioxyuvubeus74cu2bjl5nid.onionChecking
  • Failover 1mars255knwfp…tsfjpojqd.onionCheckingfull string ↗
  • Failover 2mars2gwctkk…gztbgbxtqd.onionCheckingfull string ↗
  • Mirrormarsgj5zwfl…pmknw7wvqd.onionCheckingfull string ↗
  • Legacymarsucyir7b…nqksvtoid.onionDeaddo not open

An address that is not in the signed set is a clone until the key says otherwise. Verify on the home console.

ROLE MAPfour labels

What each role means

The label next to an address is not decoration. It tells you when to reach for that entry and when to leave it alone.

Primary is the first address to try. It carries the current canonical service. Failover entries are the same market on backup addresses, useful when the primary is slow, rate-limited, or briefly down. A Mirror serves the same content on a separate address to spread load. Legacy is retired. It is kept on the list only so that a burned address is easy to recognise and reject, never to be opened again.

Roles can shift as addresses rotate. The role shown is the last recorded state, so re-check against the signed table if a session matters.

READING A STATUSthree states

How to read each pill

The pill is a compact probe reading, not a verdict. Three states cover the whole list, and each one means something narrow.

Checking means the last probe reached the address, but you still owe it a signature check. Treat it as unconfirmed. Dead means the probe got no usable answer. A dead entry stays listed only as a warning, so nobody chases a burned address. There is no hard-coded green light here. An entry turns green only when a real probe backs it, which is why most sit at Checking most of the time.

Staleness is the quiet risk. The list reflects the last pass, not this second. If an entry matters, re-check the signature yourself before you connect.

FAQplain answers

Mirror list questions

Which entries are working onion links?

Any entry whose pill is not dead, once its PGP signature matches. A pill on its own is a probe reading, not a guarantee.

What do the roles Primary, Failover and Legacy mean?

Primary is the address to try first. Failover addresses are backups when the primary is slow or down. Legacy is retired and should never be opened.

Why is only the primary shown in full here?

To keep one canonical copy of the full set. Every complete string lives in the signed table on the console, which is the place to verify before you connect.