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: The range seems to be announced by IPXO (per Hurricane Electric), an "IP marketplace" according to their website. All IPs in the range who have made contributions since 1 January 2023 are active on ExpressVPN, as well as a handful of varying residential proxies according to Spur. I've not done a fully exhaustive check on the range yet, but the only IPs I've seen not flagged as ExpressVPN on the Spur data are .251-.255, though they are still listed as data centre IPs.
It may also be worth the other /24s listed on HE as being announced by IPXO as well for any that haven't yet been blocked (some have) but probably should be. Sideswipe9th (talk) 20:56, 4 February 2023 (UTC)Reply[reply]
Ok, I've checked through the other /24s listed. Most are either locally or globally blocked (sometimes both), but I did find a list of 20 /24 ranges that are not currently blocked. I'll check through that list now and see if I can categorise them briefly before posting them. Sideswipe9th (talk) 21:32, 4 February 2023 (UTC)Reply[reply]
Done some spot checks on the other /24s, alas I don't have the tools or time to do a full check on each range. Results below split into three categories; ExpressVPN, data centre and possible unknown proxy, and unknown. The four ExpressVPN ranges are the ones I'm most confident on, there was only a few IPs in each range for which all were at a consistent last octet that weren't showing as ExpressVPN exit nodes, and the unknown ones at the end are the ones I'm least confident on.
With all of the ranges currently being assigned by IPXO, I suspect the potential for any individual IP in a range to become a proxy or VPN exit node at random is high, even if the range itself is largely not proxy or VPN exit nodes at this time.
✔️ 163.5.123.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - last active january 2023 - ExpressVPN on Spur and IPQS, compromised servers on ProxyCheck
✔️ 192.101.67.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - last active february 2023 - ExpressVPN and callback proxy on Spur, ExpressVPN on IPQS, unknown VPN on ProxyCheck
Data centre and possible unknown proxy:
✔️ 45.62.162.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - datacenter range, no proxys on Spur, unknown VPN detected on ProxyCheck and IPQS
45.151.1.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - datacenter range, no proxies on Spur, unknown VPN detected on ProxyCheck and IPQS
89.47.15.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - last active locally 2017 - datacentre range? no VPN usage on Spur, some on IPQS and ProxyCheck
89.116.202.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - datacenter on Spur, ExpressVPN on IPQS, unknown VPN on ProxyCheck
115.167.79.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - datacenter on Spur, ExpressVPN on IPQS, unknown VPN on ProxyCheck
86.38.235.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - last active locally 2014 - some webhosts, some random servers belonging to various domains, no VPN usage on Spur and IPQualityScore, some on Proxycheck
89.116.76.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - assigned by IPXO, no VPN usage on SPUR, ExpressVPN on IPQS, unknown proxy on ProxyCheck
89.116.96.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - random servers on various domains, no VPN or datacenter flags on Spur, ExpressVPN on IPQualityScore and ProxyCheck
89.116.123.0/24 ·contribs·block·log·stalk·Robtex·whois·Google - never active locally - random servers on various domains, no VPN or datacenter flags on Spur, ExpressVPN on IPQualityScore and ProxyCheck
McAfee WGCS is a corporate gateway, technically a VPN, but last time it was discussed here, it was not blocked. Requesting a second opinion. MarioGom (talk) 21:43, 26 April 2023 (UTC)Reply[reply]
Not an admin, so feel free to ignore. Looking at the two prior discussions on this (March 2021, May 2022) it seems that softblocking might be appropriate in this case? There are some McAfee WGCS ranges that we do currently softblock (eg 185.221.70.0/24, 208.81.64.0/21) so this would at least be consistent with them, though there are other ranges that we don't currently softblock (eg 185.125.227.0/24).
Whatever the decision is from this discussion, we may want to look at making things consistent across all of the known ranges. Sideswipe9th (talk) 21:56, 26 April 2023 (UTC)Reply[reply]
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[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[reply]
UnlikelyIP is an open proxy While ipcheck states it's likely a proxy due to some API data, I'm not seeing any activity on Spur and Shodan, and technical research into the IP didn't turn up anything of note. However, the /48 range this IP belongs to is currently announced by a web and VPS hosting provider from Germany, and the /32 range is assigned to a colocation provider also in Germany. A webhostblock on the /48 or a colocationwebhost block on the /32 might be appropriate in the circumstances. Flagging for a second opinion though because either choice is a big range. Sideswipe9th (talk) 20:26, 17 July 2023 (UTC)Reply[reply]
I agree a webhost block on the /47 could be appropriate. Flagging for admin attention for the final call. MarioGom (talk) 09:10, 27 August 2023 (UTC)Reply[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[reply]
Confirmed as to the ranges with "Customers" in the name (/26), but I didn't check them all. This might also be a job for the ASNbot (AS40994) @AntiCompositeNumber: — Mdaniels5757 (talk • contribs) 00:36, 8 December 2023 (UTC)Reply[reply]
Reason: Requested unblock. I'm unable to edit wikipedia pages from this IP (our office) even when logged in. The IP is statically allocated to us (since Feb 2022), we're not running any proxy and I'm not seeing any unusual open ports or suspicious network activity. xmath (talk) 19:30, 30 June 2023 (UTC)Reply[reply]
Update: never mind, the block isn't for our IP specifically, apparently the entire IP range has been mistakenly classified as webhosting instead of FTTH/FTTB. xmath (talk) 20:59, 30 June 2023 (UTC)Reply[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[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[reply]
@Bri:IP is an open proxy, but not in active use: last edits were ~6mo ago, so I think no action is needed. If a passing admin wants to block I won't object though. — Mdaniels5757 (talk • contribs) 01:10, 4 January 2024 (UTC)Reply[reply]
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.
