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

88.198.62.215

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

Says it's not an open proxy; block was a while back. Is this still operative? Daniel Case (talk) 12:11, 18 March 2011 (UTC)

Webservers don't need to edit wikipedia. While that particular IP doesn't seem to be a proxy right now, there were many proxies found on the webhost's range (which is why it's caught in a very long rangeblock). The unblock rationale is less than convincing. Sailsbystars (talk) 12:30, 18 March 2011 (UTC)

Furthermore, not only is it a webhost, it also appears to be a shared webhost. Connecting with domain name leads to a different page than connecting to the IP. Definitely no reason to unblock at this point.... Sailsbystars (talk) 12:39, 18 March 2011 (UTC)

{{oproxy}} - Likely still a proxy. Sailsbystars (talk) 04:08, 22 March 2011 (UTC)

41.134.141.195

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

Reason: Requested unblock. It's not an open proxy. It's an MWEB DSL IP address. It was blocked with a message of "{{blocked proxy}} <!-- 41.240.253.112:8080 -->", but I checked and port 8080 is not open. - htonl (talk) 12:47, 19 March 2011 (UTC)

I don't see the unblock request..... Sailsbystars (talk) 12:53, 19 March 2011 (UTC)

I'm requesting the unblock! Even though I'm logged in, I got blocked because my DSL line got this IP. I disconnected and reconnected to get a different IP number that's not blocked, but the chances are someone else will get hit by this at some point. I can formally post an {{unblock}} if it's necessary. - htonl (talk) 12:59, 19 March 2011 (UTC)

No worries, that establishes that the IP is dynamic, so the proxy has moved on or been closed. Hopefully one of the admin watchers of this page will now unblock the IP. No evidence of a proxy running in the past few days. Sailsbystars (talk) 13:03, 19 March 2011 (UTC)

{{done}} —GFOLEY FOUR— 01:49, 27 March 2011 (UTC)

{{notaproxy}} -- EdJohnston (talk) 15:28, 29 March 2011 (UTC)

79.106.109.123

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

User talk:Euriditi has been requesting unblock. He says he is stopped from editing by this IP block. The editing record of Euriditi seems harmless, and it goes back many months. Mostly he is (correctly) adding interwiki links from topics in our Wikipedia to the Albanian wikipedia. I was unable to activate 79.106.109.123 as a proxy on port 8080. That IP does show up at Project Honeypot as having been recently used in dictionary attacks. It would not trouble me to issue IPBE in his case, since he has a good edit history. This is part of a range of IPs from Tirana, and they show up in editing articles on Albanian football players (as does Euriditi), so everything looks logical to me. I am unsure about lifting the IP block. Perhaps it could be reduced to anon-only. Here is Euriditi's record:

• Euriditi (talk · contribs · deleted contribs · logs · filter log · block user · block log)
• Here is the result of a rangecontribs from 79.106.109.0/24

-- EdJohnston (talk) 15:00, 29 March 2011 (UTC) Reason: Requested unblock.

The reason that 8080 doesn't work any more is because the port has left the map. What I do see now is tpyical of a websever, all filtered ports including hosts of SSH and SMTP servers. Looking at the ISP I see nothing that would indicate they are hosting plans availible. I do see normal customer accounts, phone lines, etc. being offered. The SMTP server could easily be just a host for the webmail, not so sure about the SSH port though. That being said, I am calling this {{notaproxy}}, but keep an eye out just in case. The project honeypot does note that the last sighting of this was a while ago. Unless jpgordon has some info on this, I'd be fine with an unblock. I have notified him of this post. -- DQ (t) (e) 00:05, 30 March 2011 (UTC)

I don't have any particular insight; for my education, what exactly does "Suspected network sharing device" mean here? --jpgordon^{::==( o )} 00:36, 30 March 2011 (UTC)

I sometimes get a similar message when I use whatismyip.com from a proxy server when I'm verifying them. For some types of proxies (both the legit, and illegit kinds), whatismyip can still trace my original IP (but I think that is a different website). My guess is the website you linked to had it in a proxy blacklist at some point. I agree that it's no longer a proxy, doesn't look to be a webhost at all to me. I think the dynamic range hypothesis is a good bet. Sailsbystars (talk) 02:52, 30 March 2011 (UTC)

91.121.197.199

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

Reason: There is a block for OVH's range 91.121.192.0/20. This includes one of my servers (91.121.197.199) which I occasionally use to get access to the Internet from severly filtered locations. This server does not run any proxy software. --ColdWind (talk) 18:09, 27 March 2011 (UTC)

(non administrator) I see that at least three proxies were operating on the range at the time it was blocked. I recommend an ip-block exemption for your account. Sailsbystars (talk) 19:13, 27 March 2011 (UTC)

I have to agree with Sailsbystars. Webhosts have no real reason to edit on wikipedia. The /20 is there for proxies and webhosts. To take the whole block down would be inviting the range to proxy in on that connection. I, along with Sailsbystars recommend and IPBE which can (if everything checks out) be given to you easily. -- DQ (t) (e) 12:27, 28 March 2011 (UTC)

Note that I'm the only admin there and I'm not setting an open proxy. But, anyway, IPBE is an even better solution for me, since I might connect through other servers when I'm abroad. --ColdWind (talk) 13:11, 29 March 2011 (UTC)

ColdWind has 300 edits here and 3100 edits on the Spanish Wikipedia that look OK. I would consider granting IPBE. EdJohnston (talk) 15:38, 29 March 2011 (UTC)

{{oproxy}} Still likely a nest of proxies, but problem resolved by granting user IPBE. Sailsbystars (talk) 14:11, 14 April 2011 (UTC)