Verified gateway reference

nexus4glgk7xzeqdcantwwyfuh5qvckhlqbydrszx6n4zdlff5wjshid.onion

Primary Nexus Tor entry point tracked by this archive. Always compare the full 56-character address against the Link Verification /mirror/ table before opening it in Tor Browser.

Onion gateways open only in Tor Browser. Never follow mirror links from unsolicited messages.

Research discussions

Independent background reading on the primitives this archive documents — onion routing, private settlement, and threat models:

Tor anonymity network — how onion routing and hidden services work

r/darknet — community reports on mirror verification and marketplace outages

Monero fundamentals — ring signatures, stealth addresses, confidential amounts

Third-party platforms. Verify technical claims independently and follow your local laws.

Tor Access Archive

How this archive is organized, what it verifies, and how to use it safely.

Why an archive, not a landing page

Thin mirror pages fail because they carry no context. This archive treats each gateway as a documented system: transport over Tor, v3 onion addressing, redundancy across verified gateways, settlement with Monero as default and Bitcoin Multi-Sig fallback, and governance via Warrant Canary and OPSEC checklist. Each topic has its own page — Marketplace, Mirrors, Crypto, OPSEC, FAQ — so readers and crawlers see topical depth instead of a single shallow page.

Infrastructure at a glance

The footprint is Tor-only. There is no clearnet login, no credential form before the encrypted tunnel is established. Sessions are isolated per gateway, metadata is not retained by design, and failover is geographic: US-EAST primary, EU-CENTRAL secondary, APAC tertiary. Latency medians of 42ms, 68ms, and 91ms reflect Tor circuit variance and are published so researchers can spot hijacked mirrors that respond abnormally fast or slow.

Gateway Features

Four properties every verified route must satisfy.

Encrypted Tunnel

Tor v3 onion routing with layered handshake verification. No clearnet fallback. Every address must be verified manually character-for-character before opening in Tor Browser.

No-Logs Policy

Zero-retention design. No session history, no identifiers, no analytics fingerprint stored on gateway nodes. Verification runs client-side.

Global Nodes

Three-region redundancy with automatic load indication. If primary is congested, secondary or tertiary verified gateways take over.

Multi-Sig Wallets

2-of-3 escrow: buyer, vendor, arbiter. Funds cannot move on one key alone. Disputes resolve by majority signature, not by support ticket.

Recent Activity

What changed and when — freshness you can verify.

2026-09-23
Full re-verification and crawler-hygiene pass. All mirrors re-verified (3/3 online), Warrant Canary re-signed, unreachable .onion hrefs decoupled from crawlable markup, fake search endpoint removed from structured data, robots.txt and sitemap cleaned. Archive dateModified bumped.
2026-08-28
Latency audit. EU-CENTRAL median 68ms after circuit rotation. No address rotation — same three Nexus Onion strings retained.
2026-08-14
Crypto params reviewed. XMR remains default settlement; BTC Multi-Sig fallback confirmed. No new assets added.
Onion routing diagram showing how Tor circuits work

Fig. 2 — Onion routing reference for the OPSEC section.

Warrant Canary

Status: ACTIVE — As of September 23, 2026, no gag orders, seizures, or key compromises have been reported to archive maintainers. Next scheduled review: within 14 days. If this block is stale or missing, treat all mirrors as unverified.

How researchers use this archive

Published June 2025 — Updated September 2026 — 8 min read

This archive exists so that every mirror address, Tor parameter, and settlement rule can be checked in one place instead of scattered across link lists. Start at Mirrors to confirm the gateway string, read the escrow model under Marketplace, settle strictly per Crypto, and apply the OPSEC checklist on every visit.

Mirror verification checklist with Tor Browser and address comparison

Why verification order matters

Address first, tunnel second, funds last. A gateway that differs by a single character is hostile even if its layout looks identical. A session with a stale canary date must be abandoned before any settlement step.

What this archive never does

No clearnet logins, no credential forms, no wallet downloads, no direct deals. The archive documents public gateway metadata and points to primary sources such as Tor Project, Monero documentation, and EFF threat-model guides.

Verify the string, check the canary, isolate the session. Everything else follows.

Archive index