|
If you've been blocked as an open proxy, please see: Help:blocked.
The multiwiki MetaProject on open proxies seeks to identify, verify and block open proxies and anonymity network exit nodes. To prevent abuse or vandalism, only proxy checks by verified users will be accepted. All users are welcome to discuss on the talk page, report possible proxies, or request that a blocked IP be rechecked. |
![Proxyblock.png](https://web.archive.org/web/20160410185816im_/https://upload.wikimedia.org/wikipedia/commons/thumb/d/d6/Proxyblock.png/350px-Proxyblock.png)
Reporting
Please report IP addresses you suspect are open proxies below. A project member will scan or attempt to connect to the proxy, and if confirmed will block the address.
File a new report here | ||
I. | For block requests: | |
Verify that the following criteria has been met:
|
||
For unblock requests: | ||
Verify that the following criteria has been met:
|
||
II. | For block requests | For unblock requests |
---|---|---|
|
|
|
III. | Fill out the resulting page and fill-in the requested information. | |
IV. | Save the page. |
Verified Users/Sysops Templates |
---|
|
Requests
HERE is page REQUESTS
![]() Current Archives |
---|
2012ish
2013ish 2014ish 2015ish 2016ish |
46.20.71.233
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 46.20.71.233 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Requested unblock.
- The user impacted by this block sent in an OTRS ticket indicating that they verified the proxy, and it is not open. ProcseeBot detected an open port on the IP two days ago. I'd like someone to verify this and unblock the IP if it indeed isn't (or is no longer) an open proxy. Thanks in advance! ☺ · Salvidrim! · ✉ 19:21, 25 August 2015 (UTC)
-
- Sorry to bug you directly Materialscientist but could I ask you a big favour and get you to look at this when you have a moment? I still have the user's OTRS ticket waiting on this. I'll owe you a big one. :) 13:34, 8 September 2015 (UTC)
-
- This is also the IP address of magenta-medical.com. It is puzzling that anybody would find themselves needing to log into Wikipedia from a web server. That is a technique for hiding your true IP address. This normally qualifies for {{webhostblock}}. EdJohnston (talk) 13:49, 8 September 2015 (UTC)
91.207.105.12
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 91.207.105.12 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. Apparently another anonymous proxy used by user:Asdisis to EVADE. - MrX 19:29, 27 August 2015 (UTC)
- Comment: Looks
Unlikely to me. A few open ports and blacklist listings but no open proxies that I can see. Mww113 (talk) 05:29, 29 October 2015 (UTC)
52.8.126.110
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 52.8.126.110 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. - MrX 21:08, 27 August 2015 (UTC)
- Comment: Seems to be
Confirmed webhost. WHOIS and DNS show it belongs to Amazon AWS. Mww113 (talk) 05:37, 29 October 2015 (UTC)
IP190.37.0.0/16
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 190.37.0.0/16 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Block reason given is Blocked_proxy for the entire range. A lot of collateral damage when such a wide range is blocked as an open proxy. If all of the ISP's servers are actually misconfigured and usable as open proxies, can a user or admin fluent in Spanish contact them to recommend better configuration and XFF? WhoIs shows CANTV Servicios, Venezuela located at Venezuela, Bolivarian Republic Of Caracas Cantv Servicios Venezuela. Thanks, DocTree (ʞlɐʇ·ʇuoɔ) WER 17:51, 9 September 2015 (UTC)
Reason: Requested unblock.
-
- Comment: The two IPs with the most edits on this range don't seem to have any proxies on them. There's really only a handful of edits on the entire range and yet this block affects up to 65,536 IPs. This seems like some pretty major overkill to me. @NawlinWiki: do you have any comments as the blocking admin? Mww113 (talk) 05:49, 29 October 2015 (UTC)
217.165.22.88
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 217.165.22.88 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits and traceroute goes through cogentco.com who describe theselves: "Cogent Data Centers also host Cogent's Utility Computing servers". — Brianhe (talk) 23:12, 14 September 2015 (UTC)
146.23.3.250
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 146.23.3.250 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
This IP is owned by Chevron Corporation, located in their San Ramon, California, office. It is reported as a confirmed open proxy. People operating the proxy have made personal attacks[1] and have violated the 1RR limitation set at the Abortion and mental health article. (All abortion topics have a 1RR limitation.) Since May 2015, other edits have been made by this proxy to disputed and controversial topics such as Conversion therapy (to convert gays) and Beginning of human personhood (a debate point in the abortion topic.) Binksternet (talk) 06:29, 17 September 2015 (UTC)
174.142.138.234
– This proxy check request is closed and will shortly be archived by a bot.
- 174.142.138.234 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. WHOIS→iWeb Technologies Inc.. Google→"iWeb: Cloud Hosting, Server Hosting & Hosted Solutions". Brianhe (talk) 15:06, 21 September 2015 (UTC)
Open proxy blocked (unchecked) 174.142.0.0/16 is rangeblocked. -- zzuuzz (talk) 19:44, 3 April 2016 (UTC)
168.1.23.79
– This proxy check request is closed and will shortly be archived by a bot.
- 168.1.23.79 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. - MrX 12:01, 25 September 2015 (UTC)
- I can't check it for proxy at the moment, but blocked it as an (abused) webhost. Materialscientist (talk) 12:06, 25 September 2015 (UTC)
2.75.239.135
– This proxy check request is closed and will shortly be archived by a bot.
- 2.75.239.135 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits, same editor as above, Khazakstan location. BMK (talk) 15:32, 6 October 2015 (UTC)
- Just to be clear: the editor involved is User:Jakeleereed, He got a 60 hour block for disruptive editing from Bishonen, and immediately socked with an IP from California, which Bishonen blocked. The next day he was back, editing the same articles, with the IP I reported above, 212.76.11.80. from Kazakhstan. Today he's editing from this IP, also from Khazakhstan. There was a vague possibility that yesterday's edits might not have been him (same suite of articles, but not the same edit), but today he's reverting to his previous material, which was deleted because it went against consensus (the reason for Bishonen's block).
I am by no means knowledgable about this kind of stuff, but when an editor from California (consistent with JLR's hours of editing) shows up in Kazakhstan, it seems highly likely that the IPs involved are open proxies. Can I suggest a second look at 212.76.11.80? BMK (talk) 17:00, 6 October 2015 (UTC)
- Certainly! Here are the five IPs from Kazakhstan:
- 2.75.239.135 (talk · contribs · WHOIS), no open ports, traceroute to ISP of record (Kcell).
- 176.222.154.51 (talk · contribs · WHOIS), no open ports, traceroute to ISP of record (2day.kz).
- 176.222.136.85 (talk · contribs · WHOIS), no open ports, traceroute to ISP of record (2day.kz).
- 212.76.11.80 (talk · contribs · WHOIS), no open ports, traceroute to ISP of record (2day.kz); host is a bank, though (ftp.kisc.kz).
- 109.239.44.201 (talk · contribs · WHOIS), no open ports, ISP is Llp Alma-tv.
- None of these have open ports to analyze (the main way of spotting these), at least not any that I can see. None of these IPs show up on public open proxy lists. These could be webhosts, but they just seem to be normal ISPs (and cable providers). I've seen enough really odd proxies to know there's no magic pixie dust in verifying them, though. Will leave this in case someone else wants to take a crack at it. Seems obvious that it's your boy, though, proxy or not. Kuru (talk) 01:25, 7 October 2015 (UTC)
- Yeah, I took a look at the contribs, and there's little doubt that it's him. So, just assuming for the moment that my scenario above is right, how did an editor from California get access to an IP from Kazakhstan? BMK (talk) 01:27, 7 October 2015 (UTC)
- Don't answer if WP:BEANS is a concern. BMK (talk) 01:31, 7 October 2015 (UTC)
- Unclear, but considering he's editing from work (kisc.kz), home (2day ISP), cable/TV (alma-tv) and his cell phone (kcell), I'd probably flip the question and ask how a Kazakhstan resident edited from a t-mobile wireless IP in California. S/he's not a master of english communication skills, although there's not much to go on. Lots of comical seething for Mr. Ken and Ms. Bish, lots of love for the roaring 20's film. Interesting. Kuru (talk) 02:18, 7 October 2015 (UTC)
- Hmmm. That flip is interesting, I hadn't thought about that. It might explain the communication problem a bit. BMK (talk) 03:48, 7 October 2015 (UTC)
- So today he's using 176.222.136.233, also from Kazakhstan. Maybe you'd better check the California IP he used to see of it is an OP: 208.54.4.246 BMK (talk) 19:51, 7 October 2015 (UTC)
- First thing I did in your previous report. :) It's a bog standard t-mobile wireless IP; nothing odd, other than the fact that people apparently still use t-mobile. Before you ask, 176.222.136.233 (talk · contribs · WHOIS) is another 2day IP with no open ports and nothing funny. I realize how spectacularly unhelpful all this is. Kuru (talk) 00:13, 8 October 2015 (UTC)
- No, not "unhelpful", just a bit mystifying. I do appreciate your checking these things out. I guess I won't post any further Kazakhstan-based IPs here (I'm assuming he'll be back tomorrow), I'll only come back if he starts using something different. In the meantime, I'm reverting and Bishonen is blocking. BMK (talk) 00:27, 8 October 2015 (UTC)
- One or two more from that 176.222.* range and we can calculate a good range block. I suspect the traffic from that ISP is close to zero except for him. Kuru (talk) 00:44, 8 October 2015 (UTC)
- Today he made an account, User:Keydy iphone, but I did find an old Kazakhstan IP, 37.99.109.87 Too bad it's not in the 176 range. I'm beginning to think that the California IP is another person, who just got caught up in the net accidentally. BMK (talk) 21:28, 8 October 2015 (UTC)
- Here's another 176 for you: 176.222.186.94 Also, 212.76.24.24 from Kazakhstan. BMK (talk) 01:40, 9 October 2015 (UTC)
- One or two more from that 176.222.* range and we can calculate a good range block. I suspect the traffic from that ISP is close to zero except for him. Kuru (talk) 00:44, 8 October 2015 (UTC)
- No, not "unhelpful", just a bit mystifying. I do appreciate your checking these things out. I guess I won't post any further Kazakhstan-based IPs here (I'm assuming he'll be back tomorrow), I'll only come back if he starts using something different. In the meantime, I'm reverting and Bishonen is blocking. BMK (talk) 00:27, 8 October 2015 (UTC)
- First thing I did in your previous report. :) It's a bog standard t-mobile wireless IP; nothing odd, other than the fact that people apparently still use t-mobile. Before you ask, 176.222.136.233 (talk · contribs · WHOIS) is another 2day IP with no open ports and nothing funny. I realize how spectacularly unhelpful all this is. Kuru (talk) 00:13, 8 October 2015 (UTC)
- So today he's using 176.222.136.233, also from Kazakhstan. Maybe you'd better check the California IP he used to see of it is an OP: 208.54.4.246 BMK (talk) 19:51, 7 October 2015 (UTC)
- Hmmm. That flip is interesting, I hadn't thought about that. It might explain the communication problem a bit. BMK (talk) 03:48, 7 October 2015 (UTC)
- Unclear, but considering he's editing from work (kisc.kz), home (2day ISP), cable/TV (alma-tv) and his cell phone (kcell), I'd probably flip the question and ask how a Kazakhstan resident edited from a t-mobile wireless IP in California. S/he's not a master of english communication skills, although there's not much to go on. Lots of comical seething for Mr. Ken and Ms. Bish, lots of love for the roaring 20's film. Interesting. Kuru (talk) 02:18, 7 October 2015 (UTC)
- Certainly! Here are the five IPs from Kazakhstan:
CU logs suggest a simple picture: no proxies, and no obvious socking - just two (or more) IP hoppers with access to several IP ranges, one hopper in the US and one in Kazakhstan. Materialscientist (talk) 02:12, 9 October 2015 (UTC)
- Behaviorally the Kazakhstan IPs all appear to be identical to the named accounts, Jakeleereed (blocked for disruption) and today's Keydy iphone. The California IP I now believe to be someone else, which I guess means no necessity for there to be open proxies involved. BMK (talk) 02:33, 9 October 2015 (UTC)
- A note of caution - many movie fans have similar editing patterns (for example, there are hundreds of different wikieditors, registered or not, who tweak boxoffice data for Indian movies, in an apparently "coordinated" fashion). CU logs suggest (no certainty) a couple of similarly mistaken assumptions in this case too. Materialscientist (talk) 03:17, 9 October 2015 (UTC)
Unlikely IP is an open proxy -- zzuuzz (talk) 07:05, 10 April 2016 (UTC)
216.177.129.188
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 216.177.129.188 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 203.122.8.2 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits alongside blocked undisclosed paid editor at Delhi Poetry Festival and Poets Corner Group. Reported as a confirmed proxy by http://whatismyipaddress.com/ip/216.177.129.188 and http://whatismyipaddress.com/ip/203.122.8.2 — Brianhe (talk) 06:46, 13 October 2015 (UTC)
- I don't see proxies on these two IPs, no open ports too. Materialscientist (talk) 08:22, 13 October 2015 (UTC)
106.51.133.200
– This proxy check request is closed and will shortly be archived by a bot.
- 106.51.133.200 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Continuously editing racist and unwarranted edits on Newar people, Shrestha, Shresthas pages with absolutely no reference or citations. Nepalichoro255 (talk) 04:16, 21 October 2015 (UTC)
63.143.226.248
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 63.143.226.248 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: A whois of this IP address indicates this is an open proxy.[2] Likely sock account of User:IHeardFromBob, who had previously used optonline servers editing the same article. TuvaluEditor3 (talk) 09:00, 21 October 2015 (UTC)
121.52.154.98
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 121.52.154.98 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Disruptive editing [3] following identical disruption from other US based IPs [4][5][6][7]; reported by whatismyipaddress.com as a confirmed proxy server in Pakistan [8], which is geo-unlikely for this particular topic. Brianhe (talk) 17:26, 27 October 2015 (UTC)
8.37.224.0/20
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 8.37.224.0/20 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: We've blocked several of these IPs as open proxies already. A quick whois of this range shows that it belongs to some sort of mobile content accelerator. A search of the range contribs reveals several blocks and loads of problematic edits. I know that this IP range uses XFF headers but as of yet they are not part of the trusted list at the XFF project on meta. For now I think it might be wise to block the whole range, contact the owners of the range, and hope they have themselves added to the trusted list. It seams to me that every IP on this range is probably a proxy, and if we're going to block some of them, we might as well just block the range. Mww113 (talk) 03:57, 29 October 2015 (UTC)
67.55.34.248
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 67.55.34.248 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Webhost. Previously blocked for a long history of problematic edits. Easily confirmed by simple whois. Mww113 (talk) 04:34, 29 October 2015 (UTC)
#wikipedia-en-help harassment IPs
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 86.151.10.183 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.211.214.81 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 162.219.178.170 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.213.157.141 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 5.196.109.149 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 94.242.228.122 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 46.148.17.210 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 193.106.30.156 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 178.175.138.10 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 190.97.163.209 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 31.210.123.217 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 5.196.106.212 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: All are IPs which, all within the span of two hours, have been used to spam/harass helpers in #wikipedia-en-help on IRC. Given all the disparate IPs and speed with which the user behind them switches IPs open proxies/anonymising services are suspected. —Jeremy v^_^v Bori! 21:51, 3 November 2015 (UTC)
93.110.xx.xx
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 93.110.60.207 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 93.110.110.216 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 93.110.119.124 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits from 93.110.xx.xx -- geolocates to Iran, but virtually all editing from this range is on Asian beauty pageants [9]. General topic is under discussion on COIN. Brianhe (talk) 21:22, 5 November 2015 (UTC)
- Note, 93.110.32.0/19 is listed on the Spamhaus Policy Block List (PBL) [10]. Brianhe (talk) 12:00, 6 November 2015 (UTC)
97.73.150.149 and more
- 97.73.150.149 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 172.164.2.180 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 172.164.22.120 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 172.164.30.82 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
These recently-used IPs are related to a long-term disruptive user who typically prefaces his talk page comments and edit summaries with "Joshua Raymond Hahn", and is possibly Wikipedia:Long-term abuse/The UPN Vandal Some of the older IPs he's used (circa 2014) are:
- 97.73.64.147 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 97.73.64.153 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 172.162.3.218 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 97.73.64.154 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP - this one was blocked for 2 years, 7 months. Mama!
I dunno if those are worth checking. Just including to show some consistency with the newer ranges, 97.73.* and 172.16*.* Some of the newer IPs are flagged by whatismyipaddress.com as being suspected proxy servers, which I know doesn't mean that they are. Thanks. Cyphoidbomb (talk) 18:03, 10 December 2015 (UTC)
41.220.68.227
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 41.220.68.227 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
WhatIsMyIPAddress reports that this is confirmed as a proxy server (not necessarily open), and a spam source.
"Services: Confirmed proxy server Recently reported forum spam source. (1)"
A small number of recent suspicious edits. --joe deckertalk 00:00, 22 December 2015 (UTC)
Reason: Suspicious edits
194.75.171.106
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 194.75.171.106 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits; reported by WhatIsMyIP.com as confirmed proxy [11]. Brianhe (talk) 22:43, 22 December 2015 (UTC)
73.15.177.210 and others
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 73.15.177.210 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 216.169.136.172 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 108.171.111.75 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits; two IPs associated with reliablehosting.com and one associated with cable provider reverted Mean as custard after he reverted a CU-confirmed Orangemoody sock at Myfreeimplants. Brianhe (talk) Brianhe (talk) 10:40, 26 December 2015 (UTC)
217.123.166.163
– This proxy check request is closed and will shortly be archived by a bot.
- 217.123.166.163 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Edits made to denigrate person. Edits are offensive, sensitive and untrue https://nl.wikipedia.org/w/index.php?title=Jay_Tromp&action=history — Preceding unsigned comment added by !testTimo92! (talk • contribs)
194.75.171.106
– This proxy check request is closed and will shortly be archived by a bot.
- 194.75.171.106 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason:
- Suspicious edits on article whose subject is related to hacking and at least one of whose editors is named in SPI [12]
- IP is listed as confirmed proxy server by whatismyipaddress.com [13]
— Brianhe (talk) 12:16, 18 January 2016 (UTC)
- A confirmed proxy server is different to an open proxy. An initial observation is that this doesn't appear to be open. Belonging to an aspect of a bank, I'd be extremely surprised if it was. -- zzuuzz (talk) 12:29, 18 January 2016 (UTC)
66.85.148.52
– This proxy check request is closed and will shortly be archived by a bot.
- 66.85.148.52 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason:
- Accidentally had Anonymox switched on when trying to make a post to my talk page, nothing stopped me and I did not see a block message. This is proxy code us11e.
- Sunil The Mongoose (talk) 21:35, 26 January 2016 (UTC)
- ROBTEX also points to a "Public anonymox" service which appears to be a Firefox addon that allows one to hide one's IP address. I am inclined to consider it an open proxy service.Jo-Jo Eumerus (talk, contributions) 14:24, 8 February 2016 (UTC)
- I've hard blocked 66.85.128.0/18. Mike V • Talk 21:51, 8 February 2016 (UTC)
37.221.160.115
– This proxy check request is closed and will shortly be archived by a bot.
- 37.221.160.115 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason:
200.219.249.91
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 200.219.249.91 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. Multiple IPs from around the world editing an article about a darknet client.- MrX 13:57, 7 February 2016 (UTC)
- Scanned that one earlier along with all other IPs editing that article. Did not see anything obviously funny. Kuru (talk) 14:26, 7 February 2016 (UTC)
IP: 192.168.1.3 | Firefox doesn't work on all wikis in no languages at all.
– This proxy check request is closed and will shortly be archived by a bot.
- 192.168.1.3 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Requested unblock.
Declined to run a check: 192.168.1.3 is a private network address. Nothing we can do without the real IP address. -- zzuuzz (talk) 19:10, 3 April 2016 (UTC)
39.119.216.206
– This proxy check request is closed and will shortly be archived by a bot.
- 39.119.216.206 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason:
37.237.152.95
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 37.237.152.95 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. A user obsessed with disruptive edits to archive.today URLS . See also the section 'Sockmaster flagging archive.today links en masse' at WP:AN.- MrX 18:54, 21 February 2016 (UTC)
- There doesn't seem to be anything operating in here.. Regards—UY Scuti Talk 20:07, 21 February 2016 (UTC)
71.207.70.133
– This proxy check request is closed and will shortly be archived by a bot.
- 71.207.70.133 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on ja.wikipedia.org.--HotKorokke (talk) 00:26, 27 February 2016 (UTC)
- Yes, a proxy, already blocked by ProcseeBot. Materialscientist (talk) 01:18, 27 February 2016 (UTC)
24.148.2.64
– This proxy check request is closed and will shortly be archived by a bot.
- 24.148.2.64 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on ja.wikipedia.org.--HotKorokke (talk) 00:32, 27 February 2016 (UTC)
- Yes, a proxy, already blocked by ProcseeBot. Materialscientist (talk) 01:18, 27 February 2016 (UTC)
46.63.98.70
– This proxy check request is closed and will shortly be archived by a bot.
- 46.63.98.70 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on ja.wikipedia.org.--HotKorokke (talk) 07:46, 27 February 2016 (UTC)
Sorry, this IP is already blocked on enwp.--HotKorokke (talk) 08:00, 27 February 2016 (UTC)
94.230.139.19
– This proxy check request is closed and will shortly be archived by a bot.
- 94.230.139.19 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on ja.wikipedia.org.--HotKorokke (talk) 07:48, 27 February 2016 (UTC)
Sorry, this IP is already blocked on enwp.--HotKorokke (talk) 08:00, 27 February 2016 (UTC)
201.173.181.208
– This proxy check request is closed and will shortly be archived by a bot.
- 201.173.181.208 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on ja.wikipedia.org.--HotKorokke (talk) 07:49, 27 February 2016 (UTC)
Sorry, this IP is already blocked on enwp.--HotKorokke (talk) 08:01, 27 February 2016 (UTC)
Inconclusive: quite a dodgy IP, but at this time possibly only historically, or sporadically, so. -- zzuuzz (talk) 17:44, 8 April 2016 (UTC)
37.140.110.88
– This proxy check request is closed and will shortly be archived by a bot.
- 37.140.110.88 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on ja.wikipedia.org.--HotKorokke (talk) 07:51, 27 February 2016 (UTC)
Sorry, this IP is already blocked on enwp.--HotKorokke (talk) 08:01, 27 February 2016 (UTC)
Open proxy used by User:Tobeme free
Acccording to Checkuser comments at Wikipedia:Sockpuppet investigations/Denis.g.rancourt User:Tobeme_free "is hiding behind an anonymous proxy server." I request that the IP range being used by User:Tobeme_free be blocked. 192.235.252.195 (talk) 23:32, 27 February 2016 (UTC)
- Note: This is being discussed at WP:ANI#192.235.252.195; and is effectivly redundant. -- The Voidwalker Discuss 17:31, 28 February 2016 (UTC)
201.251.156.17
– This proxy check request is closed and will shortly be archived by a bot.
- 201.251.156.17 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
suspicious edits, namely removing cited text that has already been the subject of a talk page request for comments. Page in question has seen several visits from proxies, some already banned, in the past couple months 63.143.228.128 (talk) 01:58, 23 March 2016 (UTC) Reason: Suspicious edits
- As a sock account of User:IHeardFromBob, you shouldn't be editing let alone complaining here. 201.251.156.17 (talk) 08:29, 25 March 2016 (UTC)
187.18.122.211
– This proxy check request is closed and will shortly be archived by a bot.
- 187.18.122.211 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Suspicious edits, confirmed proxy and recently reported spam source on geolocate. 63.143.229.73 (talk) 00:42, 26 March 2016 (UTC) Reason: Suspicious edits
178.252.189.226
– This proxy check request is closed and will shortly be archived by a bot.
- 178.252.189.226 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Suspicious edits, confirmed proxy, recently reported spam source. 63.143.225.68 (talk) 13:30, 26 March 2016 (UTC) Reason: Suspicious edits
117.254.2.58
– This proxy check request is closed and will shortly be archived by a bot.
- 117.254.2.58 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: recently used by IP-hopping LTA Nsmutte (cf filter log), was previously blocked as a proxy. BethNaught (talk) 18:06, 28 March 2016 (UTC)
- Unlikely an open proxy, port 1720 is open which could be for VoIP but not for proxies. Regards—UY Scuti Talk 01:13, 29 March 2016 (UTC)
210.212.172.209
– This proxy check request is closed and will shortly be archived by a bot.
- 210.212.172.209 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
IP was blocked back in 2006 with an expiry time of indefinite. Looks like the range is allocated to an university and there isn't anything open. A quick Google search reveals there was indeed an open proxy on port 3128, but back in 2006, not now. I guess, it's okay to unblock this now. Regards—UY Scuti Talk 09:11, 2 April 2016 (UTC)
Reason: Requested unblock.
51.255.39.124
– This proxy check request is closed and will shortly be archived by a bot.
- 51.255.39.124 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Used by an IP hopping POV-pusher whose immediate prior IP was a proxy. BethNaught (talk) 08:35, 3 April 2016 (UTC)
- IP belongs to the webhosting provider OVH. Port 8080 is open with something listening on it (no open proxy) at the time I checked. The IP and port is listed on this proxy list, indicating something might have been operating on it earlier. This should be blocked as
{{webhostblock}}
. Regards—UY Scuti Talk 10:17, 3 April 2016 (UTC)Possible IP is an open proxy, blocked as a webhost. Possible VPS. See also http://www.ip-51-255-39.eu/ -- zzuuzz (talk) 17:49, 8 April 2016 (UTC)
203.129.224.79
– This proxy check request is closed and will shortly be archived by a bot.
- 203.129.224.79 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Proxy server in India. The IP's first edit was to a sockpuppetry case. - MrX 11:45, 6 April 2016 (UTC)
77.246.236.98
– This proxy check request is closed and will shortly be archived by a bot.
- 77.246.236.98 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Open on port 8080 Reason: Suspicious edits
109.232.106.142
– This proxy check request is closed and will shortly be archived by a bot.
- 109.232.106.142 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Open on port 3128 Reason: Suspicious edits
- Open proxy operating on port 3128 redirect both SSL and non-SSL requests. Regards—UY Scuti Talk 01:26, 7 April 2016 (UTC)
64.53.146.142
– This proxy check request is closed and will shortly be archived by a bot.
- 64.53.146.142 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on jawp.--HotKorokke (talk) 14:31, 8 April 2016 (UTC)
186.90.75.38
– This proxy check request is closed and will shortly be archived by a bot.
- 186.90.75.38 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits on jawp.--HotKorokke (talk) 14:33, 8 April 2016 (UTC)
191.242.79.6
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 191.242.79.6 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
open ports Reason: Suspicious edits
202.79.48.218
– This proxy check request is closed and will shortly be archived by a bot.
- 202.79.48.218 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
open ports Reason: Suspicious edits
177.126.89.76
– This proxy check request is closed and will shortly be archived by a bot.
- 177.126.89.76 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Many open ports including 8080 Reason: Suspicious edits
89.207.66.27
– This proxy check request is closed and will shortly be archived by a bot.
- 89.207.66.27 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
open on ports 80,443, 3389 Reason: Suspicious edits
177.55.253.68
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 177.55.253.68 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
multiple open ports, proxy on at least 8080 Reason: Suspicious edits
190.15.222.53
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 190.15.222.53 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
open proxy port 8080 Reason: Suspicious edits
See also
Subpages
- Blacklist of open or zombie proxies
- Information for blocked users
- List of users who can verify proxies
- Preventing access to Wikipedia from your Tor node
Related pages
- Policy on open proxies
- Open proxy detection
- Guide to checking open proxies
- Proxy check result templates
- Advice to users using Tor to bypass the Great Firewall
- meta:XFF project
- Tor exit checker
Chapters
|