Onion Verification

Direct Answer

The official onion mirror should be verified from the clearnet domain before use. Treat every claimed mirror as unverified unless it matches the address published on this page or another official source. Onion access improves the browsing access layer, but it does not guarantee anonymity, legal outcomes, or third-party service safety.^[1]

Official onion mirror:

http://xuanxiapp43gq2w3ix3dguanzbxi2ppjquwmzjolbg5wykanj6ea72yd.onionCopy

How to Verify the Onion Mirror

Official onion verification status:

Use only the onion address published by the clearnet domain.

Official onion address:

http://xuanxiapp43gq2w3ix3dguanzbxi2ppjquwmzjolbg5wykanj6ea72yd.onionCopy

Follow this verification checklist before opening the onion mirror:

1. Open the clearnet production domain first.
2. Visit this Onion Verification page from the clearnet site.
3. Copy the onion address only from this page or another official source.
4. Open the address in Tor Browser.
5. Confirm that the onion page shows the same brand, content, legal links, and verification text.
6. Do not trust onion links found only in chats, comments, search snippets, or copied forum posts.

If an onion address does not match the address published here, it is not verified.

Why Onion Verification Matters

Onion addresses are hard to memorize. That creates a phishing and impersonation problem: a fake onion can copy the public site and try to collect attention, wallet data, or trust. Suspected copies should be handled through the official contact process rather than through random chats or comments.^[2]

The safest pattern is simple:

• publish the official onion address on the clearnet domain;
• keep the onion mirror content consistent with the clearnet site;
• warn users not to trust random onion links;
• add an Onion-Location hint after the onion service is live;
• keep a stable verification page.

Onion-Location Plan

The production server should support an Onion-Location signal where the stack allows it. Tor Project documentation explains Onion-Location as a way for a clearnet site to advertise its onion service to Tor Browser users.

Recommended production checklist:

• publish the onion address on /onion-verification;
• add the onion address to Tor Access;
• add an Onion-Location HTTP header or equivalent server configuration;
• keep clearnet as the canonical SEO version;
• avoid user-agent cloaking or different bot/user content;
• serve the same educational content through the onion mirror;^[3]
• keep third-party CTA behavior consistent and clearly bounded.

What Onion Access Does

Onion access can:

• give privacy-focused readers a Tor-native route to the same content;
• reduce dependence on normal clearnet access;
• align the site infrastructure with privacy research topics;
• make phishing checks more explicit;
• support no-logs and privacy exchange education at the access layer.

What Onion Access Does Not Do

Onion access does not:

• make third-party links automatically private;
• guarantee anonymity in every situation;
• protect a user from wallet mistakes;
• verify the safety of external services;
• erase blockchain transaction history;
• replace legal, tax, AML, sanctions, or source-of-funds obligations;
• make a fake onion safe because it looks similar.

Onion access is an access layer, not a universal shield.^[4]

Fake Onion Warning Signs

Be careful if an onion site:

• asks for seed phrases or private keys;
• claims to be official but is not listed on this page;
• has different legal pages or missing trust pages;
• changes CTA destinations without explanation;
• uses copied content with broken links;
• asks for direct wallet access;
• promises guaranteed anonymity or legal immunity;
• pressures users to act quickly.

FAQ