About Oniongate: An Independent, Ad-Free Onion Status Board (2026)

Why oniongate exists

Most link pages tell you an onion address and stop there. They cannot tell you whether it works this minute, and a dead or hijacked mirror looks identical to a healthy one until you connect. That gap is where people lose money and get phished. A board that measures reachability in real time closes it, as long as the board is honest about what it does and does not know.

So oniongate's scope is deliberately small. Oniongate is not a directory, not a review site, and not a guide. It does one thing and tries to do it without lying.

How oniongate stays independent

Independence here is not a slogan, it is a set of things we refuse to do. The board carries no advertising, so no operator can buy a friendlier reading. There are no affiliate links, so we earn nothing when you connect anywhere. Placement is not for sale, and there is no placement to sell, because the board is not ranked. Order follows the data, not a deal.

• No ads. The layout has no ad slots and never will.
• No affiliate revenue. We are not paid when you visit a service.
• No paid placement. Nobody can pay to look more online than they are.
• No hand-set statuses. Every reading comes from a probe, or it reads unknown.

Where the addresses oniongate publishes come from

Oniongate does not create onion addresses. The ones oniongate monitors are drawn from a signed directory that publishes them under a 2-of-3 quorum, and oniongate's own job is only to annotate that list with live measurements. This matters for your safety: if an address is not in the signed list, it is not one oniongate vouches for, and it is not one you should trust just because it appears somewhere near the oniongate name.

Being wrong, in public: oniongate's policy

A probe can misfire. A circuit can be slow. When our reading is wrong, the honest response is a better measurement, not a quieter one. Readings age into unknown when the feed goes quiet, so the board never freezes on a stale green. If you think a reading is mistaken, the methodology explains exactly how a check is scored, and the per-service pages show the raw endpoint data behind each summary.

What oniongate does when a reading is disputed

Oniongate checks the raw probe log for that endpoint first, since the fix always starts with the measurement, not the display. If the log shows the probe genuinely got a different result than what a person saw with their own connection, that is usually a routing difference between two separate paths through Tor, not an error on either side — we note it and keep watching, rather than quietly overwriting a reading to match a single report.

Why oniongate would rather be quiet than wrong

The failure mode oniongate is most protective against is not "the board is slow to update" — it is "oniongate confidently shows something false." Every design choice on oniongate, from unknown-by-default to no hard-coded online badges, trades a little responsiveness for a lot less risk of publishing a claim oniongate cannot back with an actual measurement.

What you can check yourself, without trusting oniongate on our word

Independence claims are cheap to make and hard to verify from outside. Rather than asking a reader to simply believe oniongate is neutral, this page points at what is independently checkable.

The probe method is documented, not a black box

The methodology page describes exactly how a check runs and how a status word gets assigned, in enough detail that the process itself is auditable. Nothing about how a reading becomes Online, Checking, or Down is left as an unexplained internal decision.

Every address is shown in full, plain text

Each market's status page shows its onion addresses as copyable plain text rather than a shortened link or an image, specifically so you can independently verify one against a signed record maintained by that market's own operator — entirely outside anything oniongate itself publishes.

The ordering rule applies the same way to every market

Whatever fixed rule sorts a table or a board on this site applies identically across all seven tracked markets, with no manual override for any single one. That consistency is easier to check by comparing pages against each other than to simply take on faith.

Tools oniongate expects a careful visitor to already use

A reachability reading from oniongate is only one input in a much longer safety habit. Oniongate does not build or bundle any of the software below — it simply assumes a visitor arrives with a working toolchain, the same way any honest status board should.

PGP verification, not a status dot

Oniongate can tell you an onion address answered a probe; it cannot tell you the address is genuinely operated by the market it claims to be. That verification step belongs to PGP, not to a green dot. GnuPG is the reference implementation most guides point to for checking a signed fingerprint against a market's published key, and a password manager built for the job, such as KeePassXC, is a better place to store the resulting long strings than a text file or a note app.

An isolated, amnesiac operating system

Oniongate itself runs over plain Tor and makes no claim about the operating system a visitor should use, but the projects most guides converge on are Tails, which boots from removable media and forgets everything on shutdown, and Whonix, which isolates the Tor process from the workstation entirely so a single application bug cannot leak a real IP address. Neither is a oniongate product; both are widely reviewed independent projects worth reading about before treating any onion market as safe to browse casually.

A general reading list beyond oniongate

For a broader, non-market-specific view of the same operational-security habits oniongate assumes, Privacy Guides maintains an actively updated set of recommendations that go well past what a single status board can cover on one page.

The onion markets oniongate currently tracks

Oniongate's board currently follows seven onion markets, each with its own status page carrying the full mirror list, uptime rollups, and an honest Unknown state whenever the probe feed has nothing fresh to report. This about page does not repeat their individual readings — that detail lives on each market's own status page — but it is worth naming the roster here for anyone who lands on /about/ first.

The seven are torzon, wethenorth, nexus, vortex, omega, mars and drughub. Oniongate treats all seven identically: the same probe cadence, the same signed-directory sourcing rule for addresses, and the same refusal to hand-set a status word for any one of them over the others. Adding an eighth market to oniongate's roster would follow the identical process — sourced from a signed directory, probed on the same loop, never fast-tracked because someone asked.

Why "darknet market" is the term this page uses, precisely

Oniongate tracks darknet markets specifically: marketplaces reachable only as onion services routed over Tor, not any site that happens to sell something restricted on the open web. A darknet market in this narrow sense has no clearnet storefront standing in for the real listing platform — the Tor onion address is the only front door, and that address, not a mirror or a lookalike domain, is what oniongate actually probes. A status board that blurred "darknet market" into any restricted-goods website would be measuring a much fuzzier, less checkable claim than the one oniongate makes: does this specific onion address answer over Tor right now.

What changes, and what does not, as this darknet market roster grows

Every darknet market added to oniongate keeps the same shape: a signed onion address, probed over Tor on the shared cadence, reported as one of four honest status words. What changes with a larger roster is only the number of tracked markets, never the process a market goes through to be tracked. A visitor comparing two markets on oniongate is comparing two identically-measured onion services, not two markets scored by different rules because one has been on the board longer.

About oniongate: questions people ask

Who runs oniongate?

A small independent operation, not a market, a vendor collective, or a marketing arm for any of the services it tracks. The methodology page documents the probe process in enough detail that the "who" matters less than whether the method itself holds up to scrutiny.

Does oniongate accept payment to list or promote a market?

No. There is no paid placement, no featured slot, and no mechanism to move a service up in any listing on this site — every table and board here is ordered by a fixed rule (alphabetical-adjacent by signed-directory addition), never by who paid for visibility.

How do I report an incorrect reading?

Check the per-service status page first for the raw probe history behind the summary, then compare it against what you observed. Persistent, reproducible discrepancies are worth taking seriously; a single anomalous reading is more often a routing difference than a measurement error.

Why does this site look so sparse compared to a typical market-review blog?

Because it deliberately is one. A review blog can pad word count with opinion and speculation; a measurement board should not claim more than it has actually measured. What looks sparse is the byproduct of a strict rule: no manufactured content standing in for a real probe result.

A worked example: what happens if an operator asks oniongate for an early fix

Say an operator behind one of the onion addresses on this board emails us, in good faith, to say their service came back online an hour ago and asks whether the reading can be updated now instead of waiting for the next scheduled probe. It is a reasonable request from their side. The answer is still no, and it is worth walking through why, because the reasoning is the same policy that keeps every other reading on oniongate honest.

What actually happens to the request

The email gets a short reply pointing at the probe interval published on the methodology page, and nothing else changes. We do not have a mechanism to hand-set a status word outright — there is no admin toggle that flips an onion service from Down to Online on request, because building one would mean every reading on the board is only as trustworthy as our willingness to say no to whoever asks nicely. The next scheduled probe runs on its normal cadence, and if the endpoint answers, the status updates on its own, the same way it would for a service nobody had emailed us about at all.

Why the policy does not bend, even for a true claim

The operator in this example might be telling the complete truth. Their service might genuinely be back. That is not the point. The moment a status board starts accepting operator-reported readings as a shortcut around measurement, it stops being a probe log and becomes a bulletin board that operators can influence by asking — and there is no honest way to accept a true early report from one operator without also becoming a channel a dishonest one could use to get a false reading published faster than our own check would ever produce. Refusing every early-update request equally, true claims included, is what keeps the refusal meaningful.

Reading the oniongate board next to a market’s own status page

Some onion services publish their own uptime claim on their own front page. That number and the reading on oniongate are not competing for the same job, and treating them as interchangeable misses why an independent board exists at all. A market's self-reported status is written by the market; ours is produced by a probe that has no relationship with the market and no reason to flatter it. Neither reading replaces the other — a self-reported figure can be accurate and still be worth checking against a source with nothing to gain from saying yes.

In practice that means the useful habit is not picking one source and discarding the other, but noticing when they disagree. If a market's own page claims full uptime while oniongate shows a recent Down reading for the same onion address, that gap is itself information: either our probe hit a routing issue specific to our vantage point, or the operator's own dashboard is stale, optimistic, or simply wrong. Either way, the disagreement is more useful than either number read alone, which is the entire case for keeping a measurement independent of the thing it measures.