Jump to content

Wikipedia:Open proxies noticeboard

From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:OPP)
For information about open proxies, see WP:Open proxies.
    Open proxies noticeboard
    Shortcuts

    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.

    Open proxies may be blocked from editing


    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]
    This section is transcluded from /Requests. (edit | history)


    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]

    162.120.128.0/17

    [edit]

    – This proxy check request is closed and will soon be archived by a bot.

    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]
    VPN by Google is a successor to Google One VPN, a subscription service, which was discontinued in June 2024 due to low takeup. It is a free VPN offered with Pixel 7 (and later) devices and also Google Fi wireless, a mobile phone plan service. — Malcolmxl5 (talk) 14:56, 5 November 2025 (UTC)[reply]
     Completed. /17 blocked. A free VPN from Google. Malcolmxl5 (talk) 15:11, 5 November 2025 (UTC)[reply]

    45.129.86.225

    [edit]

    – This proxy check request is closed and will soon be archived by a bot.

    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]

    Agreed. VCCL Cloud Private Limited (brand name VCCLHosting) provide web hosting and colocation services per their website. The cidr is 45.129.86.0/23. — Malcolmxl5 (talk) 16:56, 5 November 2025 (UTC)[reply]
     Completed. /23 blocked as colocation webhost. Malcolmxl5 (talk) 17:06, 5 November 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.

    Group 1
    199.168.148.0/22 · 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
    Group 2
    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
    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. Kline • talk • contribs 04:47, 2 November 2025 (UTC)[reply]

    I have taken the liberty of rearranging the list into two groups. --Malcolmxl5 (talk) 13:51, 5 November 2025 (UTC)[reply]
    @Xaosflux. A consensus emerged at WP:AN some time ago (Wikipedia:Administrators' noticeboard/Archive324#zscaler proxies) that Zscaler ranges ought be softblocked rather than hardblocked as it operates a closed proxy and not an open proxy. Would you be willing to modify the global blocks of the ranges listed in Group 2 to allow logged-in users to edit? — Malcolmxl5 (talk) 14:07, 5 November 2025 (UTC)[reply]
    We continue to get global disruption from this proxy across projects. If you would like to allow these, you could unblock them locally (use Special:GlobalBlockWhitelist) , then reblock with whatever setting you want. People using other people's computers can also ask their administrator to whitelist our domains, assuming their administrators want their computers used for those purposes. — xaosflux Talk 14:16, 5 November 2025 (UTC)[reply]
    OK, thanks Xaosflux. — Malcolmxl5 (talk) 14:57, 5 November 2025 (UTC)[reply]

    91.124.120.73

    [edit]

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

    2 hits on ipcheck, geo-mismatch on Spur. C F A 18:42, 10 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)
    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Open_proxies_noticeboard&oldid=1299577075"