Status legend // Tor // 2026
Torzon Mirror Status 2026: Checking, Dead & Live Explained
A Torzon mirror status is a small word doing a big job, and people read it wrong all the time. This page explains what checking, dead, and live mean on the card, how each node gets probed, and why a green marker is never the thing that keeps you safe. The exact strings stay on the card, so this page reads statuses instead of repeating them.
logged by Mira Kessel // checked 2026-10-09
torzonguqmlfy2kfi5tjbnt4bp3idtkjzi4qtupmhpdihjftomjtdzqd.onionOpen the mirror setWhat each Torzon status word means on the card
Every node on the card wears one of three markers. None of them is a safety rating. They describe the last time a person reached for the node, and nothing more.
The last hand probe did not get a clean answer. That happens often on hidden services and rarely means the node is gone. Move to the next one on the card and try again later.
We watched this string fail and left it on the card, struck through, so you learn to recognise a retired address instead of chasing it. Never open a dead node.
Reserved for a node a probe actually reached. You will rarely see it, because we would rather show an honest Checking than a green light that went stale minutes ago.
This three-word vocabulary is deliberately smaller than what some Torzon mirror trackers use. A five-tier scale with percentages and uptime graphs looks more precise, but a hand-run probe on a hidden service cannot actually support that precision honestly — it can confirm a node answered once, at one moment. Three honest words beat a false-precision dashboard.
How a Torzon mirror earns the status you see
A status is not guessed. It comes out of a short routine we run against each node. Knowing the routine tells you why Checking is the honest default and why a marker can lag behind reality by hours.
How probe frequency is set
Nodes are checked by hand rather than on an automated timer, so frequency depends on how often a person sits down to run the routine, not a fixed interval like "every 15 minutes." In practice that means the primary node gets checked most often since it carries the most traffic, while backup nodes may go longer between checks. This is a deliberate tradeoff: automated polling at scale is a fingerprinting and infrastructure signal in itself, and a slower, honest cadence beats a fast, spoofable one.
What a stale timestamp means
A timestamp that is a day or more old does not mean the status is wrong — it means nobody has re-run the check since then, and the node's real state may have changed in either direction. Treat a stale timestamp as reduced confidence, not as information that the marker is false. If a date looks old, cross-check the node yourself before relying on it, the same way you would verify the onion address itself. This is the same honesty rule the rest of this Torzon reference applies everywhere else: an admitted gap in freshness is more useful than a status that looks current but is not.
Why Torzon needs more than one working mirror
A single onion address is a single point of failure. Tor relay churn, DDoS pressure aimed at a specific hidden service, or the operator rotating keys can all make one Torzon address unreachable at a given moment while the market itself is otherwise fine. A short list of verified mirrors exists to absorb that, not to offer a "backup market" with different rules.
Every Torzon mirror should point at the same market
A legitimate mirror is not a separate Torzon — same catalog, same vendor accounts, same escrow, just a different onion address reaching the same backend. If a "mirror" behaves like a different market entirely (different login, different balance, different listings), treat that as a strong signal it is not a real Torzon mirror but a clone using the mirror framing to look legitimate.
Primary vs. failover, in practice
This card marks one node primary and the rest failover, which reflects which address Torzon's own operators lead with, not a ranking of safety. A failover mirror that passes the PGP check is exactly as authentic as the primary; it is simply the address to try second, typically because it sees less traffic and less attention.
Why we do not list every mirror rumor
Forum posts and paste sites routinely circulate additional "Torzon mirrors" that do not appear on this card. That omission is deliberate: we only publish an address here once it has been checked against the signed record. An unverified mirror is not automatically fake, but it has not earned a place on this card either — run it through the fingerprint check yourself before deciding.
How a Torzon mirror's status actually changes over time
The status column on this card is not a fixed label — it reflects the last check, and darknet market mirrors move between states for reasons worth understanding rather than treating as a black box.
Checking to Dead: what usually causes it
A mirror moving from "checking" to "dead" on Torzon's list most often follows a relay-level Tor issue, targeted DDoS traffic aimed at that specific hidden service, or a deliberate rotation by the operators ahead of retiring an older address. A single dead reading is not conclusive on its own; a pattern of repeated dead readings over consecutive checks is the stronger signal that a mirror is genuinely gone rather than momentarily unreachable through one Tor circuit. Background on how Tor relay selection and circuit health affect hidden-service reachability is covered in the Tor Project's own onion services documentation.
Dead to Checking: a mirror can come back
Unlike a domain seizure, which is generally terminal, a Torzon mirror marked dead due to Tor network conditions or temporary overload can return to a checking or live state once the underlying cause clears. Do not assume a dead mirror is permanently retired — but also do not assume it will return; treat the current card as the source of truth rather than memory of how a mirror behaved last week.
When a mirror disappears from the list entirely
A mirror that is removed from this card rather than marked dead usually means the operators have formally retired that address as part of a planned rotation, distinct from an address that is merely temporarily unreachable. Once an address is removed from the signed record, treat it as retired permanently — do not continue trying it, and do not trust a third-party source claiming it is still valid.
What to do when a Torzon mirror won't answer
A Torzon mirror going quiet is routine; Tor hidden services rotate relays and republish descriptors on their own schedule, and a legend built on manual probes will always lag a live network by some margin. Here is how to read a stalled mirror without treating it as an emergency, and without reaching for an unverified replacement address out of impatience.
One dead probe is not one dead mirror
If a Torzon mirror that verified cleanly last session fails to load, retry the same signature-checked address once after a short wait before assuming it is gone. A single failed connection attempt is frequently a dropped Tor circuit rather than a genuinely offline mirror, and this legend's own Checking badge already tells you the last probe, not the current second, is what the status word reflects.
When to actually move to a different mirror
Move to a verified backup only after a primary Torzon mirror has failed more than one honest attempt across a few minutes, not on the first timeout. Pull the replacement address from this card's signed set, never from a search result or a forum post, and run the same verification discipline against it that you would against the primary.
What changed recently on this legend
The status words themselves — Checking, Dead, and the deliberate absence of a hard-coded Online — have not changed since this legend was built, and are not expected to; they reflect a permanent decision documented above under how this page stays honest. What does change, mirror by mirror, is which specific Torzon address currently holds Primary versus Backup billing on the table on the card, which is why this page always points back to the live table rather than repeating addresses here.
Status questions people ask
Does a Checking mirror mean it is dead?
No. Checking means the last hand probe did not confirm the node yet. Onion routing is slow and hidden services drop in and out. Try the next node on the card before you assume anything.
Why not just show which mirror is online?
Because availability shifts from one minute to the next, and a pinned green light turns into a lie the instant the node drops. An honest Checking beats a stale Online.
How often are the mirrors probed?
By hand, not on a timer, which means a status can be hours old. The date on the card is the last time a person actually looked, so treat it as a hint, not a live feed.
Should I trust a mirror listed as Online more than one Checking?
Slightly, in that Online reflects a probe that actually succeeded recently. But it is still a snapshot, not a live guarantee, and both statuses require the same fingerprint match against the signed record before you connect to either.
What should I do if all nodes show Checking or Dead?
Wait and retry later rather than searching for an alternate mirror outside the signed card. An unverified link found through search carries far more risk than a temporarily unreachable verified one.
Why does this Torzon mirror list use words instead of a simple up/down icon?
A binary icon implies a certainty this page does not have. "Checking," "Online," and "Dead" each describe a specific probe outcome rather than a promise about the current instant, and spelling that out in words leaves less room for a glance to be misread as a guarantee than a colored dot would.
Can a Torzon mirror go from Online back to Checking without going Dead first?
Yes. A node that stops answering a probe moves straight to Checking, not to Dead, because a missed probe alone does not confirm the service is actually gone — it could be a routing hiccup, a restart, or a temporary Tor network issue. Dead is reserved for a node with a longer pattern of failed probes or a specific confirming signal.
Is the Torzon mirror list the same as the mirrors.json record linked elsewhere on this site?
Yes, this page presents the same underlying record in a readable, status-explained layout. The raw mirrors.json file is the machine-readable version of the identical data, useful for scripting a check rather than reading it as prose.
Back to the strings
Now that the words make sense, grab an address from the card, or read the door routine end to end. This Torzon mirror list pairs with the signature bench and the access guide — three pieces of the same verification habit, not three separate checks to pick between.