Requested Unblock

202.156.13.10

– A proxy checker has placed this case on hold pending further information or developments. 202.156.13.10 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan User claims in request that IP shows as open proxy because it's dynamic, and goes into some detail in their request. Daniel Case (talk) 15:57, 7 July 2011 (UTC)[reply]

Is there a way to search for blocks on a particular range or with a particular prefix? This seems almost identical to the above request and I'm wondering if there are more similar blocks out there. Sailsbystars (talk) 02:54, 8 July 2011 (UTC)[reply]

This actually may need to be re-blocked. It was used by a "logged out user" not a week ago and the amount of abuse in general from this IP is pretty high. I can't verify the proxy though, it may be intermittently available. Sailsbystars (talk) 12:15, 17 August 2011 (UTC)[reply]

84.147.220.8

– A proxy checker has placed this case on hold pending further information or developments. 84.147.220.8 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Block was made three years ago. Can we see if things have changed since then? Daniel Case (talk) 18:30, 2 August 2011 (UTC)[reply]

Taking a quick look, I'm not quite sure what this means (I'm too tired to hash it right now), but lets leave it for now. The following came up:

113/tcp closed auth
5060/tcp open sip AVM FRITZ!Box WLAN 7170 29.04.80 (Jan 27 2010)

-- DQ (t) (e) 02:34, 3 August 2011 (UTC)[reply]

Seems down right now, not to concerned with port 5060, but recheck down the road would be good. -- DQ (t) (e) 13:50, 5 August 2011 (UTC)[reply]

98.142.216.62

– This proxy check request is closed and will soon be archived by a bot. 98.142.216.62 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 98.142.208.0/20 · contribs · block · log · stalk · Robtex · whois · Google

Reason: A range was blocked of which my computer is a part. My IP (98.142.208.62) is my personal server, used only by myself. There has never been an open proxy on this IP. I have never had an association with any other IP in the 98.142.208.0/20 range. --Revaaron (talk) 16:33, 8 August 2011 (UTC)[reply]

Admins cannot unblock IPs that are in a blocked range without undoing the rangeblock entirely. —Jeremy v^_^v ^{Components:V S M} 19:49, 10 August 2011 (UTC)[reply]

Would it not be possible to block the actual offending IPs, or more specific ranges? The range covers a huge group of IPs and includes my own, which is not running an open proxy. Surely, WP has some sort of system for dealing this. --Revaaron (talk) 15:34, 11 August 2011 (UTC)[reply]

Well this is 1) The same thing we went through a month ago 2) Should not be your home ISP's IP Address 3) We block webhosts in general 4) I'm not comfortable unblocking the range. You can take this to functionaries-en

lists.wikimedia.org and see if they will give you an IP Block Exemption. But I can't do it without a checkuser, and I don't feel you need it to be honest. Note: This Website comes right off of your IP. -- DQ (t) (e) 18:15, 11 August 2011 (UTC)[reply]

I've had a similar brain dead httpd serving photos since I began using WP in 2002-3. It's never been a problem in the past. There's never been an open proxy in evidence. It'd be a stretch to call a photo of my cat a web site, let alone use that as a basis for categorizing this IP as a "webhost." There are a total of three IPs in this block of 4096 addresses with any contributions, and from what I can tell only one of them (98.142.211.209) was engaging in abuse, and that last occurred in March 2010, over a year before the block was put into place. I support the goal is to prevent abuse while allowing honest users to contribute, but I fail to see how this block, as implemented, helps WP achieve it. Thanks again- Revaaron (talk) 04:31, 18 August 2011 (UTC)[reply]

Open proxy Also, this range is under a global block, so even if we were to decide the range is safe to unblock (which it almost certainly isn't) on en.wikipedia, you would still be blocked from editing by the global block. It's not an explicit rule, but in general webservers are not allowed to edit wikipedia because most webhosting ranges can be and do get abused as open proxies. It's IPBE or edit through your ISP.... Sailsbystars (talk) 12:31, 17 August 2011 (UTC)[reply]

Then, it seems I'll be booted from editing WP for good for the unlisted rule of having an http server on port 80? Is an open proxy is in evidence, from this IP or any IP associated with my username? Editing through my ISP (work) isn't an option, as Wikipedia is blocked as a potential source of objectionable information and explicit images. Even if WP was no longer blocked at work, from what I can tell I'd be blocked again- as a developer, my machine is always running some sort of web server, though I've never run or used an open proxy. --Revaaron (talk) 04:37, 18 August 2011 (UTC)[reply]

202.156.13.252

– This proxy check request is closed and will soon be archived by a bot. 202.156.13.252 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

Requesting unblock. IP was directly blocked Jan 9 2011; block report indicated Port 80 was open. —Jeremy v^_^v ^{Components:V S M} 19:49, 10 August 2011 (UTC)[reply]

Host is down right now, will check later. -- DQ (t) (e) 20:48, 11 August 2011 (UTC)[reply]

Not currently an open proxy and unblocked. -- DQ (t) (e) 00:34, 14 August 2011 (UTC)[reply]