Tor Relay, Bridge or Tor Exit Node hosting in the Netherlands.

IncogNET allows Tor on our network, however we have some reasonable guidelines set.

IncogNET proudly supports Tor and believes it plays a vital role in online privacy and anonymity. As such, we allow and encourage our customers to operate Tor relays, bridges, guard and exit nodes. However, to protect our network from abuse and to maintain a high level of quality of service for all, we do ask that those running Tor Exits utilize a strict exit policy, similar to that shown in the example below.

Tor Exit Hosting in Netherlands

Tor Exit Hosting Guidelines

We will allow Tor Exits on our network as long as the operator (you) follow our guidelines to help reduce the chance of abusive behavior stemming from our network. We support Tor because we support privacy, however our desire to maintain a clean and reliable network outweighs our desire to allow end-users to run unrestricted Tor Exit nodes. We have some reasonable guidelines put in place that allow you to offer quality network resources to the Tor network while also respecting our desire to have a happy network free of abuse.

By running a Tor Exit you agree that you will do the following:

  • You disallow common mail ports and use an exit policy similar to what is shown below. [Learn More]
  • You host a page on port 80 explaining that the server is a Tor Exit. [See Example]

Example of a strict Tor Exit Policy

The below contains just one example of a strict exit policy that we would accept on our network. For more examples, visit https://gitlab.torproject.org/legacy/trac/-/wikis/doc/ReducedExitPolicy. Your exit policy should allow access to common ports for web browsing and non-email communication, but not be so open that it allows for abuse from bad actors. Email ports must be blocked to prevent spam.

				
ExitPolicy accept *:20-21 	# FTP
ExitPolicy accept *:43 		# WHOIS
ExitPolicy accept *:53 		# DNS
ExitPolicy accept *:80-81 	# HTTP, HTTP alt.
ExitPolicy accept *:389 	# LDAP
ExitPolicy accept *:443 	# HTTPS
ExitPolicy accept *:464		# kpasswd
ExitPolicy accept *:531 	# IRC/AIM
ExitPolicy accept *:543-544 	# Kerberos
ExitPolicy accept *:554 	# RTSP
ExitPolicy accept *:636 	# LDAP
ExitPolicy accept *:706 	# SILC
ExitPolicy accept *:749 	# kerberos
ExitPolicy accept *:873 	# rsync
ExitPolicy accept *:902-904 	# VMware
ExitPolicy accept *:981 	# Remote HTTPS management for firewall
ExitPolicy accept *:989-990 	# FTP over TLS/SSL
ExitPolicy accept *:991 	# Netnews Administration System
ExitPolicy accept *:992 	# Telnet protocol over TLS/SSL
ExitPolicy accept *:1043 	# BOINC Client Control
ExitPolicy accept *:1103 	# Adobe Server 2
ExitPolicy accept *:1113 	# Licklider Transmission Protocol (IANA official) [RFC 5326]
ExitPolicy accept *:1194 	# OpenVPN
ExitPolicy accept *:1220 	# QT Server Admin
ExitPolicy accept *:1293 	# PKT-KRB-IPSec
ExitPolicy accept *:1500 	# VLSI License Manager
ExitPolicy accept *:1533 	# Sametime
ExitPolicy accept *:1677 	# GroupWise
ExitPolicy accept *:1723 	# PPTP
ExitPolicy accept *:1755 	# RTSP
ExitPolicy accept *:1863 	# MSNP
ExitPolicy accept *:1883 	# Message Queuing Telemetry (IANA official)
ExitPolicy accept *:2082 	# Infowave Mobility Server and CPanel default
ExitPolicy accept *:2083 	# Secure Radius Service (radsec) and CPanel default SSL
ExitPolicy accept *:2086-2087 	# GNUnet, ELI
ExitPolicy accept *:2095-2096 	# NBX
ExitPolicy accept *:2102-2104 	# Zephyr
ExitPolicy accept *:2222 	# DirectAdmin Control Panel
ExitPolicy accept *:3690 	# SVN
ExitPolicy accept *:4083-4085 	# Virtualizor Control Panel
ExitPolicy accept *:4321 	# RWHOIS
ExitPolicy accept *:4643 	# Virtuozzo
ExitPolicy accept *:4070 	# Trivial IP Encryption (TrIPE)
ExitPolicy accept *:5004 	# RTP media data [RFC 3551, RFC 4571]
ExitPolicy accept *:5050 	# MMCC
ExitPolicy accept *:5190 	# ICQ and AOL Instant Messenger
ExitPolicy accept *:5222-5223 	# XMPP, XMPP over SSL
ExitPolicy accept *:5228 	# Android Market
ExitPolicy accept *:5287 	# IP Camera viewer apps
ExitPolicy accept *:5675 	# V5UA application port (IANA official) [RFC 3807]
ExitPolicy accept *:6667-7000	# IRC
ExitPolicy accept *:6880 	# Dwyco Video Conferencing
ExitPolicy accept *:8008 	# HTTP alternate
ExitPolicy accept *:8074 	# Gadu-Gadu
ExitPolicy accept *:8082 	# HTTPS Electrum Bitcoin port
ExitPolicy accept *:8087-8088 	# Simplify Media SPP Protocol, Radan HTTP - Control Panel
ExitPolicy accept *:8232-8233 	# Zcash
ExitPolicy accept *:8332-8333 	# Bitcoin
ExitPolicy accept *:8443 	# PCsync HTTPS - Plesk Control Panel, Apache Tomcat SSL
ExitPolicy accept *:8502 	# FTN Message Transfer Protocol (IANA official)
ExitPolicy accept *:8601 	# Wavestore CCTV protocol
ExitPolicy accept *:8602	# XBConnect, Wavestore Notification protocol
ExitPolicy accept *:8888 	# HTTP Proxies, NewsEDGE, HUSH coin
ExitPolicy accept *:9418 	# git - Git pack transfer service
ExitPolicy accept *:11371 	# OpenPGP hkp
ExitPolicy accept *:19294 	# Google Voice
ExitPolicy accept *:19638 	# Ensim control panel
ExitPolicy accept *:50002 	# Electrum Bitcoin SSL
ExitPolicy accept *:64738 	# Mumble - voice over IP
ExitPolicy reject *:*
				
              

The Tor network is great, but what about I2P?

We love Tor, but currently their network capacity greatly exceeds the demand. While they have an abundance of resources available, there is another anonymity network that we love that could greatly benefit from some additional network resources. I2P (Invisible Internet Project) is over 20 years old with a large but often overlooked network. Click here to view our guides on running a high performance I2P network router or view the I2P Network Official Site.