Primary front
The address the market expects most traffic to use. It carries the freshest descriptor and is the first thing our probe checks each cycle.
Mirror Directory
Mars Market
Mars Market
Mirror Directory
A reachability log for the Mars Market onion fleet. We track which front addresses answer a Tor circuit, how the failover set rotates under pressure, and how long each descriptor has been live — so you always start from an address that was confirmed reachable, not one copied from a forum.
Front onions tracked5
Answering nowPRIMARY LIVE
Descriptor ageROTATING
Probe methodTor SOCKS circuit
Address formatv3 .onion (56ch)
How the fleet is built
One market, several front doors
Mars runs a small set of independent v3 hidden services that all terminate at the same marketplace. They are not separate sites and they do not hold separate accounts — they are redundant front doors, published so that losing any one of them does not take the market offline.
Failover set
Several standby onions that stay published but quiet. When the primary struggles to build circuits, these absorb the load until its descriptor republishes cleanly.
Rotation under pressure
Introduction-point flooding targets one address at a time. Rotating which front we recommend keeps the attacker chasing a moving target instead of knocking the market down.
Reading a status row
What each column actually means
A mirror table is only useful if you know what it is claiming. Here is how to interpret ours before you trust any single row.
| Column | What it reports | How to use it |
|---|---|---|
| Address | The full 56-character v3 onion | Copy it whole — never retype or shorten |
| Role | Primary front or failover | Start with primary, fall back only if it will not load |
| Last answered | When the descriptor last replied to a probe | Fresh = confirmed reachable; stale = unconfirmed |
| Circuit result | Whether a Tor circuit built end to end | A built circuit is the only real reachability signal |
Mirror questions
Common mirror questions
Why does the recommended address change between visits?
Because reachability changes. When a front onion is under introduction-point pressure, we promote a failover that is answering cleanly. The market behind every address is the same, so a changed recommendation is a routing decision, not a new destination.
A mirror loaded yesterday but not today — is it dead?
Not necessarily. Hidden service descriptors expire and republish on a cycle, and a node under load can miss a republish window. Try a failover, then re-check the original later. Permanent removal only happens after repeated failed cycles.
Does a reachable mirror mean it is the genuine Mars?
No. Reachability and authenticity are different questions. A clone can be perfectly reachable. An address is only genuine when it also matches the PGP-signed canon — confirm the signature before you trust any front, however quickly it loads.
Is this directory affiliated with Mars Market?
No. This is an independent reachability log kept for research and reference. We hold no funds, take no commission, and operate none of the mirrors we track.