onion.stinklink.net
Network Transparency Statement
This page describes the Tor relay infrastructure operated under the stinklink.net domain and provides context for administrators, researchers, and abuse-handling teams who may encounter this network in their work.
Relays
Two Tor relays are operated under this domain, both registered in the public Tor relay directory.
MiddleZwiebel middle
View on Tor Metrics →ExitZwiebel exit
View on Tor Metrics →Both relays declare a shared MyFamily identifier, ensuring the Tor client will never route a single circuit through more than one of them.
Exit Policy
The exit relay operates a reduced exit policy. The following destination ports are rejected, covering the highest-abuse traffic categories:
| Port(s) | Protocol |
|---|---|
| 22 | SSH |
| 23 | Telnet |
| 25, 465, 587 | Email (SMTP) |
| 135–139, 445 | Windows networking (SMB / NetBIOS) |
| 1194 | OpenVPN |
| 3389 | Remote Desktop (RDP) |
| 6881–6889 | BitTorrent |
All remaining ports are forwarded. This configuration follows the Tor Project's guidance for responsible exit operation and is consistent with policies maintained by the Electronic Frontier Foundation.
About the Tor Network
Tor is a free, open anonymity network designed to protect users against traffic analysis and surveillance. It is used by journalists, researchers, human rights workers, and members of the public who have a legitimate interest in private communication.
Traffic exiting through a Tor exit node originates from users distributed across the globe. The operator of an exit node has no visibility into, and no control over, the content of that traffic. The exit node is the last step in a three-hop encrypted relay chain; the traffic's origin is not known to the exit operator, and the destination is not known to earlier relays in the chain.
The Tor Project is a US 501(c)(3) nonprofit organisation. Relay operators worldwide contribute bandwidth voluntarily to sustain the network's capacity and geographic diversity.
Legal Framework
This infrastructure is operated in compliance with applicable law. The exit relay is hosted in Germany, where the operator's legal position is grounded in the following:
Mere conduit liability exemption. The EU Digital Services Act (DSA, Regulation 2022/2065), Article 4, and its German implementation in the Digitale-Dienste-Gesetz (DDG) §8, exempt providers that transmit third-party information without initiating, selecting the recipient of, or modifying that information. A Tor exit relay meets all three conditions and falls squarely within this exemption.
Established German case law. German courts have consistently treated Tor exit operators analogously to access providers (Zugangsanbieter). The absence of control over transmitted content, combined with the technical inability to identify individual users, has led courts to decline imposing liability on exit operators for traffic they route but do not originate.
"The operator of a Tor exit node is not the author of the transmitted content and cannot be held liable as a Störer where they have no practical means of preventing specific transmissions without shutting down the service entirely."
— paraphrased from the body of German Tor exit case law
The Electronic Frontier Foundation maintains a detailed legal reference for Tor relay operators: EFF Tor Legal FAQ.
Abuse & Contact
Abuse reports and enquiries from network administrators, law enforcement, and hosting providers are handled promptly. Please include the IP address, timestamp (with timezone), and any available context so reports can be matched to relay activity logs.
Contact: litterbulb@stinklink.net
Exit notice page: tor-exit.stinklink.net