|
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/20150928133153im_/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
![]() Ancient Archives |
||
---|---|---|
|
||
![]() Current Archives |
---|
2012ish
2013ish 2014ish 2015ish |
199.19.250.123
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 199.19.250.123 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits, involved with logged-in editor suspected of COI [1]; host lookup says "Blue Coat Systems, Inc cloud services".
198.136.25.82
– This proxy check request is closed and will shortly be archived by a bot.
- 198.136.25.82 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits at article prone to autobio [2], host lookup said Gorilla Servers
69.87.100.1
– This proxy check request is closed and will shortly be archived by a bot.
- 69.87.100.1 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits associated with COI editor; host lookup at whatismyip.com says IP is a known proxy.
- The is the exit node for a corporate proxy, not an open proxy or webhost. I can see all sorts of interesting COI edits related to some of the entities in that "family" which sort of confirms this. Just block like a regular shared IP if there's too many bad edits. Kuru (talk) 02:15, 16 August 2015 (UTC)
145.226.158.81 / 145.226.158.82
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 145.226.158.81 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 145.226.158.82 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Used to evade active block in zhwiki, and the IP also edit here. The IP is from France but other IPs used by that zhwiki user is from Germany.--GZWDer (talk) 02:02, 20 August 2015 (UTC)
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)
2C0F:F930:0:3:0:0:0:221
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 2C0F:F930:0:3:0:0:0:221 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
I just reverted some vandalism which does not need any follow up, but when I looked at the IP's talk (User talk:2C0F:F930:0:3:0:0:0:221) is saw a claim "This is a Tor exit node.2C0F:F930:0:3:0:0:0:221 (talk) 13:01, 16 August 2015". I'm hoping someone will take any action necessary, but it's a not a problem at the moment. Johnuniq (talk) 02:33, 26 August 2015 (UTC)
- Can't do much checking now. Their global contributions indeed suggest international sharing. This tool doesn't identify the IP as Tor; the tool used to work well with ipv4, but I'm not sure about ipv6. Materialscientist (talk) 03:06, 26 August 2015 (UTC)
104.238.83.28
– This proxy check request is closed and will shortly be archived by a bot.
- 104.238.83.28 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. A persistent sockpuppet of user: Asdisis hiding behind a proxy. - MrX 17:50, 27 August 2015 (UTC)
Open proxy ip-104-238-83-28.ip.secureserver.net - port 443 (confirmed) and probably some other ports. -- zzuuzz (talk) 18:00, 27 August 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)
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)
2001:41D0:8:B330:0:0:0:1
– This proxy check request is closed and will shortly be archived by a bot.
- 2001:41D0:8:B330:0:0:0:1 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. Sock of Asdisis (talk · contribs · logs). - MrX 22:39, 27 August 2015 (UTC)
95.172.74.63
– This proxy check request is closed and will shortly be archived by a bot.
- 95.172.74.63 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits. WHOIS reports this is an open proxy from Zscaler. Brianhe (talk) 04:38, 30 August 2015 (UTC)
Open proxy blocked, 95.172.74.63:8080, already blocked by MaterialScientist. Kuru (talk) 13:01, 30 August 2015 (UTC)
109.192.2.224
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 109.192.2.224 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Appears to be connected to company called Wittenstein that sells a product called Fitbone - they trying to edit war PROMO content about that product into several articles. Reported at COIN here and was referred to this board. Jytdog (talk) 10:03, 31 August 2015 (UTC) Reason: Suspicious edits
- I don't see an open proxy there, but anonblocked per spam. Materialscientist (talk) 10:16, 31 August 2015 (UTC)
- It was reported as an open proxy here: http://whatismyipaddress.com/ip/109.192.2.224 — Brianhe (talk) 18:58, 31 August 2015 (UTC)
- It's actually reported as a 'confirmed proxy server', of which open proxies are possibly a subset. Likewise, I don't see that it's open (in fact I don't agree it's even a proxy), more like a relatively static broadband IP in Germany. -- zzuuzz (talk) 19:11, 31 August 2015 (UTC)
- It was reported as an open proxy here: http://whatismyipaddress.com/ip/109.192.2.224 — Brianhe (talk) 18:58, 31 August 2015 (UTC)
IP 220.255.3.185
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 220.255.3.185 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits
- This IP was asking some questions about socking at WP:AN#Sock abuse under protection, as well as talking back to User:Drmies about an SPI case. A web search for 220.255.*.* shows some generally-advertised proxy services based in Singapore. May not be this exact range, though. This IP gets some hits from a spam finder at Cleantalk. There are seven hits in the SPI directory for cases that contain the string '220.255'. EdJohnston (talk) 02:39, 3 September 2015 (UTC)
It looks like a duck to me. I recognise this proxy user. Apart from that, getting close, 220.255.3.170:80 exits at 220.255.3.186. A few more rolls of the dice might nail it. If not, it's a duck. -- zzuuzz (talk) 03:07, 3 September 2015 (UTC)
- I can't proxy-check it now (and would leave this to zzuuzz anyway), but CU scan shows that this IP is shared, is not particularly active, and was abused by an unrelated spambot yesterday. Materialscientist (talk) 03:13, 3 September 2015 (UTC)
112.79.38.210
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 112.79.38.210 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits
- See this AN/I thread. BMK (talk) 02:58, 5 September 2015 (UTC)
- Block evasion, yes, but I don't see an open proxy there. Materialscientist (talk) 03:07, 5 September 2015 (UTC)
104.238.169.86
– A proxy check has been completed and it is now awaiting administration and close.
- 104.238.169.86 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- Per http://whatismyipaddress.com/ip/104.238.169.86, "Confirmed proxy server, Recently reported forum spam source."
- Trolling User talk:Jimbo Wales: [3], [4]
Reason: Suspicious edits
- Blocked. Materialscientist (talk) 12:18, 8 September 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.
119.81.135.18
– A proxy check has been completed and it is now awaiting administration and close.
- 119.81.135.18 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Suspicious edits BMK (talk) 13:09, 10 September 2015 (UTC)
- Blocked. Materialscientist (talk) 23:25, 10 September 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[5] 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)
122.3.238.242
– A proxy check has been completed and it is now awaiting administration and close.
- 122.3.238.242 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Disruptive edit of WP:OR by a sockpuppet using OpenVPN as Open proxy.[6]
- Blocked, thanks. Materialscientist (talk) 22:57, 18 September 2015 (UTC)
174.142.138.234
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 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)
168.1.23.79
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 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)
95.141.31.6
– A user has requested a proxy check. A proxy checker will shortly look into the case.
- 95.141.31.6 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.141.31.8 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.141.31.9 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.141.31.22 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.141.31.23 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.141.31.24 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
- 95.141.31.25 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Reason: Cyberghost proxy. 95.141.31.6 to 9 and 95.141.31.22 to 25
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
|