Wikipedia:WikiProject Open proxies/Archives/Unblock/2011/July

59.95.15.0

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

See request on talk page, saying that this is a Dynamic IP not an open proxy. JohnCD (talk) 15:08, 17 June 2011 (UTC)

A quick check on the ip shows that it is likely on a dynamic range, and the previous proxy on the IP is no longer operating (port 1080). The last time the proxy was reported open was over a year ago. Probably safe to unblock..... Sailsbystars (talk) 16:19, 17 June 2011 (UTC)

I am looking at the same thing. -- DQ (t) (e) 11:44, 20 June 2011 (UTC)

{{notaproxy}} Unblocked by DQ, no suspicious edits since unblock. Sailsbystars (talk) 20:38, 3 July 2011 (UTC)

218.186.15.10

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

Reason: Requested unblock by Chensiyuan. עוד מישהו Od Mishehu 13:20, 30 June 2011 (UTC)

Note: I've temporarly granted ipexempt to Chensiyuan as he's a high volume good faith editor. This appears to be a large ISP (starhub), and my assumption is he just now rotated to that IP as it has been blocked for quite some time. If this action is in error, or there are other factors I'm missing, please feel free to revert. Kuru (talk) 14:13, 30 June 2011 (UTC)

IPBE is certainly earned here. It looks like the proxy was closed in march, so the IP can probably be safely unblocked. Sailsbystars (talk) 14:29, 30 June 2011 (UTC)

I'm a little more hesitant to hit that unblock button, I would like to take a deeper look esp. as port 80 is still open. I'll be back tomorrow for sure. -- DQ (t) (e) 03:02, 1 July 2011 (UTC)

Not enough to hold a block, unblocking and removing IPBE. -- DQ (t) (e) 18:49, 2 July 2011 (UTC)

{{notaproxy}}. Edits since unblock look pretty normal. Sailsbystars (talk) 13:42, 3 July 2011 (UTC)

195.55.130.44

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

The IP is not an open proxy but an IP from the Government of Spain, autonomous community of Aragón. We've received a complain via OTRS regarding this block; which blocks the whole Government in that area. Best regards, --m:dferg 17:11, 29 June 2011 (UTC)

I'm a bit hesitant to unblock... this IP has been severely abused in the past (much more so than even your average proxy). It doesn't currently appear to be a proxy, at least not useable on the port it was blocked on most recently nor another port listed in numerous google results. However, given how badly this was abused I would wait for another verified user to chime in before unblocking. My opinion is that the OTRS request is genuine and the server does appear as described in the request. My guess is that while upgrading or reconfiguring the server in May someone briefly misconfigured the caching server software (I've seen this happen before). The proxy appears to have been most active between January and February 2010, but no longer. Sailsbystars (talk) 22:21, 29 June 2011 (UTC)

I am also concerned for the same reason as the comments above. -- DQ (t) (e) 18:49, 2 July 2011 (UTC)

ya know, the block on this one expires within a week. Why don't we just wait until the block expires and see if procseebot reblocks or we get spammer editors? I think that's a reasonable compromise sort of action. Sailsbystars (talk) 13:39, 3 July 2011 (UTC)

{{notaproxy}} - Block expired a week ago with no edits of any sort. Procseebot has not reblocked, so it's likely clean for now. Sailsbystars (talk) 15:22, 14 July 2011 (UTC)

202.156.11.12

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

Reason: Requested unblock by Torment273. Block has a comment attached to it: 80. עוד מישהו Od Mishehu 12:57, 3 July 2011 (UTC)

This is the same ISP as above. It appears to be a caching server that was misconfigured at some point. At the moment however, it seems to no longer be a proxy for me. Sailsbystars (talk) 13:38, 3 July 2011 (UTC)

As far as I can tell, all they have done since the closure is made it into a reverse proxy which doesn't comfort me. Sailsbystars, I'm not exactly sure what it is, but it still sounds like a proxy or anon. software to me. This is the software running on port 80. -- DQ (t) (e) 19:53, 3 July 2011 (UTC)

Do you actually get a response on 80? All I get are blank pages or no data errors no matter what I do. There are legimiate reasons for using a closed proxy, and given that it has "cache" in the hostname, it seems to be one of those. Granted, it's a bit suspicious for a user with three edits to complain about a proxy, but I don't see any evidence it can be used as such recently. Sailsbystars (talk) 20:05, 3 July 2011 (UTC)

Hmm, ya, didn't see that in the host name yesterday. My response from the software for port 80 (the web interface) is "502 Bad Gateway".Sorry that would produce what you have, I have my web configured differently. Point taken that it hasn't been used much, and it could be legit usage. Ok, lets open it up, and watch. -- DQ (t) (e) 14:42, 4 July 2011 (UTC)

{{notaproxy}} Seems to have had mostly productive edits since unblock and nothing geographically suspicious. Sailsbystars (talk) 15:26, 14 July 2011 (UTC)

216.108.229.20

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

Reason: Requested unblock.

This ip is NOT a proxy!!— Preceding unsigned comment added by 119.130.246.154 (talk) 06:43, 25 July 2011

{{opblocked}} Yes it was a proxy beyond any reasonable doubt. And due to other malfeasance from the range, it will remained blocked for the forseeable future. No one needs to edit from a webserver, particularly one known to harbor proxies. Sailsbystars (talk) 11:18, 25 July 2011 (UTC)

202.46.143.62

202.46.143.62 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Blocked a couple of weeks ago; they say it's been closed. Daniel Case (talk) 16:09, 13 June 2011 (UTC)

Just ran a port scan, everything appears to be filtered. I get timeout errors when attempting to connect on ports 80, 443, 8000, and 8080 through a web browser. Hersfold ^(t/a/c) 22:02, 13 June 2011 (UTC)

Re-ran scan targeting port 2946 specifically (listed by ProcseeBot as the original access point) and it's also filtered and times out. Hersfold ^(t/a/c) 22:04, 13 June 2011 (UTC)

So we can't tell, then? Daniel Case (talk) 17:07, 14 June 2011 (UTC)

I ran a scan yesterday and wasn't able to find anything (relatively the same results of Hersfold). Despite what the web says/looking like it's highly active, I think we can assume good faith and unblock. -- DQ (t) (e) 17:43, 14 June 2011 (UTC)

In my experience, generally if everything is filtered, that means that whatever is on the other end isn't configured to serve as anything, much less a proxy. My guess is the proxy moved elsewhere when addresses got reassigned. It's when you get ports that are actually configured to be open or closed that things get suspicious. Hersfold ^(t/a/c) 16:04, 18 June 2011 (UTC)

{{notaproxy}} Unblocked by DQ, and hasn't been any trouble since. No proxy I could find. Sailsbystars (talk) 00:39, 26 July 2011 (UTC)