This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page.

211.116.154.220 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

which also edit warred on the Teardrop trailer article with the same content also is listed as an open proxy on port 8080, although I am unable to verify that it is still open. Sailsbystars (talk) 19:59, 18 October 2010 (UTC)

Appears to be a print server... doesn't seem to proxy, or if so, is very slow. Sailsbystars (talk) 21:13, 18 October 2010 (UTC)

• Note: I copied some comments by User:Sailsbystars that were left regarding this IP in an earlier entry. This IP has a holding page at http://211.116.154.220:80, but I was not able to use it as a proxy with my own browser, either at 80 or 8080. At 80 it let me in, but I could only see the provider's web site, not the general web. A Google search for the IP still shows it listed as a proxy server on 8080, so I recommend that we go ahead and block it for two years as a suspected open proxy. There is already some abuse in the history, since the IP was used as part of a revert war, as you can see in the edit history of Teardrop trailer. EdJohnston (talk) 20:32, 28 October 2010 (UTC)
  • No problem with shuffling things around, I was debating breaking them up myself. I agree that this server is a bit of an oddball. It clearly is being use AS a proxy, but I can't for the life of me figure out how. I seem to recall it had many open ports, but I only checked 80 and 8080 for proxying(and I think something else in the 808* range) and couldn't get any of them to work. However I agree that a block is probably in our best interest, as it sure is quacking like a proxy. Sailsbystars (talk • contribs • email) 21:10, 28 October 2010 (UTC)
  • Ports 301, 548, 1801, and 8081 are all also open and don't correspond with a normal service. But none seem to proxy for me. Also seems to have an open ftp server on port 21 and port 443, the ssl port, seems to be broken. I give up. Sailsbystars (talk • contribs • email) 03:54, 29 October 2010 (UTC)
    • My inclination for now is to leave it unblocked. Still unable to confirm at this time. My suspicion is that the sysadmin for the server fixed its settings so it's no longer an open proxy. If it starts misbehaving again, then we can revisit the issue. Sailsbystars (talk • contribs • email) 15:01, 3 November 2010 (UTC)
      • OK to close without action, in my opinion. Another admin has semiprotected Teardrop trailer until 25 November. I suggest that the semi be extended for six months if more problems occur there. EdJohnston (talk) 20:22, 3 November 2010 (UTC)
        • ((inconclusive)). It's possibly been fixed but I've blocked it for a year per Ed's original comment. There should be no legitimate collateral. -- zzuuzz ^(talk) 08:30, 4 November 2010 (UTC)

221.130.162.232 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

Reason: Open proxy[1]. Plus, see also [2] Irafox (talk) 17:29, 27 November 2010 (UTC)

((inconclusive)) Port is open but no pages may be retrieved. Q ^{T C} 04:52, 28 November 2010 (UTC)