Tor Browser can reach a site without revealing who operates it. A genuine address, for its part, cannot protect files left unencrypted on your device. The two guides address those problems in sequence.
Our Reference Hub compares three 56-character .onion reference strings with PGP-signed announcements on Dread (d/DrugHub) as a baseline for address comparison. Part 1 covers personal security, from Tor connections to local storage and account access. Part 2 walks through checking an address signature and spotting clones before connecting. Both draw on platform documentation and established Tor and PGP practices, without the usual "top 10" filler.
Tor will not connect, or one page keeps timing out? Start with the browser and bridge settings, then check the device and its encrypted backups. The guide also explains the documented PGP-only sign-in model and what losing a private key means for account recovery. A working connection cannot confirm whether the site is genuine.
Found an address in a search result or on a supposed official mirror list? Platform documentation covers how public gateways rotate and how two private mirrors are distributed. From there, the guide works through full fingerprint checks, signed text verification, and proxy clone detection. It also addresses misleading trust badges and the steps to take after visiting a suspect page.
| Topic | Guide | Section |
|---|---|---|
How Tor Browser handles v3 .onion addresses and when bridges help |
Part 1 | Tor Browser and .onion addresses |
| Connection timeouts, CAPTCHA loops, Proof-of-Work and DDoS load | Part 1 | Connection problems |
| Browser settings, isolated operating systems and encrypted local storage | Part 1 | OPSEC and storage |
| PGP-only sign-in, authentication challenges and lost keys | Part 1 | PGP login |
| Public and private mirrors, address changes and stale links | Part 2 | Mirror addresses |
| Key fingerprints, signed lists and phishing-clone warning signs | Part 2 | PGP checks · Phishing copies |