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]


    23.134.88.0/24

    [edit]

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

    Reason: IP Range belongs to Cloudie Networks, a cloud/VPS provider. Range info X2step (talk) 00:29, 23 September 2025 (UTC)[reply]

    141.101.181.0/24

    [edit]

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

    Reason: Marked as datacenter by Spur, Whois search on IP comes back to Scloud, a VPS/hosting company. X2step (talk) 04:12, 23 September 2025 (UTC)[reply]

    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 · log · 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]

    Similar proxy IPs

    [edit]

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

    Reason: Bit more complex request here, all have been vandalizing Adrian Barber (along with a lot of older reverted edits) under the same parameters (mobile iOS app) along with coming from similar ISPs. IPCheck lists them all as proxies and Spur as datacenters.. curious. Klinetalkcontribs 00:56, 27 September 2025 (UTC)[reply]

    38.23.34.78 and 38.23.46.55 are now globally blocked so we need not worry about those. I took a look at the history of Adrian Barber and blocked 211.34.80.37 as a VPNGate VPN.
    That leaves 63.135.170.112. We can also consider 63.135.170.113 and 63.135.170.114 (see 63.135.170.112/30). These are owned by MacStadium, a hosting provider of cloud solutions for businesses. The domain for 63.135.170.112 and 63.135.170.113 appears to be appetize.io, a provider of ‘cloud mobile emulators'; I couldn’t ID the other. I don’t think we should really be seeing editing from these internet connections, much of which has been disruptive, which suggests vulnerabilities have been exploited. I note that 63.135.170.0/24 is blocked as an 'open proxy or zombie' on Meta. I will block 63.135.170.0/24 as a webhost.
    Open proxy blocked. 63.135.170.0/24 blocked as a webhost. Also 211.34.80.37 blocked as a VPNGate VPN. 38.23.34.78 and 38.23.46.55 are globally blocked. Malcolmxl5 (talk) 14:06, 27 September 2025 (UTC)[reply]

    103.230.213.253

    [edit]

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

    Reason: VPNGate proxy via Google search. x2step (lets talk 💌) 08:16, 28 September 2025 (UTC)[reply]

    Open proxy blocked. VPNGate VPN. Malcolmxl5 (talk) 08:55, 28 September 2025 (UTC)[reply]

    50.47.140.58

    [edit]

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

    Reason: SoftEther/VPNGate proxy. x2step (lets talk 💌) 22:08, 28 September 2025 (UTC)[reply]

    Open proxy blocked. VPNGate VPN. Malcolmxl5 (talk) 12:59, 29 September 2025 (UTC)[reply]

    179.228.177.69

    [edit]

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

    Reason: SoftEther/VPNGate proxy. x2step (lets talk 💌) 06:00, 1 October 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)