The WikiProject 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.
If you've been blocked as an open proxy, please see: Help:blocked.
To report a proxy check or an incorrect block, see the #Reporting section.
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.
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.
File a new report here
I.
For block requests:
Verify that the following criterion has been met:
The IP has made abusive contributions within the past week
For unblock requests:
Verify that the following criteria has been met:
No current criteria
II.
For block requests
Replace "IP" below with the IP address you are reporting.
For unblock requests
Replace "IP" below with the IP address you are reporting.
III.
Fill out the resulting page and fill-in the requested information.
IV.
Save the page.
Verified Users/Sysops Templates
IP is an open proxy((Proxycheck|confirmed)) for confirmed open proxies and Tor exit nodes.
LikelyIP is an open proxy((Proxycheck|likely)) for likely open proxies and Tor exit nodes.
PossibleIP is an open proxy((Proxycheck|possible)) for possible open proxies and Tor exit nodes.
UnlikelyIP is an open proxy((Proxycheck|unlikely)) for unlikely open proxies and Tor exit nodes.
Not currently an open proxy((Proxycheck|unrelated)) for IP's confirmed not to be an open proxy or Tor exit node.
Inconclusive((Proxycheck|inconclusive)) for IP's that are inconclusive.
Declinedto run a check((Proxycheck|decline)) to decline a check.
Open proxy blocked((Proxycheck|blocked)) for open proxies and Tor nodes that have been blocked. Please add this if you block the IP.
This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with ((no admin backlog)) when the backlog is cleared.
Reason: Amazon AWB. 165.85.64.0 - 165.85.66.255 are all registered to Amazon AWB, hence the /22 range in this report. BLP disruption caught by filter log. 73.67.145.30 (talk) 16:45, 28 April 2023 (UTC)[reply]
I've checked the three /24s separately here (165.85.64.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - 165.85.65.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - 165.85.66.0/24 ·contribs·block·log·stalk·Robtex·whois·Google). While the ISP is Amazon, all three ranges are currently allocated to Palo Alto Networks. The first range, 165.85.64.0/24, appears to be used for part of their GlobalProtect VPN service per Spur's data. This seems similar to the McAfee WGCS and Zscaler ranges currently reported on this page, and any hardblock on these ranges would have some collateral on legitimate users. A softblock/((Colocationwebhost-soft)) might be appropriate here. The other two ranges in the /22 seem to be in the same data centre, and don't seem to be part of the same service, but the filter log linked above is from an IP on the third /24 so it clearly has some use somewhere. Not sure what to recommend here, and I've not been able to easily search to see if any other IPs in the range have triggered any filters, though none have any recorded contributions. Sideswipe9th (talk) 18:17, 17 July 2023 (UTC)[reply]
Confirmed While the range is announced by Perimeter 81, and a large portion of it seems to be empty per Spur and Shodan, there are IP ranges within that are active on Perimeter 81's VPN product. However that product is aimed at businesses, with pricing to match. This seems similar to the Zscaler, McAfee WGCS cases that are also open at present. A softblock on the range might be appropriate however, the one contributor who was active on 15 May 2023 was using an IP that's part of their VPN range. While I've tried to pin down the exact range for just the IPs that are part of their VPN offering, it seems somewhat spread out throughout it with gaps, so it might be more expedient to just block it in its entirety. Flagging this for a 2O though, while we figure out how to handle this particular type of VPN provider. Sideswipe9th (talk) 00:22, 19 July 2023 (UTC)[reply]
Reason: Cloud server/VPN. This is an odd one, because the IP range geolocates to Turkey, and is listed as a VPN network; but most of the edits are to Turkish-related articles. Is this some sort of corporate cloud network? 2601:1C0:4401:F60:8C11:4CC3:7E71:B4CE (talk) 20:54, 13 August 2023 (UTC)[reply]
My reading is that this is a user or users in Turkey editing via a connection belonging to an enterprise, perhaps a business or a public body, that subscribes to cybersecurity services offered by Forcepoint. It looks to me like a corporate proxy. The contributions suggest a stable connection with largely unproblematic edits and I would not be inclined to take any action at this time. Malcolmxl5 (talk) 02:05, 20 January 2024 (UTC)[reply]
Reason: Same proxy sock that got blocked earlier for both ban evasion and editing with proxy. [1] He is still socking to restore the same article.[2][3]Ratnahastin (talk) 15:22, 8 March 2024 (UTC)[reply]
There’s a lot of blocks in the history, the most recent is a 3 month /12 block in September for block evasion. Malcolmxl5 (talk) 11:06, 13 March 2024 (UTC)[reply]
Reason:Listed ISP is FedEx which is not a legitimate provider, in addition these various FedEx proxy ranges are used by a LTA and extensive sock puppeteer HaughtonBrit to block evade and push tendentious edits in various South Asian topics. Southasianhistorian8 (talk) 21:13, 3 April 2024 (UTC)[reply]
Note sure how reliable this is, but it's identified as a VPN server on the goeloacate link on the contributions page. Assuming that's accurate, I suspect the VPN is being used by at least some one of the editors on this range to evade IP range blocks. Sir Sputnik (talk) 00:31, 12 May 2024 (UTC)[reply]
Seems to be a Menlo Security VPN. Checked using Spur (public version) and IPQualityScore and returned as a VPN. Edit history also indicates that it might be a shared IP. However, other services (shown on IPCheck) indicates that it may not be a proxy. ~~2NumForIce (speak|edits) 15:04, 16 May 2024 (UTC)[reply]
User admitted to being proxy after vandalizing pages. Interestingly, their Uncyclopedia page reveals that their IP is an open proxy for pawns.app. OhHaiMark (talk) 22:24, 29 May 2024 (UTC)[reply]
Reason: Amazon AWS webhosting services. Recently used for vandalism/disruption. 73.67.145.30 (talk) 15:59, 31 May 2024 (UTC)[reply]
Automated lists and tools
User:AntiCompositeBot/ASNBlock maintained by User:AntiCompositeBot is a list of hosting provider ranges that need assessment for blocks that is updated daily. Admins are encouraged to review the list and assess for blocks as needed. All administrators are individually responsible for any blocks they make based on that list.
ISP Rangefinder is a tool that allows administrators to easily identify and hard block all ranges for an entire ISP. It should be used with extreme caution, but is useful for blocking known open proxy providers. All administrators are individually responsible for any blocks they make based on the results from this tool.
IPCheck is a tool that can help provide clues about potential open proxies.
Bullseye provides information about IPS, including clues about potential open proxies.
