Tor Exit Nodes List: The Public Register Behind Every Tor Connection
What an exit relay is and why a Tor exit nodes list exists at all
A Tor circuit passes through three relays by default. The first, the guard, sees the user's real address but not their destination. The middle relay sees neither. The third, the exit, sees the destination and carries the user's traffic onto the ordinary internet, so the website the user visits sees the exit's address rather than the user's. A Tor exit nodes list is simply the register of relays currently willing to perform that last role. The list exists because exits are, by design, not hidden. A relay operator who volunteers to run an exit is announcing to the network that traffic may leave through their machine, and that announcement is part of the network's public consensus, the document all Tor clients download to learn which relays exist and what they are allowed to do. This matters because it separates two things people often confuse. Tor hides the user. It does not hide the fact that a connection is coming from Tor. A website can know with near certainty that a visitor is using Tor, while knowing nothing about who the visitor is. The exit list is the mechanism for the first part and is irrelevant to the second. A scenario: a site administrator sees a login from an address on the exit list. They know the visitor used Tor. They do not, and cannot from that fact alone, know anything about which person it was.
Where the official tor exit list is published and in what forms
The authoritative tor exit list comes from the Tor Project,. The Tor Project has historically published exit addresses through a service called TorDNSEL and its associated bulk exit list, which lists the addresses from which exit relays are seen to make connections. A relay's advertised address and the address its exit traffic leaves from can differ, and the bulk exit list records the latter, which is what a website sees. The project's current metrics and status infrastructure, including Onionoo and the Relay Search tool, exposes relay data in machine-readable form with exit flags, and the check.torproject.org service, the page Tor Browser shows to confirm you are connected, is built on the same data. The formats you will encounter: - A plain text list of exit addresses, one per line, suitable for feeding into firewalls or block lists. - DNS-based lookups, where a service queries whether a specific address is an exit, useful for real-time checks without downloading the whole list. - JSON from the relay-search API, which includes the relay's flags, bandwidth, contact information and other details beyond the address. For anything that matters, use the Tor Project's own sources, which are documented on its metrics and support pages, and note that the list changes continuously as relays join, leave and change roles. A scenario: an administrator downloads a third-party copy and finds it six months old. Hundreds of current exits are missing and hundreds of listed addresses no longer run Tor.
Why publishing the list does not harm Tor users
A natural worry is that a public exit list undermines anonymity. Tor's anonymity comes from separating who you are from what you do. The guard relay knows your address; the exit knows your destination; neither knows both, and no single observer sees the whole path. The exit list reveals which machines are exits. It reveals nothing about which user's traffic is passing through which exit at a given moment, and nothing about which guard that user entered through. The Tor Project's threat model is explicit that it does not hide Tor usage from the destination. It hides the user's identity and location from the destination and hides the destination from local observers. Someone who needs to hide the fact that they are using Tor at all, from their local network rather than from the website, uses bridges, unlisted entry relays, which are a separate mechanism and are deliberately not published in bulk. There is a real cost to exit visibility, but it falls on convenience rather than anonymity: sites that block or challenge Tor traffic make the network less pleasant to use, and the project documents this trade-off and encourages sites to find alternatives to outright blocking. A scenario: a user worries that a site knows they use Tor. It does, and that is expected. What the site does not know is who they are.
How websites and administrators use a tor exit nodes list
The main consumers of a tor exit nodes list are the operators of services, and the ways they use it range from sensible to counterproductive. - Abuse triage. When a site receives abusive traffic from an address, checking it against the exit list tells the administrator whether blocking the address would block one abusive person or every Tor user routed through that exit. - Risk-based handling. Many services treat Tor traffic as higher-risk for specific actions such as account creation, payments or password resets, adding a challenge or extra verification while leaving reading unrestricted. This preserves access while addressing genuine fraud patterns. - Outright blocking. Some services refuse all connections from exits. The Tor Project's documentation argues against this, noting that it excludes journalists, activists and ordinary privacy-conscious users along with any abusers, and that abusers have many alternative sources of addresses while Tor users often do not. - Research and measurement. Academics and the Tor Project itself use the data to study network health, exit capacity by country and how websites treat Tor traffic. - Wrongly, as an identity signal. Treating an exit address as though it identified a person is a category error. An exit may carry thousands of users' traffic in a day. A scenario: a forum sees spam from an exit address. Instead of banning the address, which would silence every Tor user on that exit, it requires new accounts from Tor to complete an extra step. Spam falls.
What a tor exit nodes list download does and does not tell you
People perform a tor exit nodes list download for many reasons, and being precise about what the file contains prevents the most common misreadings. What it tells you: the addresses through which Tor traffic currently leaves the network, and, depending on the format, the relay's nickname, bandwidth, flags, uptime and the contact information its operator chose to publish. What it does not tell you: anything about the users whose traffic passes through those exits. It does not tell you what traffic an exit carried, when, or for whom. It does not tell you whether an exit is trustworthy; the Tor Project flags relays known to misbehave and removes them from the consensus, but the list itself is not a reputation system. It also does not stay accurate. Relays come and go, addresses change, and a list downloaded today is measurably wrong within days. A further caution: a list of exit addresses is not a list of Tor users, and treating it as one, for example by cross-referencing it against a site's logs to identify people, produces nothing but a list of connections that used Tor. That is a fact about the connections, not about the people. A scenario: a researcher downloads the list to count exits by country and finds the distribution heavily weighted toward a few European and North American jurisdictions. That is a finding about infrastructure, not about where Tor users are.
Exits versus other relays: reading the list correctly
The exit list is a subset of the full relay list, and understanding the distinction prevents confusion when reading relay data or comparing sources. Every relay in the Tor consensus carries flags describing its roles. Guard relays are stable, high-bandwidth relays that clients choose as their first hop and keep for months. Middle relays carry traffic between guard and exit. Exit relays are those whose operators have set an exit policy allowing traffic to leave to the internet, possibly only on certain ports. A relay can hold several flags at once, and many exits are also guards. Consequences for reading a list: - Only relays with the Exit flag matter for the question of which addresses websites will see. - Exit policies mean an address on the exit list may not be an exit for your service's port. A relay that exits only web traffic will never appear in your mail server's logs. - The exit list is much shorter than the full relay list. The network has thousands of relays, of which a minority run as exits, because exit operators absorb the abuse complaints that arrive at their address and many volunteers prefer to avoid that. - Bridges are absent from both lists by design. A scenario: an administrator compares the full relay list to their logs and finds many matches that are not exits. Those are guards and middles; only the Exit-flagged addresses represent Tor traffic arriving at their service.
A public list for a network built on hiding the right things
The Tor exit nodes list is public because exits were never secret. The network hides who a user is from the websites they visit and hides what they visit from anyone watching their connection; it does not hide the fact that Tor is in use, and the exit list is simply the convenient form of information every Tor client already holds. The Tor Project publishes it in several formats, as a plain address list, as DNS lookups and as a rich relay-search API, and the official sources are the ones to use, since third-party copies go stale within days. For service operators, the list supports abuse triage and risk-based handling and is misused for blanket blocking and, worse, as an identity signal it can never be. For everyone else, it is a window into the infrastructure of the network: who volunteers to run the hardest role, where that capacity sits geographically, and how much of the network is willing to carry traffic out into the open internet. One step to take today: open the Tor Project's relay search, filter for relays with the Exit flag, and read the contact information on a dozen of them. You will find universities, nonprofits and named individuals who chose to publish their involvement, and the abstraction of an exit node will become a set of specific people running specific machines for reasons they were willing to sign.
Frequently asked questions
is the list of tor exit nodes public?
Yes. The Tor Project publishes it deliberately, in plain-text, DNS-lookup and API forms, because exit relays are part of the public network consensus that every Tor client already downloads. Publishing it reveals which machines are exits, not who is using them.
does a public exit list compromise tor users' anonymity?
No. Tor hides who a user is from the destination and what they visit from local observers; it does not hide the fact that Tor is in use. Knowing an address is an exit tells a website only that a visitor used Tor, nothing about which of the many users routed through that exit it was.
where do i download the official tor exit list?
From the Tor Project's own metrics and status infrastructure, which is documented on its metrics and support pages and includes the bulk exit list, DNS-based lookups and the relay-search API. Third-party copies are frequently stale, and the list changes continuously, so refresh it often.
should websites block tor exit nodes?
The Tor Project recommends against blanket blocking, since it excludes journalists, activists and privacy-conscious users along with any abusers, who have other address sources. It suggests risk-based handling instead, such as extra verification for account creation or payments while leaving reading unrestricted.
can an exit node address identify a specific person?
No. An exit may carry traffic for thousands of users in a day, and its address says nothing about any of them. Cross-referencing exit addresses against logs produces only a list of connections that used Tor, which is a fact about the connections rather than about people.