3 ms·

Exit node: https://atlas.torproject.org/#details/463DC28452F676B7A6597ACA6DF7C6934F598806 https://atlas.torproject.org/#details/463DC28452F676B7A6597A... https:

by hieving 10y ago

Exit node: https://atlas.torproject.org/#details/463DC28452F676B7A6597ACA6DF7C6934F598806 https://atlas.torproject.org/#details/463DC28452F676B7A6597A... https://fraudguard.io/?ip=5.196.143.10 https://fraudguard.io/?ip=5.196.143.10 Non-exit node: https://atlas.torproject.org/#details/EF4BD6E8E5817690B79C6760898C7EFCCB6C2D30 https://atlas.torproject.org/#details/EF4BD6E8E5817690B79C67... https://fraudguard.io/?ip=108.61.199.202 https://fraudguard.io/?ip=108.61.199.202 It does not seem to make a distinction between exit and relay nodes, they are both deemed "tor_tracker".

Karunamon 10y ago
A number of large vendors like Barracuda and Tipping Point do this. A friend of mine one time found that they were unable to log in to pay their TV bill a few days after setting up a relay node. After he made enough noise about this, their engineers investigated, and sure enough, Tipping Point flags a relay node as suspicious for no good reason, and the IPS was blocking his traffic. On a side note, companies really don't like to deal with people who can't access their site. Being told over and over "It's your ISP", even when on a conference call with said ISP (and nevermind how difficult it was to get that set up with someone who understands the problem) was infuriating.