The exit relay inbox: DMCA notices, scare calls and guilt by IP address
Every Tor circuit ends on somebody's server. The exit relay is the only hop whose IP address faces the open internet, which means every destination site logs that single address for the actions of thousands of passing strangers. The Tor Project's support portal is blunt about the consequence: "it's probably safe to say that you will eventually hear from somebody" (Tor support portal).
The standard mail pile
The portal's expectations page reads like a catalogue of the internet's grievances: - Automated copyright notices covering "the first two minutes of a Vin Diesel movie."
- A well-known ransom-note email "supposedly from the FBI" over a hijacked account - the operator answers, the filer says "oh well" and leaves.
- Spam complaints, with the angry follow-up mail addressed to the operator's ISP.
- IRC nuisance reports, then a distributed denial-of-service attack against the relay itself.
None of it ends in court; most of it ends in silence. Long-term operators describe the same profile. Writing on the Tor Project blog in 2008 after five years running exits, phobos tallied "around 50 DMCA infringement notices, 20 abuse complaints, and zero visits from the Feds" (Tor Project blog). His first complaint came from an ISP after a DALnet IRC attack, resolved by phone and a quick port block. His summary: "Real life is much more boring." Guilt by IP address
The mail keeps arriving because of a structural assumption: whatever the IP did, the IP is guilty. The Tor Project's abuse template library exists to answer the recurring genres - comment spam, exploited webmail relaying, denial-of-service attacks, scraping robots, brute-force logins, hacked accounts, and e-commerce fraud, where shops flag every Tor order as fraudulent on the IP alone. It even answers threats of violence, by analogy: a death threat sent by post is not blamed on the mailbox's owner (Tor abuse templates). Each makes the same two points: the operator cannot identify any user, and the traffic did not originate there. The templates' standard closing says it plainly: "There is little we can do to trace this matter further. The system does not record logs of client connections or previous hops." An exit operator runs the address, not an archive. The project's philosophy section draws the conclusion: The philosophy of the Tor Project is that abuse should be handled proactively by the site administrators, rather than wasting effort and resources on seeking vengeance and chasing ghosts.
Answering the mail
The community's guidance is procedural rather than dramatic. The relay resources page asks operators to answer complaints promptly - usually within 24 hours - keep form letters on hand, and record which hosters tolerate exits at all (Tor community resources). Templates cover DMCA notices and generic abuse reports; when a host grows tired of the volume, the page offers one pressure valve: reduce the number of allowed ports in the exit policy. What those port lists control is widely misread - our exit policy myths explainer untangles it. The advice encodes lived experience. phobos met hourly DMCA notice bots in 2005 by wiring the template into a mail filter that replied on its own; later notices went to his ISP, which "just keeps closing the tickets" after receiving the same letter. The same page also advises running the exit somewhere that is not your home, and knowing a lawyer in advance - acknowledgment that some complaints are not settled by a good letter. When it stops being email
Law-enforcement queries are the rarer, heavier category. In June 2015, Boing Boing received a federal grand jury subpoena from the FBI in New Jersey demanding all records tied to one of its IP addresses: the site's own Tor exit node, then three years old. Its lawyer replied with a letter the outlet published in full: "Boing Boing does not have any subscriber records, user information, or any records at all related to the use of that IP address at that time, and thus cannot produce any responsive records" (Boing Boing). Cory Doctorow's account of the aftermath: "And that was it." Other jurisdictions have been less benign; the same post points to prosecutions of exit operators in Germany and Austria. Police attention does not always wait for a complaint: in June 2018, German Staatsschutz units raided the homes of Zwiebelfreunde board members - a group that helps fund and run Tor exit infrastructure - over an investigation targeting a political blog. Donor records were seized, reportedly including identities of Tails project members; a board member called the link "tenuous", and ZDNet reported no Tor infrastructure was compromised (ZDNet). More ordinary than raids are evictions: phobos lost an ISP when new owners enforced a proxy ban. Why exits stay scarce
Stack the frictions and the tier's scarcity stops being mysterious. Operators need an abuse contact and patience to feed it. Hosters that accept exits are rare enough that the community keeps lists of friendly and unfriendly providers. Blacklisting pushes exits off mainstream platforms: one operator quoted in a 2012 Tor Project funding discussion quit after his IP "started to get blacklisted on many, many major sites" (Turning funding into more exit relays). That discussion even weighed paying a dedicated person to answer complaints for sponsored exits - complaint handling priced as a part-time job. The post's author, Roger Dingledine, put the underlying economics simply: "you can't build servers out of cardboard and pay for their internet connections with good intentions." The Tor Project still ranks bridges and guard or middle relays as very low risk, with exits as the tier that carries the legal exposure. That ranking, plus an inbox that fills with other people's misdeeds, explains why exits remain the network's scarcest volunteers. The design still holds: an exit proves nothing about who sent the traffic, and every operator who answers another DMCA with the same old template is, in practice, keeping the network's front door open.
