Jump to content

Wikipedia:Open proxies noticeboard

From Wikipedia, the free encyclopedia
    Open proxies noticeboard

    The Open proxies noticeboard 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.


    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 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.

    Requests

    [edit]


    2605:a141:2231:149::/64

    [edit]

    A user has requested a proxy check. A proxy checker will shortly look into the case.

    2605:a141:2231:149::/64 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google

    Reason: Requested unblock.

    This IP address range is one which was assigned to me by Contabo (German web hosting service), and I am in sole control of it.

    While I do use it as a proxy while abroad, it is not an open proxy, and I am the only user of it.

    NateNate60 (talk) 19:00, 24 September 2025 (UTC)[reply]
    
    @NateNate60. A steward has globally blocked 2605:a140::/30 across all wikis. I suggest you make a request for IP block exemption, see m:Global IP block exemptions, to allow you to edit through this range block. — Malcolmxl5 (talk) 10:36, 26 September 2025 (UTC)[reply]

    103.137.24.0/22

    [edit]

    – A proxy checker has requested administrator assistance for action regarding the case below. The requested action is below.

    103.137.24.0/22 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google

    Reason: Requested unblock: this government ISP (Special Communications Organization) provides residential services, and does not seem to be a proxy. (ACC related) — Mdaniels5757 (talk • contribs) 15:09, 4 October 2025 (UTC)[reply]

    Agreed. This is Special Communications Organization, a public sector arm of the Pakistan Government responsible for developing, operating and maintaining internet and telecom infrastructure in the Azad Kashmir and Gilgit Baltistan regions. It is an eyeball network, ie one that is primarily used to browse the internet and read emails and so on. It does not appear to be a hosting provider nor does there appear to be any open proxies or VPNs. The IPs editors appear to be a mix of mobile and (presumably) desktop internet connections. A number of the mobiles are noted on Spur as belonging to call-back proxy networks but there doesn’t appear to be proxy use on-wiki.
    @Yamla. Would you be willing to unblock or to reduce the block to a soft-block with account creation enabled? Malcolmxl5 (talk) 01:44, 2 November 2025 (UTC)[reply]
    Historical technical data (I didn't check current data) shows widespread abuse of this range for a number of abusive sockpuppeteers and at least one spam farm operating from this address. This has been going on for several years. Optimistically, let's hope this all occurred when the range didn't belong to the Pakistan Government. I have modified the block to be anon-only. I don't want to just allow account creation at the moment, but specifically don't object if you wish to modify the block further if you want to try being more optimistic. --Yamla (talk) 11:51, 2 November 2025 (UTC)[reply]

    147.161.236.0/24

    [edit]

    A user has requested a proxy check. A proxy checker will shortly look into the case.

    Reason: Zscaler range, at least one active user of this range which was ID'd as a Zscaler proxy by Spur. Klinetalkcontribs 12:56, 24 October 2025 (UTC)[reply]

    Actually, it might be worth taking a look at the bigger ranges preceding this /24, looks like more Zscaler ranges. Klinetalkcontribs 12:58, 24 October 2025 (UTC)[reply]
     Completed. These are closed proxies, not open proxies. @Kline, Zscaler is a company that provides cybersecurity services to organisations at a price. Organisations use Zscaler products to provide employees with secure access to the internet usually to access internal applications, among other things. Users have to be authorised, authenticated and are closely monitored hence this is a closed proxy and not an open proxy that may be freely used by anyone. The risks of misuse are low and disruption, if any, can handled in the usual way. --Malcolmxl5 (talk) 23:36, 1 November 2025 (UTC)[reply]
    @Malcolmxl5 Looks like there might be a bigger problem on our hands, because the range has already been globally blocked and I have been under the guise that Zscaler's are open proxies (I have been on Zscaler range multiple times, always blocked). If this is the case, do unblocks need to be done? Klinetalkcontribs 23:51, 1 November 2025 (UTC)[reply]
    @Kline. I think there are differing opinions and I’m sure Zscaler has been discussed on en.wiki a number of times. The last discussion I can find (Wikipedia:Administrators' noticeboard/Archive324#zscaler proxies, 27 August 2020) appeared to reach a consensus that Zscaler should be soft-blocked and not be hard-blocked, which would allow logged in editing and prevent IP editing. if we can identify Zscaler ranges that are hard-blocked, we can look to have these reduced to soft-blocks. — Malcolmxl5 (talk) 00:47, 2 November 2025 (UTC)[reply]
    Well to start, the range here is globally hard blocked so that might be a place to start. I'll see if I can drum up some more ranges and submit them here for unblocking if possible. Klinetalkcontribs 00:51, 2 November 2025 (UTC)[reply]
    OK, I’ll compose a message for AramilFeraxa. — Malcolmxl5 (talk) 00:53, 2 November 2025 (UTC)[reply]
    @AramilFeraxa. Zscaler operates a closed proxy and not an open proxy as discussed above. Would you be willing to reduce the global block to a soft-block to allow logged-in users to edit? — Malcolmxl5 (talk) 00:55, 2 November 2025 (UTC)[reply]
    @Malcolmxl5  Done AramilFeraxa (talk) 11:00, 2 November 2025 (UTC)[reply]

    162.120.128.0/17

    [edit]

    A user has requested a proxy check. A proxy checker will shortly look into the case.

    Reason: ISP says "VPN by Google". Not sure if it's a VPN service provided by Google or if it's being used simply as a network. Either way this should be looked into. Thanks. ConnerTT (talk) 05:36, 25 October 2025 (UTC)[reply]

    I’m not familiar with this one. It appears to be a VPN service offered on Pixel phones and tablets. I’ll look into it. — Malcolmxl5 (talk) 02:04, 2 November 2025 (UTC)[reply]

    45.129.86.225

    [edit]

    A user has requested a proxy check. A proxy checker will shortly look into the case.

    Reason: Search showing IP is registered to VCCL Cloud Private Limited, a VPS/hosting company. x2step (lets talk 💌) 03:39, 29 October 2025 (UTC)[reply]

    Various Zscaler ranges

    [edit]

    – A proxy checker has requested administrator assistance for action regarding the case below. The requested action is below.

    199.168.148.0/22 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    175.107.128.0/18 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    101.2.192.0/18 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    209.55.128.0/18 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    87.58.64.0/18 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    209.55.192.0/19 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    137.83.128.0/18 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    185.46.212.0/22 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google
    198.14.64.0/18 · contribs · block · block log · active blocks · stalk · Robtex · whois · Google

    Reason: Following up from the previous Zscaler range report, these ranges should have their block downgraded to anonymous only. Note that some of these are globally blocked. Klinetalkcontribs 04:47, 2 November 2025 (UTC)[reply]

    Automated lists and tools

    [edit]
    • 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.
    • whois-referral is a generic WHOIS tool.
    • Range block finder finds present and past range blocks.

    See also

    [edit]
    Subpages
    Related pages
    Sister projects (defunct)