en
Tor Exit Node VPS - Run a Relay on Offshore Infrastructure
Running a Tor exit node contributes to a global privacy infrastructure used by journalists, activists, dissidents, and privacy-conscious users worldwide. Exit nodes handle traffic exiting the Tor network to the clearnet - they appear as the source IP for traffic that may include sensitive content. Hosting an exit node requires a provider that understands Tor and a jurisdiction with legal cover for exit node operation. Iceland provides this environment.
Need this done for your project?
We implement, you ship. Async, documented, done in days.
Exit Node vs Relay - Understanding the Distinction
The Tor network consists of three node types: guard (entry) nodes, middle relays, and exit nodes. Exit nodes are the final hop - they make the actual clearnet connection on behalf of Tor users. This means the exit node's IP address appears as the source of traffic.
Running a middle relay is lower risk: middle relays only pass encrypted Tor traffic between Tor nodes. They never see the content or destination of the traffic. Middle relays receive no complaints from external parties.
Exit nodes do receive abuse complaints - DMCA notices, port scan complaints, and occasionally law enforcement inquiries about traffic that appeared to originate from the exit IP. Hosting an exit node requires a provider that explicitly supports this and has experience handling these contacts.
Anubiz Host Tor Hosting plans are designed for Tor infrastructure. Iceland's legal framework provides the best exit node hosting environment: the Icelandic Modern Media Initiative specifically protected Tor exit node operation from liability.
Setting Up a Tor Exit Node on Iceland VPS
Full Tor exit node configuration:
```bash
apt update && apt install tor -y
# Configure /etc/tor/torrc:
cat > /etc/tor/torrc << 'EOF'
ORPort 9001
DirPort 9030
ExitPolicy accept *:80
ExitPolicy accept *:443
ExitPolicy accept *:6667
ExitPolicy reject *:*
Nickname YourNodeNickname
ContactInfo your-contact@protonmail.com
RelayBandwidthRate 10 MB
RelayBandwidthBurst 20 MB
EOF
systemctl restart tor
# Check it is working:
journalctl -u tor -f
```
The ExitPolicy above allows HTTP/HTTPS/IRC traffic while rejecting high-risk ports. This "reduced exit policy" dramatically reduces abuse contacts while still contributing meaningfully to exit capacity.
Full exit policy (accept all ports) provides maximum benefit to the Tor network but generates more abuse complaints. Start with reduced policy.
Handling Abuse Contacts on Exit Nodes
Exit node operators receive automated abuse reports. Anubiz Host will forward these to your contact email. Standard handling:
DMCA notices: Tor exit node operators have a standard DMCA response template. The Tor Project provides sample language explaining that the IP is a Tor exit node and the traffic originated from Tor network, not from the server operator. Most automated DMCA systems accept this response.
Port scan complaints: If your exit policy allows TCP scan ports, you may receive reports of port scans appearing from your IP. Restrict exit policy to HTTP/HTTPS/common ports to eliminate most of these.
The Tor Project maintains the "Good Bad ISPs" wiki page documenting which providers support exit node hosting. Anubiz Host is supportive of Tor relay and exit infrastructure.
For legal protection: document your node's configuration, keep Tor Project's legal FAQ accessible, and respond promptly and professionally to Anubiz Host forwarded abuse contacts.
Related Services
Why Anubiz Host
100% async — no calls, no meetings
Delivered in days, not weeks
Full documentation included
Production-grade from day one
Security-first approach
Post-delivery support included
Ready to get started?
Skip the research. Tell us what you need, and we'll scope it, implement it, and hand it back — fully documented and production-ready.