Wikipedia:WikiProject on open proxies/Archives/Closed/2011/April
 | This is an archive of past discussions about Wikipedia:WikiProject on open proxies. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
200.37.107.194
- 200.37.107.194 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Obvious block evasion by 91.155.234.89 (talk · contribs · WHOIS) who according to this comment makes habitual use of proxies. Favonian (talk) 19:15, 26 March 2011 (UTC)
- I was able to activate this as a proxy on port 80, so I've hardblocked for one year. I'll wait for someone else to close this, in case I've missed anything. EdJohnston (talk) 19:39, 26 March 2011 (UTC)
- Hash.es had it open on 8080. However neither currently 80 nor 8080 proxies for me. The ISP it is hooked to offers both hosting and consumer internet, it's unclear which this is. On port 80, I now get a router page when trying to use it as a proxy. Hash.es gives the last good ping as 4 hours ago. While it looks like the proxy problem has been solved, the range has very sparse recent contributions and there has been some spam trouble from the range (200.37.112.205 (talk · contribs · WHOIS)) I think a yearlong block sounds about right, since the risk of collateral damage is exceedingly low, and the risk that there is still a proxy there is not. Sailsbystars (talk) 20:33, 26 March 2011 (UTC)
- {{notaproxy}} 8080 is not online right now as Sailbystars said and is usually where the traffic comes from according to multiple searches. That being said, port 80 does have software that allows for proxying, but a password is required making it look closed. With my SPI expirience, this is a planned evasion and a year on a single IP in this range sounds good. -- DQ (t) (e) 21:14, 26 March 2011 (UTC)
- Hash.es had it open on 8080. However neither currently 80 nor 8080 proxies for me. The ISP it is hooked to offers both hosting and consumer internet, it's unclear which this is. On port 80, I now get a router page when trying to use it as a proxy. Hash.es gives the last good ping as 4 hours ago. While it looks like the proxy problem has been solved, the range has very sparse recent contributions and there has been some spam trouble from the range (200.37.112.205 (talk · contribs · WHOIS)) I think a yearlong block sounds about right, since the risk of collateral damage is exceedingly low, and the risk that there is still a proxy there is not. Sailsbystars (talk) 20:33, 26 March 2011 (UTC)