Deep Web WireOnion address desk
Wire

Vortex onion address, links and mirrors for 2026 — Deep Web Wire record

Marketplace Unknown Address record

Vortex publishes three onion addresses. Because our last measurement is stale, this record honestly reads unknown rather than guessing a status we cannot back up.

This record shows all three Vortex strings, and it shows an honest unknown rather than a status we cannot prove. Copy an address, confirm it against a source you trusted first, and open it yourself.

Access box — Vortex onion addresses

Unknown does not mean down. It means our most recent check is too old to report as fact. When a fresh measurement lands, the status word here changes — we never leave a stale up on the page.

Current status: Unknown  last reviewed 2026-08-24

Primary
vortexqttelw7m627vd25uhzielmoqbbbep6xn3hoa6re2xiac3tomad.onion
Mirror 2
vortext2pim3tsbfwi26zb33xeuxrocicjnjw32vdwqqn2pd7atv3nqd.onion
Mirror 3
vortex7e5d5qekpkmnjy2bkt7afzwrzhtyup5bozej7dy34syimnxsyd.onion

This button is an inert placeholder and performs no action yet. Routing and verification are handled by a separate layer. For now, copy an address above and open it in Tor Browser by hand.

Phishing warning. An outdated status is its own hazard: a reader who assumes unknown means dead may go hunting for a ‘replacement’ that is really an impostor. Do not chase a fourth address. Test the three here first.

How to reach Vortex safely

  1. Install Tor Browser from the Tor Project before anything sensitive istyped anywhere.
  2. Copy one of the three addresses with its button so no character is left to chance.
  3. Because our reading is stale, expect to test more than one string; unknown means untested here, not broken.
  4. When one answers, save it as a Tor bookmark and treat that saved copy as your future starting point.

Why Vortex is set up this way

Vortex keeps three addresses, which is enough redundancy to ride out a takedown without becoming a list too long to remember. The more useful thing to understand on this page is the status word: we mark Vortex unknown because our last reachability reading is too old to repeat as fact. That is an honesty flag about our data, not a verdict on the three strings, which remain equal entrances to the same platform.

Payments and what we track

Vortex runs a standard escrow flow over Tor. Payment options are the project's own; this page limits itself to the addresses and whether we could reach them.

What this Vortex record does not claim

Vortex in this record is the darknet marketplace — not the optics brand, not the game mod manager, and not a misspelling of vertex.

We track the address, not the business behind it. Nothing here says Vortex is honest, solvent, or safe to trade on. The claim is narrow: this is the string we currently tie to the project, and it changes the moment that stops being true.

Verify then connectCopyCompareMatchConnect

Vendor and category mix

Escrow marketplaces in this class typically group listings into department-style categories rather than a flat, undifferentiated feed — a structure meant to help buyers narrow a large catalog, not a signal of legitimacy on its own. Vortex is no exception in shape: the storefront is organised the way most Tor marketplaces in this era are, with category filters, vendor pages carrying a trade history, and a search bar layered over the listing set.

What the department structure typically looks like

A typical department layout on a market like Vortex separates listings by product type, then again by vendor, so a buyer can filter down before ever opening an individual page. That structure is common across this class of marketplace and is not unique to Vortex — it is closer to a shared convention than a differentiator, and we mention it here only so readers know what to expect from the interface, not as an endorsement of anything sold through it.

Why Deep Web Wire does not rank or review Vortex vendors

This record stops at the address. We do not browse, catalog, rate, or recommend individual vendor pages on Vortex, and we would not publish a vendor ranking even if we did — a ranking implies an endorsement of trade, which sits outside what an address-and-status reference is for. Anything you read about specific listings or sellers should come from sources built for that purpose, not from this page.

What the category mix does not tell you about legitimacy

A well-organised catalog is not evidence that a marketplace is safe, honest, or free of exit-scam risk. Category structure is a usability feature copied across dozens of Tor markets regardless of how any individual project has historically treated its users. Judge Vortex on the same terms you would judge any escrow platform — independent of how tidy its listing pages look — and keep that judgement entirely separate from the one fact this page actually verifies: which onion string currently belongs to the project.

Escrow, disputes and what this record does not track

Vortex runs on a standard escrow model typical of Tor marketplaces: funds are held by the platform until a buyer confirms receipt or a dispute is opened and resolved by staff. That mechanism belongs entirely to Vortex, and Deep Web Wire has no visibility into it, no relationship with its outcome, and no way to verify individual dispute claims either way.

What we cannot verify about a given trade

We cannot confirm order histories, vendor reputations, dispute outcomes, or refund claims for Vortex or for any project on this wire. Those events happen inside the platform itself, often behind a login this record does not have and would not want. If a dispute matters to your decision to use Vortex, resolve it through the platform's own process; this page has nothing to add there.

Why the escrow model doesn't change how we track the address

Regardless of Vortex's dispute process, deposit terms, or vendor policies, the only fact this record commits to is the onion address and whether our last check reached it. A market with a well-regarded escrow process and a market with user complaints receive an identical level of scrutiny here: we check the string, not the reputation.

Verification history: how this Vortex record was built

A record like this one is only useful if a reader can see how it was assembled, not just what it currently says. Below is the honest version of that process for the Vortex entry — expand each note for detail.

How each mirror on this record was sourced

Cross-checked before publication

No address on this page was added because a single forum post claimed it. Each string above was cross-referenced against more than one independently maintained source before it was published here — typically the project's own channel plus at least one outside mirror tracker reporting the same string. An address that only ever appears in one place, however plausible, does not clear that bar on its own.

What would get a mirror removed from this list

Three removal triggers

Three things trigger a removal: the project itself announces a retirement of that mirror, the address stops resolving over an extended check window rather than a single blip, or independent reports converge on it being a copycat rather than a genuine Vortex mirror. We would rather leave a dead entry flagged than delete history silently.

Why a reader-submitted extra mirror doesn't get added on request

Submissions are not evidence

We get occasional messages proposing an additional Vortex mirror. A submission alone is not evidence — anyone can claim any string belongs to any project. Until an address clears the same cross-reference bar the existing ones did, it stays out of the record rather than being added provisionally and quietly walked back later.

How Deep Web Wire tracks Vortex, specifically

Deep Web Wire does not treat every project on this wire identically — Vortex's entry is built from the sourcing method that fits how Vortex itself publishes its address, and Deep Web Wire notes that method explicitly rather than applying a generic template across every market.

What makes the Vortex entry on Deep Web Wire different from a copied listing

A copied listing repeats an address with no sourcing. Deep Web Wire's Vortex record states where that address came from, when it was last confirmed, and what would change the status word above — the same discipline Deep Web Wire applies across its entire wire, applied here to Vortex specifically.

Why Deep Web Wire keeps re-checking Vortex instead of treating this record as finished

An address that was correct when Deep Web Wire last confirmed it is not guaranteed correct indefinitely. Vortex, like every project on this wire, can rotate its address, and Deep Web Wire's process exists to catch that rotation and update this record rather than let a stale address sit here looking current.

One more sourcing note

Readers sometimes ask why Vortex’s record looks the way it does compared with a market running a longer mirror list. The short answer is that address count follows the project’s own operational choices, not a Deep Web Wire preference: Vortex currently has three on file, and that number can change the moment the project rotates, expands, or consolidates its public entrances. When it does, this record updates to match — we would rather publish a smaller, accurate list than pad it with anything unconfirmed just to look more complete.

How Vortex compares across the wire

Deep Web Wire tracks seven projects with the same discipline: one record per project, addresses published as copyable text, and a status word that reflects our last honest reading rather than an assumed uptime. Vortex sits alongside the following on that same wire.

Why address counts differ between projects

Address count is a project's own operational choice, not a Deep Web Wire ranking. A market running several mirrors is not more trustworthy than one running a single guarded address; the two approaches trade off differently between redundancy and the number of strings a reader has to check.

Frequently asked questions

Does unknown mean Vortex is down?
No. Unknown means our most recent check is too old to report as current fact. Test the addresses yourself; they may well answer.
How many Vortex addresses are real?
Three, all listed here and all equal. A fourth found elsewhere starts from no trust regardless of how it is presented.
When will the status update?
When a fresh measurement lands. Until then we leave unknown in place rather than printing a stale up.
Does an unknown status mean I should avoid Vortex entirely?
It means our own measurement is stale, not that Vortex is unsafe or offline. Test an address yourself if the current reading matters to your decision.
Are all three Vortex addresses equally official?
Yes. None of the three carries more authority than the others; each was cross-checked the same way before being added to this record.
What happens to a Vortex address that stops resolving?
It stays flagged rather than being silently deleted, following the same removal process this wire applies to every tracked project.

Record last reviewed 2026-08-25.