What Onion Addresses Are and How They Work
An onion address is a special domain name that routes traffic through the Tor network to a hidden service. Unlike regular domain names, onion addresses are not registered with a central authority; they are generated cryptographically by the service operator. The address itself is derived from the service's public key, which means the address and the service are mathematically linked.
Onion addresses come in two formats. Version 2 addresses are 16 characters long and were the standard for years, but they are now considered weak and have been deprecated by the Tor Project. Version 3 addresses are 56 characters long and use stronger cryptography. A short address like 5mvm7cg6bgklfjtp appears to be a version 2 address, which means any service using it should have migrated to version 3 by now.
The Tor Project documentation emphasizes that the address itself proves nothing about the service's legitimacy or safety. An address is simply a routing identifier. The service operator controls what content or functionality runs behind it.
Why Onion Addresses Are Spoofed and Cloned
Attackers create fake onion addresses that look similar to legitimate ones to trick users into visiting phishing sites. Because onion addresses are random strings, users cannot easily remember them and often rely on bookmarks, search results, or word-of-mouth links. A clone might differ by only one or two characters, making it hard to spot at a glance.
Phishing clones of popular dark web forums and markets have been documented repeatedly. An attacker registers a new onion address, copies the legitimate site's design, and waits for users to mistype or follow a malicious link. Once a user logs in or submits information, the attacker captures credentials or payment details.
This is why the Tor Project and security researchers recommend that users verify onion addresses through multiple independent channels before trusting them. A PGP-signed announcement from the service operator, a link from an official clearnet website, or a mention in a trusted community forum are stronger signals than a single search result.
How to Verify an Onion Address Before Visiting
Verification requires you to cross-reference the address against trusted sources. Here are the steps to follow:
- Search for the address on the official website or social media account of the service (if one exists on the clearnet).
- Check the Tor Project's list of official onion addresses for well-known services like the Tor Project itself, the EFF, and other organizations.
- Look for a PGP-signed announcement from the service operator. The signature proves the announcement came from the operator's private key and has not been tampered with.
- Ask in trusted communities or forums where users discuss the service. Multiple independent confirmations reduce the risk of phishing.
- Compare the address character-by-character with any reference you find. Do not rely on a quick visual scan.
If you cannot find independent confirmation of an onion address, treat it as unverified. Do not log in, submit payment information, or upload sensitive files until you are confident the address is legitimate.
Reality Check: What Actually Protects You
According to Tor Project documentation, the Tor network itself does not validate whether an onion address belongs to who claims to operate it. The network routes traffic correctly, but it does not prevent impersonation. This means you are responsible for verification, not the network.
Security vendor incident reports on dark web phishing campaigns show that users who verify addresses through multiple channels are significantly less likely to fall for clones. The common mistake is visiting an address from a single source, such as a search engine result or a Reddit post, without cross-checking it elsewhere.
Law-enforcement actions against dark web markets have also revealed that some operators themselves run multiple mirrors or backup addresses. This is why a service might have several legitimate onion addresses. Knowing which ones are official requires checking the operator's own announcements, not guessing based on address similarity.
The takeaway is that your own diligence is the primary defense. No technical feature of Tor or onion addresses prevents phishing; you must verify independently.
Comparing Version 2 and Version 3 Onion Addresses
Version 2 onion addresses are 16 characters long and use older cryptographic algorithms. The Tor Project deprecated them in 2020 because they are vulnerable to brute-force attacks and do not provide the same security guarantees as version 3.
Version 3 onion addresses are 56 characters long and use stronger elliptic-curve cryptography. They are harder to forge and provide better protection against certain attacks. Most new services now use version 3 addresses exclusively.
If you encounter a short 16-character address, it is likely outdated. A legitimate service should have migrated to version 3 by now. A service still using only version 2 may be abandoned, poorly maintained, or intentionally using an old address to avoid detection. This is not a guarantee of illegitimacy, but it is a reason to investigate further before trusting it.
When verifying an address, check whether the service operator has published a version 3 address as well. If they have, use the version 3 address instead; it is more secure.
Common Mistakes When Checking Onion Addresses
Users often make preventable errors when verifying addresses. The most common is trusting a single source without cross-checking. If you find an address in a search result, a forum post, or a Reddit comment, verify it against at least one other independent source before visiting.
Another mistake is assuming that an address works correctly means it is legitimate. A phishing clone can load quickly and look identical to the real site. Functionality is not proof of legitimacy.
Users also sometimes confuse similar-looking characters. The letter 'l' (lowercase L) and the number '1' look nearly identical in many fonts, as do 'o' and '0'. When comparing addresses, zoom in or copy-paste them into a text editor to compare character-by-character.
Finally, do not assume that a service is safe just because it has been around for a long time or has many users. Phishing clones can exist alongside legitimate services for months before users notice. Verify every time you visit, not just the first time.
Safe Practices for Onion Address Management
If you regularly visit onion services, develop a system to store and verify addresses securely. Use a password manager or encrypted note-taking app to store verified addresses, not your browser history or a plain text file.
When you find a new address, create a verification checklist before saving it. Document where you found it, which other sources confirmed it, and the date you verified it. This record helps you spot if an address changes unexpectedly.
Bookmark addresses in your Tor Browser only after verification. Do not rely on bookmarks as your sole source of truth; re-verify periodically, especially if a service has been offline or if you have not visited it in months.
If you use multiple devices or mirrors of the same service, keep a separate list of which addresses are official. Some services publish a list of mirrors on their main onion address; check there first before trusting an address you found elsewhere.
The final step is to report suspected phishing clones. If you find an address that looks like a clone of a legitimate service, report it to the service operator or to the Tor Project. This helps protect other users.
Next Steps: Verify Before You Trust
An onion address like 5mvm7cg6bgklfjtp is just a routing identifier; it tells you nothing about the service's legitimacy or safety on its own. Your responsibility is to verify it independently before you interact with it.
Start by asking yourself: where did I find this address, and can I confirm it from another source. If the answer is no, do not visit it yet. Search for the service name plus "onion address" on the clearnet, check the service's official website or social media, and look for PGP-signed announcements. Only after you have found independent confirmation should you visit.
Keep a record of verified addresses and update it regularly. If a service publishes a version 3 address, prioritize that over any version 2 address. And if you ever doubt an address, verify it again before logging in or submitting sensitive information. This habit takes a few extra minutes but prevents the frustration and risk of phishing.
Common Questions
How do I know if an onion address is real or a phishing clone
Cross-reference the address against multiple independent sources, such as the service's official clearnet website, PGP-signed announcements, and trusted community forums. Compare the address character-by-character, not by sight. If you cannot find independent confirmation, do not visit it.
What is the difference between a 16-character and a 56-character onion address
The 16-character addresses are version 2, which use older cryptography and are now deprecated by the Tor Project. The 56-character addresses are version 3, which use stronger encryption. New services should use version 3 exclusively. If a service still uses only version 2, it may be outdated or abandoned.
Can I trust an onion address just because it loads quickly and looks legitimate
No. Phishing clones can load quickly and look identical to real sites. Functionality and appearance are not proof of legitimacy. Always verify the address independently before logging in or submitting sensitive information.
What should I do if I find a suspected phishing clone of an onion service
Report it to the legitimate service operator and to the Tor Project. Document the fake address and explain where you found it. This helps protect other users from the same scam.
Is the Tor network responsible for preventing onion address spoofing
No. The Tor network routes traffic correctly but does not validate whether an onion address belongs to who claims to operate it. You are responsible for verifying addresses independently.





