torzon: catalogue record and onion addresses

torzon publishes one primary address and four mirrors. All five lead to the same platform. A mirror exists so the project stays reachable when one address is under load or being attacked, so treat the whole set as equal rather than hunting for a newer one.

Copy a string, then read it back against a second source before you connect. The addresses here are the only ones torindex ties to torzon.

First recorded here means the date torindex started keeping the entry, not the age of the market. torindex does not backdate.

A single address is a single point of failure. When a project keeps only one, a sustained attack on it knocks the whole thing offline until a replacement is announced, and that announcement window is exactly when fakes appear. Several mirrors spread the load and buy time, so pressure on one address does not force a scramble for a fresh link that scammers can then imitate.

For a reader the rule is short. Treat all five as equal. If the primary is slow or refuses to load, work down the list rather than trusting a sixth address you found somewhere else. A sixth address is not on this torindex record, and anything off this torindex record starts with no trust at all.

Known addresses

Each address on this torzon record entered the file the same way: submitted or found in circulation, then held as unconfirmed until it cleared the checks below. torindex does not list an address on reputation or forum chatter alone — every string above passed a character-level review before publication.

How we verified this torzon record

Verification for this torzon entry runs the standard torindex method: confirm each onion resolves and serves the expected torzon platform rather than a parking page, diff the full string against any previously confirmed copy, and note the date of that check plainly rather than implying it is current forever. The "last confirmed reachable" field above reflects exactly that check, not a live status feed.

Status history for this torzon entry

This torindex record for torzon shows one confirmation pass as of 2026-08-17. As with every torindex entry, a status change — an address going dark, a new mirror appearing, a PGP fingerprint publishing — updates this page and its dated fields rather than silently overwriting the record. Readers checking back later should expect the "first recorded" date to stay fixed while "last confirmed" moves forward with each re-check.

A torindex record is only as good as your own checking. Compare the address above with a second independent listing. When the signature layer is live, match the signed fingerprint too. If two trusted sources disagree, stop and treat both as suspect until the conflict is resolved.

The button opens the project site in the clear. Inside Tor, use the onion addresses above.

Verifying the torzon address above is the first check, not the only one. What happens after you connect — how you pay, and how you store the credentials that protect your account — is entirely outside what a torindex record can check, and it matters just as much.

Why payment currency choice is a real security decision

Most onion market vendors and operators, torzon included based on public discussion of the project, accept Monero alongside more traditional cryptocurrencies specifically because a transparent public ledger can retroactively link a purchase back to a wallet and, from there, to a person. torindex is not a financial advisory and does not verify torzon's actual payment implementation, but the general principle — that payment privacy is a separate concern from address verification — applies to every onion market a reader might use, not just this one.

Keeping a PGP key and login credentials somewhere safer than a browser

Anyone verifying an onion market address against a project's PGP-signed canon needs somewhere secure to hold that key, along with account credentials, without retyping them from memory. KeePassXC is a widely used, offline password manager built for exactly that kind of sensitive local storage, independent of any cloud sync that could become a separate point of failure. Neither Monero nor KeePassXC is affiliated with torindex or with torzon; both are named here because they address a real gap the torzon record above cannot close on its own.

This torzon record did not start with five addresses. It started with the primary address alone, entered after the standard torindex reachability check described on the methodology page. The four mirrors were added to the torindex record only after each one independently passed the same check — resolves over Tor, serves the torzon platform rather than a parking page or an unrelated service, and diffs clean against any copy already on file. torindex does not add a mirror to a record on the strength of a forum post claiming it is genuine; each string above earned its place the same way the primary address did.

Why the mirror count matters more than the mirror count alone suggests

A reader skimming this torzon record might see five addresses and assume more is simply better, the way more listings looks better on a scraped aggregator. That is not quite the right read. Five addresses exist because torzon, like most active marketplaces, treats a single point of failure as an operational risk worth hedging against — sustained pressure on one address should not take the whole platform offline. torindex records that reality rather than picking a single "official" address and ignoring the rest; all five are equally part of the canonical set until one is retired.

What torindex does and does not track about mirror history yet

Right now, this torindex record shows two dated fields per address: when the entry was first recorded here, and when it was last confirmed reachable. What it does not yet show is a full change-log of every mirror addition, rotation, or retirement over time — that level of granular history is on the torindex roadmap alongside the two-of-three signature layer described on the methodology page, and it is not implied here before it actually exists. If a mirror above is ever retired, this record will say so plainly with the date, the same way a retired market moves to the graveyard with its last-checked date intact rather than being silently deleted.

What to do if you find a torzon address not on this record

An onion address for torzon that does not appear in the five above is not automatically fake, but it also has not cleared the torindex pipeline, which means it carries no verification weight from this torindex record at all. Treat any sixth address the way you would treat an unverified claim generally: do not act on it until it either appears here after review or you have independently confirmed it against torzon's own signed channel.

It is worth being precise about what a torindex record does and does not claim, since "on file" could easily be read as a broader endorsement than torindex intends. This torzon record is torindex's narrowest possible claim: these five specific strings resolved over Tor and served the torzon platform as of the date shown.

What torindex does vouch for on this torzon record

torindex vouches for exactly one thing on this page: character-for-character accuracy of the five addresses above, each independently confirmed reachable and matched against the torzon platform rather than a parking page, a clone, or an unrelated service. That confirmation is what "on file" means everywhere torindex uses the phrase, on this torzon record and on every other torindex entry.

What torindex does not vouch for on this torzon record

torindex does not vouch for torzon's escrow reliability, dispute-resolution track record, vendor quality, or long-term operational security — none of that is observable from outside the platform, and torindex does not pretend otherwise by implying it through a favorable-sounding status word. A torindex Checking status is not a safety rating; it is a dated confirmation of one narrow fact, repeated here because it is the single most commonly misread claim on any torindex market record.

Why torindex draws the line exactly here

torindex draws this boundary the same way on every record, torzon included, because a directory that quietly expands its own claims past what its verification method can actually support stops being trustworthy for the one thing it can genuinely check. Readers who want an assessment beyond what torindex can honestly offer should look elsewhere for it; torindex would rather be narrow and accurate than broad and wrong.