Jump to content

Wikipedia:WikiProject on open proxies

From Wikipedia, the free encyclopedia
"WP:OP" redirects here. For other uses, see WP:Open proxies.
    WikiProject on open proxies
    Shortcuts

    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.

    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.
    Verified Users/Sysops Templates
    • IP is an open proxy {{Proxycheck|confirmed}} for confirmed open proxies and Tor exit nodes.
    •  Likely IP is an open proxy {{Proxycheck|likely}} for likely open proxies and Tor exit nodes.
    •  Possible IP is an open proxy {{Proxycheck|possible}} for possible open proxies and Tor exit nodes.
    •  Unlikely IP 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.
    • no Declined to 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.

    Requests

    [edit]
    This section is transcluded from /Requests. (edit | history)

    165.85.64.0/22

    [edit]

    – A proxy checker has requested a second opinion on this case.

    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]

    209.35.227.0/24

    [edit]

    – A proxy checker has requested a second opinion on this case.

    Reason: VPN. Perimeter 81. 73.67.145.30 (talk) 18:43, 15 May 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]

    103.23.206.0/23

    [edit]

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

    103.23.206.0/23 · contribs · block · log · stalk · Robtex · whois · Google

    Reason: Requested unblock or softening. Non-proxy collateral on this range. - RichT|C|E-Mail 01:23, 15 November 2024 (UTC)[reply]

    @Rich Smith. Have you discussed this with the blocking admin ST47? Malcolmxl5 (talk) 22:07, 19 November 2024 (UTC)[reply]

    93.127.170.0/23

    [edit]

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

    Reason: VPN (Express VPN); per the former request. Also blocked in several projects (cf. Stalk toy). Eryk Kij (talk) 15:57, 16 November 2024 (UTC)[reply]

    Iranian rangehopper

    [edit]

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

    Reason: Dubious edits, dubious geolocation. SPA rangehopping, at the least, but smells proxy-ish to me. ☆ Bri (talk) 04:18, 19 November 2024 (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:WikiProject_on_open_proxies&oldid=1253336048"