Having a list of Tor nodes can always be a useful resource for spam-fighting, even though unfortunately most of those lists most often don’t make the difference between nodes which are just a relay and nodes which are also exit points.
So, here are a few listings that seems to be regularly updated (as of today, at least):
- http://torstatus.all.de/index.php?SR=Bandwidth&SO=Desc: has lots of details (notably, they do make the difference between exit nodes and simple relays), but is probably not trivial to parse automatically. NB: if you’re on Firefox, beware that it will slow down the browser massively for a few seconds. It’s fine on Iron, though.
- http://torstatus.blutmagie.de/index.php?SR=Bandwidth&SO=Desc: pretty much the same as the previous one (still a Fx killer, notably!), but hosted elsewhere.
- http://torstatus.rueckgr.at/index.php: and the same again, somewhere else.
- http://www.ircproxy.net/torlist/: just a list of IPs, probably great to parse. Also mention the update date, even though I guess it’s not a guarantee.
- http://files.sabmx.net/pg2/tor_block.txt: also just a list of IP, indicated as IP ranges.
- http://teksimple.com/tornodes.txt: that’s probably the easiest one to parse: just a text list, one IP per line, update date and time on first line.
Note however that it seems pretty much impossible to perform a DDoS attack from the Tor network (limitation #1 being it doesn’t really have that much bandwidth available), so there’s no reason to be a jackass like Daniel Austin MBCS and ban all traffic from Tor nodes. Particularly, blocking traffic from non-exit nodes altogether is seriously retarded. Purely banning all traffic from Tor also means you’d simply play along SOPA and alike. You might want instead to maybe just make the spam filter harsher, or systematically manual, on contents coming from Tor.
Well, anyway, you got the list now act smart with it. 😉
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.