Wikipedia:WikiProject on open proxies
| This is a WikiProject, an area for focused collaboration among Wikipedians. New participants are welcome; please feel free to join! |
| Before reporting any suspected open proxies here, please remember that not all vandals are open proxies and vandals should not get an automatic check here; remember that it takes the volunteers here about 5-10 minutes to give a request a thorough check. |
| 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. |
Contents |
Reporting[edit]
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[edit]
Current Archives |
|---|
| 2011 |
88.12.3.152[edit]
A user has requested a proxy check. A proxy checker will shortly look into the case.
- 88.12.3.152 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: This proxy check indicates that it's an open proxy, not to mention that it has been blocked by the proxy bot in the past as well. 47.149.143.100 (talk) 19:29, 4 October 2018 (UTC)
185.180.196.0/22[edit]
– This proxy check request is closed and may now be archived.
- 185.180.196.0/22 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: All IP addresses from 185.180.196.0 to 185.180.199.255 belong to King Servers (dedicated webhosting servers). 2601:1C0:4401:24A0:F427:6E8F:5237:1F6F (talk) 05:23, 11 October 2018 (UTC)
79.115.41.253[edit]
– This proxy check request is closed and may now be archived.
- 79.115.41.253 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Apparent proxy/attack source. 2601:1C0:4401:24A0:7D2D:D646:4903:9614 (talk) 05:42, 12 October 2018 (UTC)
151.237.192.0/19 & 176.56.96.0/19[edit]
– This proxy check request is closed and may now be archived.
- 151.237.192.0/19 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
- 176.56.96.0/19 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Both IP ranges belong to "ServiHosting Networks S.L." (webhosting/dedicated server networks). 73.240.4.160 (talk) 05:51, 12 October 2018 (UTC)
103.254.208.0/22[edit]
– This proxy check request is closed and may now be archived.
- 103.254.208.0/22 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Active IP range that was recently active on 103.254.208.148 (talk · contribs · WHOIS). This range has been blocked in the past. 2601:1C0:4401:24A0:D30:1D07:A2EE:90DB (talk) 07:14, 22 October 2018 (UTC)
172.83.40.67[edit]
– This proxy check request is closed and may now be archived.
- 172.83.40.67 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Suspicious edits
- WHOIS states that the /24 range at 172.83.40.0/24 is operated by Total Server Solutions. From their web site they are a web hosting company. Edits from this range have been reported at WP:AN3. I've blocked the range for three months anon-only as {{webhostblock}}. Offering this for review here to be sure I did it correctly. If confirmed, a block of one year or more might be reasonable. EdJohnston (talk) 20:55, 23 October 2018 (UTC)
- EdJohnston, Yep - that's a hosting range. I've re-blocked it as a 1-year long hardblock, and cleaned up the other non-blocked TSS ranges. SQLQuery me! 23:08, 8 November 2018 (UTC)
192.93.8.156[edit]
– This proxy check request is closed and may now be archived.
- 192.93.8.156 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Used by country-hopping spammer. IamNotU (talk) 22:33, 2 November 2018 (UTC)
- IamNotU -
Unlikely IP is an open proxy. Unfortunately, I wasn't able to find any technical evidence that this IP is presently an open proxy. SQLQuery me! 03:03, 9 November 2018 (UTC)
80.179.42.39 Comment[edit]
– This proxy check request is closed and may now be archived.
- 80.179.42.39 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Used by obvious sock of Shingling334 known to use proxies, ipqualityscore.com score 95 "Proxy/VPN Detected" IamNotU (talk) 22:52, 8 November 2018 (UTC)
- IamNotU, HQServ indeed appears to be a VPS. Blocked, and I'll try to find more ranges belonging to this hosting provider to block. SQLQuery me! 02:57, 9 November 2018 (UTC)
72.46.128.0/19[edit]
A user has requested a proxy check. A proxy checker will shortly look into the case.
- 72.46.128.0/19 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Requested unblock of part of range. Blocked by User:Elockid on 00:23, 5 October 2015. User:Elockid has gone AWOL, so I cannot ask them. http://whois.domaintools.com/72.46.128.0 shows the range to Versaweb as a /20 (not /19), and I have a user on OTRS (caught in the block) at 72.46.148.212 - they are coming up as a different company (United Electric Cooperative in a different state) (http://whois.domaintools.com/72.46.148.212), and it appears the user is correct when they say they are on a static broadband (https://whatismyipaddress.com/ip/72.46.148.212). Maybe Versaweb have sold on some of their allocation? They could obviously go for IPBE, but if the block is too wide we may be losing other legitimate editors. It would make more sense to fix the range block size. Ronhjones (Talk) 17:52, 10 November 2018 (UTC)
- I also found https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/72.46.148.212 Ronhjones (Talk) 20:24, 12 November 2018 (UTC)
107.77.249.6 Comment[edit]
A user has requested a proxy check. A proxy checker will shortly look into the case.
- 107.77.249.6 - talk - edits - block - log - current blocks - ipinfo - Robtex - WHOIS - proxy checker - Google - HTTP - stalk
Reason: Long history of vandalism and blocks, "confirmed proxy server" by whatismyipaddress.com, proxy score 100 at ipqualityscore.com. IamNotU (talk) 22:23, 14 November 2018 (UTC)
See also[edit]
Subpages[edit]
- 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[edit]
- 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