This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. Multiple requests to the unblock-en mailing list from the IP range. Seems that Singaporean ISP maybe putting customers through a local proxy, rather than open proxies. Spoke with admin placing block and their memory of the specifics of the incident are now vague beyond a check was run. Thanks . — billinghurst sDrewth 01:38, 8 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This has been blocked for a year, have a request to unblock-en, can we please check the range to determine whether it still is problematic. Thanks — billinghurst sDrewth 02:48, 15 January 2012 (UTC) Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Blocked 4+ years ago, time to review following email to unblock-en 1 October 2007 Ryulong (talk | contribs | block) blocked 195.189.142.176 (talk) (account creation blocked) with an expiry time of indefinite ({{blocked proxy}}: Opera Mini Demo interface) (unblock | change block) Reason: Check for ongoing validity. Thx — billinghurst sDrewth 13:24, 17 January 2012 (UTC)
{{
proxycheck| … |complete
, |confirmed
, |likely
, |unlikely
, |possible
, |blocked
, |inconclusive
, |notaproxy
, and |decline
.
that it generates random IPs, so i've blocked the /20 and we'll try later to see if this one comes back. --
DQ
(ʞlɐʇ) 10:10, 21 January 2012 (UTC)– This proxy check request is closed and will soon be archived by a bot.
There is an unblock request at User talk:216.17.107.51. There are, in fact, two range blocks affecting that IP address, one is a checkuser block, which I have referred to the blocking checkuser/admin. The other is a proxy block, and I would be grateful if someone could check it. The user says "this ip is not an open proxy and is only used by me." The block log entry is 07:07, 15 June 2007 Ryulong blocked 216.17.104.0/21 (talk) (account creation blocked) with an expiry time of indefinite ({{blocked proxy}}). JamesBWatson ( talk) 11:38, 20 January 2012 (UTC)
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
A number of requests via unblock-en, and there seems a hint of IP proxy, especially I rDNS I find it is
Singapore Serangoon Starhub Cable Vision Ltd
Resolve Host: 202.156.10.9.cache.maxonline.com.sg
IP Address: 202.156.10.9
If we could at least check and rule out open proxy (as history previously as open proxy, though not currently labelled that way, just problematic), then we can modify how we handle requests from this IP.
Reason: Check only at this stage. Thanks. —
billinghurst
sDrewth 01:37, 22 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Repeated abuse from IP, currently reported on WP:AIV. Geolocate lists the IP as a "confirmed proxy server" RA0808 talk contribs 15:19, 23 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. I used the tor check tool which seemed to indicate that it was a tor node that exited to wikipedia, but figured it was worth reporting. Currently is blocked for 3 months, email and talkpage blocked since it was being abusively abusive, abusively. Syrthiss ( talk) 18:47, 24 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
From User_talk:64.76.75.58: "This is not really an open proxy. It's a transparent proxy for the customers of IFotoncorp (ifotoncorp.com), a small (as in <200 customers) ISP in the Galapagos islands."
Reason: Requested unblock.
Admin comment - I found this through Unblock Requests, although the IP block is not active. I can't figure out what is going on, but I'm sure a tech wizard here might sort it out. Apologies if this is time-wasting. Manning ( talk) 11:14, 29 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Appeal at unblock-en-l. I am unable to confirm that this IP address is still running an open proxy. -- Chris (talk) 15:05, 29 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits IP previously blocked as proxy. The only recent contribution is an attack on another user ( http://en.wikipedia.org/?title=User_talk:Sparthorse&diff=prev&oldid=474051216), previous contribution [2] suggests it is probably a web proxy. Peter E. James ( talk) 19:46, 31 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
See User talk:Sudip Regmi. User claims it isn't a open proxy, would appreciate some advice. -- Closedmouth ( talk) 11:31, 1 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
I am a User:Ramaksoud2000 and I'm reporting this proxy myself from this proxy because it is a tor exit relay. I'll be signing here as Ramaksoud2000 shortly to confirm but this is a tor exit relay and should be blocked.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:Sceptre - this is a university proxy server so the block is likely affecting a number of users. — DoRD ( talk) 15:55, 3 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This is a dedicated server that I administer. It is not acting as a proxy. draeath ( talk) 22:25, 3 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This is a dedicated server that I administer. It is not acting as a proxy. Reason: Requested unblock. draeath ( talk) 22:25, 3 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Escapeeyes again.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
I am independently running a scan of this range and will report back with my findings. -- Chris (talk) 21:05, 7 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
User seems a little irritated about the block and insists that it's not a proxy. Daniel Case ( talk) 19:26, 5 February 2012 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Escapeeyes. -- GenericBob ( talk) 07:40, 6 February 2012 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Escapeeyes. -- GenericBob ( talk) 07:41, 6 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Block message: {{blocked proxy}} <!-- 115.66.71.229:8888 -->
I am unable to verify that this proxy is still open. Estavali ( talk · contribs) has requested that this address be unblocked. -- Chris (talk) 09:34, 6 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
On behalf of Fnagaton ( talk · contribs). -- Chris (talk) 09:38, 6 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Escapeeyes. -- GenericBob ( talk) 07:27, 7 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
173.192.0.0/16 blocked by Zzuuzz, ({{blocked proxy}}: <!-- SoftLayer Technologies hosting range -->).
Reason: Requested unblock at User talk:Speeddymon. The user says "The IP in question is the external endpoint IP for SoftLayer's corporate office network. No idea why they use a proxy, but I am reasonably sure that the single IP could be whitelisted without causing any further spamming since it is separate from the rest of the hosted customers.
Side note, I had to post this from my phone on 4G because I can no longer even edit my talk page on the company network. ". JamesBWatson ( talk) 22:03, 7 February 2012 (UTC)
I've Googled the /16 range and here is what I've got: there are tons of web and http proxies in the range and some web proxies are below (verified). The 173.192.118.0/24 range seems clean, but there are some ghosts like freewebproxy.co, which was (is?) sitting in the 173.192.64.0/18 range. To sum up, the /16 range is rotten, but I have no direct evidence there is an active proxy in the particular 173.192.118.0/24 subrange. A possible compromise is "anonblock" on /16, i.e. release users who are already registered. Materialscientist ( talk) 11:38, 8 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Though their specific statements about 222.166.181.43 to 22.166.181.159, 222.166.181.43 to 22.166.181.231
Requests through unblock-en for clearance or to grant IP-exemption for account. — billinghurst sDrewth 14:34, 23 January 2012 (UTC)
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Beetstra and XLinkBot are having a little battle with a morphing set of domains, and a few IP addresses. Needing to determine whether it is corrupted, open, owned. Have a series that belong to same case. There are more. however, this should give a good indication of whether it is open proxy abuse. Thanks. — billinghurst sDrewth 03:45, 26 January 2012 (UTC)
Reason: Requested block.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested an unblock. Claims the open proxy was a misconfiguration and has since closed the open squid on port 3128.--v/r - T P 13:39, 29 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Suspected proxy once more of Escapeeyes, who now is insulting Purrum as some of her other favourite targets have been recently protected.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits The IP is clearly a sock of someone - see unblock request decline.
I looked up the ip on http://whatismyipaddress.com/blacklist-check: both The Spamhaus Project and Spam and Open Relay Blocking System came back red for that IP. The IP was already blocked for other disruption at that point. Several adjustments to the block were made, but I ultimately restored the original disruption block, questioning the results from the blacklist check. This seems like a better route to verify the existance of an open relay/proxy. Toddst1 ( talk) 23:07, 7 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Vandalising Canadian websites from an IP that seems to resolve to Rotterdam, the Netherlands. Possible proxy. Vale of Glamorgan ( talk) 01:09, 8 February 2012 (UTC)
Reason: Suspicious edits
Moscow IP has just made identical edit as suspected Rotterdam proxy (immediately above). Vale of Glamorgan ( talk) 01:47, 8 February 2012 (UTC)
Reason: Suspicious edits. Same edit as Rotterdam and Moscow but now it's from Lithuania. Vale of Glamorgan ( talk) 02:25, 8 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User claims that the tool used delivers a lot of false poses that would lead us to block his entire range (However, there may be a subtext to this. See this recent AN/I thread. Daniel Case ( talk) 03:35, 8 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Geolocate indicates name of registered organization is Peacefire, typing IP directly into the address bar leads to a Peacfire Circumventor Site. RA0808 talk contribs 05:37, 17 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
"Hide My Ass!" web proxies. Rangeblock? HF 25 18:26, 26 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Unblock request from the mailinglist. The block is a five year block from 2009, it might be time for a re-check. Martijn Hoekstra ( talk) 18:38, 26 February 2012 (UTC) Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Edit warrior from Azerbaijan who feels like spamming all kinds of comment sections and email spamming [3] or an open proxy. You decide! Hipocrite ( talk) 14:10, 2 March 2012 (UTC)
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Abusive edits
OverlordQ's Tor Checker, Geolocate, and Robtex all indicate that this is a TOR exit node. RA0808 talk contribs 18:02, 2 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: The account is currently blocked, but we have received no less than 9 clearly distinct unblock requests from the unblock mailinglist. This indicates there might be some proxy editing going on. Martijn Hoekstra ( talk) 13:48, 6 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Says it's merely a dynamic IP, not a proxy. Daniel Case ( talk) 16:27, 10 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User says that while block message says they may be running an open proxy, they are not. Daniel Case ( talk) 18:42, 11 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:61.18.170.68. Blocked at 06:33, 14 October 2011 by ProcseeBot. Block reason is {{blocked proxy}} <!-- 61.10.194.136:8909 -->. Unblock request reason is "Dynamic IP of the second largest ISP in Hong Kong. Not a proxy server." I have not been able to confirm that either 61.10.194.136 or 61.18.170.68 is currently a proxy, but would appreciate a check from someone more knowledgeable about proxies than me. JamesBWatson ( talk) 20:34, 13 March 2012 (UTC)
They updated their IP list. I have blocked the IPs themself but will have no time (and technical ability) to check for rangeblocks [4] for the next day or so (those IPs usually sit within hosting ranges). If you can, please check. Materialscientist ( talk) 22:48, 13 March 2012 (UTC)
I have also blocked
and
which are also newipnow.com proxies. I see that Materialscientist has blocked all the IP addresses he/she has listed and also two more (184.107.58.144, 173.248.191.250), almost all for 6 months. I would think that longer blocks would be in order. (Other IPs from the same proxy server have been blocked for substantially longer. For example, 64.15.147.205 has been blocked by Zzuuzz for 5 years.) My inclination is to increase the block lengths, but I will wait to see if anyone else disagrees. JamesBWatson ( talk) 09:13, 14 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Vandal targetting 2012 Midi-Pyrénées shootings [then my talk page after I protected the article] and using Wikipedia as a soapbox. 218.208.97.226 has been blocked as an open proxy in the past. - Mike Rosoft ( talk) 13:38, 24 March 2012 (UTC) Reason: Suspicious edits
Add to that:
Mike Rosoft ( talk) 16:01, 25 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Admission by zh:User:67.15.34.252, by zh:User:Tomchiukc and by zh:User:Gzdavidwong at zh:User:67.15.34.252 ( [5]) ( [6]). 77.86.113.133 ( talk) 15:08, 26 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Blocked indef in 2008. Is this still an open proxy? T. Canens ( talk) 08:11, 4 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: a hardblocked user is requesting a check to insure that this is actually an open proxy. Salvio Let's talk about it! 13:22, 5 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. Salvio Let's talk about it! 16:09, 6 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: repeated YouTube spam RA0808 talk contribs 00:36, 10 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This edit reintroduced vandalism previously added by 132.204.239.254 ( talk · contribs · WHOIS) and 132.207.222.136 ( talk · contribs · WHOIS). Both of these are registered to universities in Montréal, whereas the reported IP is Brazilean. Could be a case of meat puppetry (or international travelling), but robtex reports the IP as blacklisted by CNET. Not sure about the ramifications of that information, though. Favonian ( talk) 10:02, 12 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot. Need advice (go ahead and block if ..) on 176.227.192.0/20 ( talk · contribs). Behavior-wise, there is a strong evidence for a proxy of some kind [7]. The host is redstation.co.uk. Materialscientist ( talk) 13:37, 12 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reasons: Tor node [8]; blocked for abusive edits [9], [10]. See talk page history [11] for list of warnings and blanking of those warnings. JoeSperrazza ( talk) 16:11, 12 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Confirmed proxy. Hipocrite ( talk) 19:57, 12 April 2012 (UTC)
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: yesteday, another IP editor made a similar edit to Darkness Shines' talk page; it turned out that the IP was an open proxy. I suspect this one could be too. Salvio Let's talk about it! 10:08, 13 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Appears to be an open proxy. User has previously added identical edits [13] on User talk:Erikvcl as two other blocked proxies (193.224.193.153, [14] 41.35.45.197 [15]). One of the blocking admins recognized the edits as those of a banned user. Mathsci ( talk) 04:19, 14 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This IP was used recently in an edit war, it says Here that it is a confirmed proxy server. Darkness Shines ( talk) 12:03, 17 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. Cheers. Salvio Let's talk about it! 09:45, 28 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock (UTRS ticket #886).-- Jezebel'sPonyo bons mots 03:35, 1 May 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Requested on mailinglist. This is a global block
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
This is a Tor exit, but the block also blocks authenticated users who are obviously not anonymous!
Reason: Requested unblock. — Preceding unsigned comment added by Bgcaus ( talk • contribs)
– This proxy check request is closed and will soon be archived by a bot.
Hi, would one of the more experienced admins please look over this proxy block? It was clearly being used for sockpuppetry, and appears to be the server "ems23.your-freedom.de" via the port 53379. Thanks! Reaper Eternal ( talk) 14:20, 13 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits — Preceding unsigned comment added by Billinghurst ( talk • contribs)
This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. Multiple requests to the unblock-en mailing list from the IP range. Seems that Singaporean ISP maybe putting customers through a local proxy, rather than open proxies. Spoke with admin placing block and their memory of the specifics of the incident are now vague beyond a check was run. Thanks . — billinghurst sDrewth 01:38, 8 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This has been blocked for a year, have a request to unblock-en, can we please check the range to determine whether it still is problematic. Thanks — billinghurst sDrewth 02:48, 15 January 2012 (UTC) Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Blocked 4+ years ago, time to review following email to unblock-en 1 October 2007 Ryulong (talk | contribs | block) blocked 195.189.142.176 (talk) (account creation blocked) with an expiry time of indefinite ({{blocked proxy}}: Opera Mini Demo interface) (unblock | change block) Reason: Check for ongoing validity. Thx — billinghurst sDrewth 13:24, 17 January 2012 (UTC)
{{
proxycheck| … |complete
, |confirmed
, |likely
, |unlikely
, |possible
, |blocked
, |inconclusive
, |notaproxy
, and |decline
.
that it generates random IPs, so i've blocked the /20 and we'll try later to see if this one comes back. --
DQ
(ʞlɐʇ) 10:10, 21 January 2012 (UTC)– This proxy check request is closed and will soon be archived by a bot.
There is an unblock request at User talk:216.17.107.51. There are, in fact, two range blocks affecting that IP address, one is a checkuser block, which I have referred to the blocking checkuser/admin. The other is a proxy block, and I would be grateful if someone could check it. The user says "this ip is not an open proxy and is only used by me." The block log entry is 07:07, 15 June 2007 Ryulong blocked 216.17.104.0/21 (talk) (account creation blocked) with an expiry time of indefinite ({{blocked proxy}}). JamesBWatson ( talk) 11:38, 20 January 2012 (UTC)
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
A number of requests via unblock-en, and there seems a hint of IP proxy, especially I rDNS I find it is
Singapore Serangoon Starhub Cable Vision Ltd
Resolve Host: 202.156.10.9.cache.maxonline.com.sg
IP Address: 202.156.10.9
If we could at least check and rule out open proxy (as history previously as open proxy, though not currently labelled that way, just problematic), then we can modify how we handle requests from this IP.
Reason: Check only at this stage. Thanks. —
billinghurst
sDrewth 01:37, 22 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Repeated abuse from IP, currently reported on WP:AIV. Geolocate lists the IP as a "confirmed proxy server" RA0808 talk contribs 15:19, 23 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. I used the tor check tool which seemed to indicate that it was a tor node that exited to wikipedia, but figured it was worth reporting. Currently is blocked for 3 months, email and talkpage blocked since it was being abusively abusive, abusively. Syrthiss ( talk) 18:47, 24 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
From User_talk:64.76.75.58: "This is not really an open proxy. It's a transparent proxy for the customers of IFotoncorp (ifotoncorp.com), a small (as in <200 customers) ISP in the Galapagos islands."
Reason: Requested unblock.
Admin comment - I found this through Unblock Requests, although the IP block is not active. I can't figure out what is going on, but I'm sure a tech wizard here might sort it out. Apologies if this is time-wasting. Manning ( talk) 11:14, 29 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Appeal at unblock-en-l. I am unable to confirm that this IP address is still running an open proxy. -- Chris (talk) 15:05, 29 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits IP previously blocked as proxy. The only recent contribution is an attack on another user ( http://en.wikipedia.org/?title=User_talk:Sparthorse&diff=prev&oldid=474051216), previous contribution [2] suggests it is probably a web proxy. Peter E. James ( talk) 19:46, 31 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
See User talk:Sudip Regmi. User claims it isn't a open proxy, would appreciate some advice. -- Closedmouth ( talk) 11:31, 1 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
I am a User:Ramaksoud2000 and I'm reporting this proxy myself from this proxy because it is a tor exit relay. I'll be signing here as Ramaksoud2000 shortly to confirm but this is a tor exit relay and should be blocked.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:Sceptre - this is a university proxy server so the block is likely affecting a number of users. — DoRD ( talk) 15:55, 3 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This is a dedicated server that I administer. It is not acting as a proxy. draeath ( talk) 22:25, 3 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This is a dedicated server that I administer. It is not acting as a proxy. Reason: Requested unblock. draeath ( talk) 22:25, 3 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Escapeeyes again.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
I am independently running a scan of this range and will report back with my findings. -- Chris (talk) 21:05, 7 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
User seems a little irritated about the block and insists that it's not a proxy. Daniel Case ( talk) 19:26, 5 February 2012 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Escapeeyes. -- GenericBob ( talk) 07:40, 6 February 2012 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Escapeeyes. -- GenericBob ( talk) 07:41, 6 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Block message: {{blocked proxy}} <!-- 115.66.71.229:8888 -->
I am unable to verify that this proxy is still open. Estavali ( talk · contribs) has requested that this address be unblocked. -- Chris (talk) 09:34, 6 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
On behalf of Fnagaton ( talk · contribs). -- Chris (talk) 09:38, 6 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Escapeeyes. -- GenericBob ( talk) 07:27, 7 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
173.192.0.0/16 blocked by Zzuuzz, ({{blocked proxy}}: <!-- SoftLayer Technologies hosting range -->).
Reason: Requested unblock at User talk:Speeddymon. The user says "The IP in question is the external endpoint IP for SoftLayer's corporate office network. No idea why they use a proxy, but I am reasonably sure that the single IP could be whitelisted without causing any further spamming since it is separate from the rest of the hosted customers.
Side note, I had to post this from my phone on 4G because I can no longer even edit my talk page on the company network. ". JamesBWatson ( talk) 22:03, 7 February 2012 (UTC)
I've Googled the /16 range and here is what I've got: there are tons of web and http proxies in the range and some web proxies are below (verified). The 173.192.118.0/24 range seems clean, but there are some ghosts like freewebproxy.co, which was (is?) sitting in the 173.192.64.0/18 range. To sum up, the /16 range is rotten, but I have no direct evidence there is an active proxy in the particular 173.192.118.0/24 subrange. A possible compromise is "anonblock" on /16, i.e. release users who are already registered. Materialscientist ( talk) 11:38, 8 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Though their specific statements about 222.166.181.43 to 22.166.181.159, 222.166.181.43 to 22.166.181.231
Requests through unblock-en for clearance or to grant IP-exemption for account. — billinghurst sDrewth 14:34, 23 January 2012 (UTC)
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Beetstra and XLinkBot are having a little battle with a morphing set of domains, and a few IP addresses. Needing to determine whether it is corrupted, open, owned. Have a series that belong to same case. There are more. however, this should give a good indication of whether it is open proxy abuse. Thanks. — billinghurst sDrewth 03:45, 26 January 2012 (UTC)
Reason: Requested block.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested an unblock. Claims the open proxy was a misconfiguration and has since closed the open squid on port 3128.--v/r - T P 13:39, 29 January 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Suspected proxy once more of Escapeeyes, who now is insulting Purrum as some of her other favourite targets have been recently protected.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits The IP is clearly a sock of someone - see unblock request decline.
I looked up the ip on http://whatismyipaddress.com/blacklist-check: both The Spamhaus Project and Spam and Open Relay Blocking System came back red for that IP. The IP was already blocked for other disruption at that point. Several adjustments to the block were made, but I ultimately restored the original disruption block, questioning the results from the blacklist check. This seems like a better route to verify the existance of an open relay/proxy. Toddst1 ( talk) 23:07, 7 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Vandalising Canadian websites from an IP that seems to resolve to Rotterdam, the Netherlands. Possible proxy. Vale of Glamorgan ( talk) 01:09, 8 February 2012 (UTC)
Reason: Suspicious edits
Moscow IP has just made identical edit as suspected Rotterdam proxy (immediately above). Vale of Glamorgan ( talk) 01:47, 8 February 2012 (UTC)
Reason: Suspicious edits. Same edit as Rotterdam and Moscow but now it's from Lithuania. Vale of Glamorgan ( talk) 02:25, 8 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User claims that the tool used delivers a lot of false poses that would lead us to block his entire range (However, there may be a subtext to this. See this recent AN/I thread. Daniel Case ( talk) 03:35, 8 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Geolocate indicates name of registered organization is Peacefire, typing IP directly into the address bar leads to a Peacfire Circumventor Site. RA0808 talk contribs 05:37, 17 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
"Hide My Ass!" web proxies. Rangeblock? HF 25 18:26, 26 February 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Unblock request from the mailinglist. The block is a five year block from 2009, it might be time for a re-check. Martijn Hoekstra ( talk) 18:38, 26 February 2012 (UTC) Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Edit warrior from Azerbaijan who feels like spamming all kinds of comment sections and email spamming [3] or an open proxy. You decide! Hipocrite ( talk) 14:10, 2 March 2012 (UTC)
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Abusive edits
OverlordQ's Tor Checker, Geolocate, and Robtex all indicate that this is a TOR exit node. RA0808 talk contribs 18:02, 2 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: The account is currently blocked, but we have received no less than 9 clearly distinct unblock requests from the unblock mailinglist. This indicates there might be some proxy editing going on. Martijn Hoekstra ( talk) 13:48, 6 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Says it's merely a dynamic IP, not a proxy. Daniel Case ( talk) 16:27, 10 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User says that while block message says they may be running an open proxy, they are not. Daniel Case ( talk) 18:42, 11 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:61.18.170.68. Blocked at 06:33, 14 October 2011 by ProcseeBot. Block reason is {{blocked proxy}} <!-- 61.10.194.136:8909 -->. Unblock request reason is "Dynamic IP of the second largest ISP in Hong Kong. Not a proxy server." I have not been able to confirm that either 61.10.194.136 or 61.18.170.68 is currently a proxy, but would appreciate a check from someone more knowledgeable about proxies than me. JamesBWatson ( talk) 20:34, 13 March 2012 (UTC)
They updated their IP list. I have blocked the IPs themself but will have no time (and technical ability) to check for rangeblocks [4] for the next day or so (those IPs usually sit within hosting ranges). If you can, please check. Materialscientist ( talk) 22:48, 13 March 2012 (UTC)
I have also blocked
and
which are also newipnow.com proxies. I see that Materialscientist has blocked all the IP addresses he/she has listed and also two more (184.107.58.144, 173.248.191.250), almost all for 6 months. I would think that longer blocks would be in order. (Other IPs from the same proxy server have been blocked for substantially longer. For example, 64.15.147.205 has been blocked by Zzuuzz for 5 years.) My inclination is to increase the block lengths, but I will wait to see if anyone else disagrees. JamesBWatson ( talk) 09:13, 14 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Vandal targetting 2012 Midi-Pyrénées shootings [then my talk page after I protected the article] and using Wikipedia as a soapbox. 218.208.97.226 has been blocked as an open proxy in the past. - Mike Rosoft ( talk) 13:38, 24 March 2012 (UTC) Reason: Suspicious edits
Add to that:
Mike Rosoft ( talk) 16:01, 25 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Admission by zh:User:67.15.34.252, by zh:User:Tomchiukc and by zh:User:Gzdavidwong at zh:User:67.15.34.252 ( [5]) ( [6]). 77.86.113.133 ( talk) 15:08, 26 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Blocked indef in 2008. Is this still an open proxy? T. Canens ( talk) 08:11, 4 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: a hardblocked user is requesting a check to insure that this is actually an open proxy. Salvio Let's talk about it! 13:22, 5 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. Salvio Let's talk about it! 16:09, 6 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: repeated YouTube spam RA0808 talk contribs 00:36, 10 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This edit reintroduced vandalism previously added by 132.204.239.254 ( talk · contribs · WHOIS) and 132.207.222.136 ( talk · contribs · WHOIS). Both of these are registered to universities in Montréal, whereas the reported IP is Brazilean. Could be a case of meat puppetry (or international travelling), but robtex reports the IP as blacklisted by CNET. Not sure about the ramifications of that information, though. Favonian ( talk) 10:02, 12 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot. Need advice (go ahead and block if ..) on 176.227.192.0/20 ( talk · contribs). Behavior-wise, there is a strong evidence for a proxy of some kind [7]. The host is redstation.co.uk. Materialscientist ( talk) 13:37, 12 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reasons: Tor node [8]; blocked for abusive edits [9], [10]. See talk page history [11] for list of warnings and blanking of those warnings. JoeSperrazza ( talk) 16:11, 12 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Confirmed proxy. Hipocrite ( talk) 19:57, 12 April 2012 (UTC)
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: yesteday, another IP editor made a similar edit to Darkness Shines' talk page; it turned out that the IP was an open proxy. I suspect this one could be too. Salvio Let's talk about it! 10:08, 13 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Appears to be an open proxy. User has previously added identical edits [13] on User talk:Erikvcl as two other blocked proxies (193.224.193.153, [14] 41.35.45.197 [15]). One of the blocking admins recognized the edits as those of a banned user. Mathsci ( talk) 04:19, 14 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
This IP was used recently in an edit war, it says Here that it is a confirmed proxy server. Darkness Shines ( talk) 12:03, 17 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. Cheers. Salvio Let's talk about it! 09:45, 28 April 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock (UTRS ticket #886).-- Jezebel'sPonyo bons mots 03:35, 1 May 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Requested on mailinglist. This is a global block
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
This is a Tor exit, but the block also blocks authenticated users who are obviously not anonymous!
Reason: Requested unblock. — Preceding unsigned comment added by Bgcaus ( talk • contribs)
– This proxy check request is closed and will soon be archived by a bot.
Hi, would one of the more experienced admins please look over this proxy block? It was clearly being used for sockpuppetry, and appears to be the server "ems23.your-freedom.de" via the port 53379. Thanks! Reaper Eternal ( talk) 14:20, 13 March 2012 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits — Preceding unsigned comment added by Billinghurst ( talk • contribs)