Tor · guide

Is Tor Browser safe, and safe from whom?

By Alberto Gulotta · Updated 18 September 2026 · 20 min read

Is Tor Browser safe? The program is free, it is made by a nonprofit, and it does not promise perfect anonymity — its own documentation says so, in the first line. The word hides four separate questions with four different answers, and the shortest route through them is to work out which of the four you are actually asking.

Which of the four questions are you asking?

The shorter way of asking — is Tor safe — is the same question and gets the same four answers. The order above is the order in which they cost you something: the code is good, what you do with it is where things go wrong, and the last two are not about you at all. They are about what the network around you can observe, and what it has been advised to do about that.

What undoes the protection, and why

Notice what the five rows in that table have in common: not one of them is a weakness in the network. A form you fill in defeats the whole thing before the traffic leaves the machine — provide a name, an email, an address or a phone number and “you are no longer anonymous to that website”, whatever the three relays did. The Tor Project’s advice there is behavioural rather than technical: “be vigilant and extremely cautious when filling out web forms”. It is also the reason a page about this tool is mostly a page about habits, and why what of you is already public is a better first hour than any browser setting.

Using it safely, step by step

1. Take it from the project, and change nothing afterwards. The browser arrives configured; the settings that matter are already set. The Tor Project asks you not to add to it — it blocks plugins such as Flash and Quicktime because “they can be manipulated into revealing your IP address”, and it does not recommend extra add-ons either, on the grounds that they may bypass Tor or harm your anonymity in other ways.
2. Understand what is and is not inside the tunnel. Only traffic from applications configured to use Tor goes through it. Everything else on the machine — a mail client, a chat app, an update checker — connects the way it always did, from your own address, at the same time.
3. Watch the address bar, because the last hop is not yours. Tor encrypts traffic to and within its own network, but “the encryption of your traffic to the final destination website depends on that website”. The browser ships with HTTPS-Only Mode for exactly this. Tails says what the last relay can do without it: it can observe your traffic, and it can impersonate the site you meant to reach — what Tails calls a machine-in-the-middle attack. What the padlock does and does not say covers the same ground for an ordinary browser.
4. Treat a certificate warning as an instruction, not an obstacle. If one appears, Tails’ advice is to “use the New Identity feature of Tor Browser to change exit node” rather than click through. It is the only step on this list that changes the route rather than a setting, and a connection that is not private is worth recognising before you meet one here.
5. Never run a torrent client over it. Not as a compromise, not carefully. Torrent applications have been seen ignoring proxy settings and connecting directly even when told to use Tor, and even when they obey, “you will often send out your real IP address in the tracker GET request, because that’s how torrents work”. The Tor Project’s own wording leaves no room: “Under no circumstances is it safe to use BitTorrent and Tor together”.
6. Do not open a downloaded document while you are still online. The browser warns you before handing a download to another application, and the warning exists because “these documents can contain Internet resources that will be downloaded outside of Tor by the application that opens them”. The consequence is stated plainly: “This will reveal your non-Tor IP address.” The recommended way round it is either “using a disconnected computer, or using dangerzone to create safe PDF files that you can open”.
7. If it matters that nobody knows you use it, ask for a bridge. By default Tor “does not prevent somebody watching your Internet traffic from learning that you’re using Tor”, and the remedy is in the same sentence: configure it to reach the network through a bridge instead of connecting to it directly. No bridge addresses appear on this page: the project hands them out itself, and that is the only place to get one.

Who can see that you are using it

Now the third question, which is where this page earns its place. Using Tor is visible, and it is worth being exact about who sees which half of it. Your provider and the network you are sitting on can see the connection but, as Tails puts it, “they cannot know which sites you visit”. The site at the other end has the opposite view: it cannot see you, but it knows the traffic came through Tor, “because the list of exit nodes of the Tor network is public”. That public list is also why, in Tails’ words, “Many websites ask you to solve a CAPTCHA or block access from the Tor network.”

The fourth question has an answer in a document most readers of this subject never meet. CISA — the United States cyber-defence agency — published an advisory, written with contributions from the FBI, on the risks associated with Tor and what organisations should do about the traffic. Its recommendation is to “block or closely monitor inbound and outbound traffic from known Tor nodes”, and its most restrictive option is to “Block all web traffic to and from public Tor entry and exit nodes.” The machinery for doing it is public too: the Tor Project runs the exit list itself, and the advisory notes “the highly dynamic nature of the Tor exit list, which is updated hourly”. It even names the ports — “ports commonly affiliated with Tor include 9001, 9030, 9040, 9050, 9051, and 9150”. This advisory is archived and was last revised on 2 August 2021, which its own page states at the top; the dates matter and they are given here for that reason.

Two things in that document are worth holding onto, and they pull in opposite directions. The first is that it does not treat you as a suspect: organisations are told to weigh “legitimate reasons that non-malicious users may prefer to, or need to, use Tor”, and that “mitigation actions can also impact the access of legitimate users who leverage Tor to protect their privacy”. The second is that blocking is imperfect in a way that is quietly informative: “blocking known Tor nodes does not completely eliminate the threat”, because bridges are not all listed publicly — the same property that makes one useful to a journalist makes it useful to anybody else.

Would a VPN be safer?

Which leaves the question almost everybody arrives holding: would a VPN be safer? The honest version of the answer needs a label on it, because the clearest statement of it comes from the Tor side. Tails writes that no anonymity network used for fast connections can fully protect against correlating both ends of a circuit, and then: “VPNs (Virtual Private Networks) are less secure than Tor, because they do not use 3 independent relays.” It also says, of those correlation attacks, that they have been studied in research papers “but we don’t know of any actual use to deanonymize Tor users”. Read it as what it is — the position of the project that maintains Tor — and then read what a tunnel changes and what it does not for the shape of the other tool, because the two are not answers to the same question. If what you actually want is for a website to stop recognising your browser, neither is the tool: that is fingerprinting, and what a private browser blocks.

Not covered here. It will not publish a single address: no onion links, no bridge lines, no mirrors, not even as illustration.

It will not name a version. One of the better-known answers to this question has a heading about what is new in a numbered release; the official download page, read on 17 September 2026, came back with about 212 words and no version number in it, so this page gives none.

And it will not tell anybody whose safety depends on this that a web page was enough. Where the stakes are real the right move is training and support from an organisation that does this properly, with your own situation in front of them. What holds instead is simple: the statement that Tor Browser includes many privacy protections but cannot guarantee perfect anonymity, the line that generally it is impossible to have perfect anonymity even with Tor, the boundary that Tor does not protect all of a computer’s Internet traffic and only protects applications properly configured to send their traffic through Tor, the warning that providing a name, email, address or phone number means you are no longer anonymous to that website and the advice to be vigilant and extremely cautious when filling out web forms, the observation that torrent applications have been observed to ignore proxy settings and make direct connections even when they are told to use Tor and that a real IP address often goes out in the tracker GET request because that is how torrents work, the flat statement that under no circumstances is it safe to use BitTorrent and Tor together, the note that plugins can be manipulated into revealing an IP address and that extra add-ons may bypass Tor or otherwise harm anonymity and privacy, the point that encryption of traffic to the final destination website depends on that website, the warning before documents are opened by external applications with the reason that such documents can contain Internet resources downloaded outside of Tor by the application that opens them and that this will reveal a non-Tor IP address, the recommendation to use a disconnected computer or dangerzone to create safe PDF files, the fact that by default Tor does not prevent somebody watching your Internet traffic from learning that you are using Tor together with the bridge as the remedy, and the closing social argument that the more Tor users there are near you and the more diverse their interests the less dangerous it is to be one of them, are all quoted from the Tor Project’s support page on using Tor Browser safely; the description of the Tor Project as a nonprofit organization that provides internet anonymity and anti-censorship tools, the statement that the advisory highlights risks associated with Tor, the recommendation to block or closely monitor inbound and outbound traffic from known Tor nodes, the most restrictive option of blocking all web traffic to and from public Tor entry and exit nodes, the Exit List Service actively maintained by the Tor Project, the highly dynamic nature of the Tor exit list updated hourly, the list of ports commonly affiliated with Tor, the acknowledgement of legitimate reasons that non-malicious users may prefer to or need to use Tor, the note that mitigation actions can also impact the access of legitimate users who leverage Tor to protect their privacy, and the admission that blocking known Tor nodes does not completely eliminate the threat, are quoted from CISA advisory AA20-183A, written with contributions from the FBI and last revised on 2 August 2021; and the statements that Tor and Tails do not protect you by making you look like any random Internet user but by making all Tor and Tails users look the same, that your provider and local network cannot know which sites you visit, that the sites you visit can know you are using Tor because the list of exit nodes is public, that many websites ask you to solve a CAPTCHA or block access from the Tor network, that an exit node can pretend to be the destination server in a machine-in-the-middle attack, the advice to use the New Identity feature of Tor Browser to change exit node after a security warning, the comparison that VPNs are less secure than Tor because they do not use three independent relays, and the note that end-to-end correlation attacks are studied in research papers but with no known actual use to deanonymize Tor users, are quoted from the Tails warnings page — which is written by the same organisation as the first source, and says so.