Wikipedia:Open proxies noticeboard

    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

    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


    96.82.59.129

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

    Reason: Says this is a "callback proxy". Might be fine or not. S0091 (talk) 21:07, 1 December 2025 (UTC)[reply]

     Completed. Callback proxies are device specific and typically shortlived. There doesn’t appear to be an attempt to mask location (a U.S. IP editing U.S. topics). Last edit was two months ago. No action needed. Malcolmxl5 (talk) 00:19, 7 January 2026 (UTC)[reply]

    IP 23.247.0.0/17

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

    Reason: AMAZON-02, US hit by bullseye Peterxytalk16:01, 5 December 2025 (UTC)[reply]

     Completed. Globally blocked. Malcolmxl5 (talk) 00:23, 7 January 2026 (UTC)[reply]

    57.140.0.0/16

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

    Reason: The IP infobox lists this as a tunnel operator (and I've seen geolocations on multiple continents). It looks like they operate an enterprise system as well as some sort of proxy service. Most of the edits have been benign updates (insofar as the specific commanders of ships seem to be concerned) but some vandalism does wiggle through and I assume those are mostly coming from the proxy part of the range. Izno (talk) 06:14, 8 December 2025 (UTC)[reply]

     Completed. Blocked by Yamla. Malcolmxl5 (talk) 00:24, 7 January 2026 (UTC)[reply]

    162.239.157.2

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

    Reason: FortiClient VPN hit by Spur. Klinetalkcontribs 17:36, 11 December 2025 (UTC)[reply]

     Completed. A closed proxy. Access requires authorised credentials issued by a network administrator. Will block anon only. Malcolmxl5 (talk) 00:32, 7 January 2026 (UTC)[reply]

    205.147.22.0/24

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

    Reason: Active Proton VPN range. Klinetalkcontribs 20:54, 27 December 2025 (UTC)[reply]

     Completed. Globally blocked. Malcolmxl5 (talk) 00:39, 7 January 2026 (UTC)[reply]

    185.219.157.0/24

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

    Reason: Various proxies and VPNs on this range. Not sure whether the whole range has been filled with them, but some of them are definitely VPNs and are actively being used. Klinetalkcontribs 21:04, 10 January 2026 (UTC)[reply]

     Completed. I've blocked the /24 range as a colocation/webhost (Delska) with several Browsec VPNs observed on the range. Malcolmxl5 (talk) 16:28, 11 January 2026 (UTC)[reply]

    173.255.170.0/24

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

    Reason: IPVanish range. Klinetalkcontribs 15:53, 12 January 2026 (UTC)[reply]

     Completed. I've blocked 173.255.160.0/19 as a colocation/webhost (ServerMania) with multiple White Label/IPVanish VPNs observed on the range. Malcolmxl5 (talk) 17:02, 12 January 2026 (UTC)[reply]

    64.145.79.0/24

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

    Reason: Latitude.sh range with various WhiteLabel VPNs. Klinetalkcontribs 17:36, 12 January 2026 (UTC)[reply]

    Hmm, the /24 is registered to NetProtect, which owns some VPN brands, so it wouldn’t be a surprise to see VPNs popping up in the range. I see the /19 has been blocked previously, I'll take a look at that. — Malcolmxl5 (talk) 20:08, 12 January 2026 (UTC)[reply]
     Completed. Looked at the /19. 64.145.64.0/22 is globally blocked until 2028. I've blocked 64.145.76.0/24, 64.145.79.0/24, 64.145.91.0/24, 64.145.93.0/24 and 64.145.94.0/24 as NetProtect ranges with VPNs observed on them. --Malcolmxl5 (talk) 20:52, 12 January 2026 (UTC)[reply]

    2A0C:F040:0:0:0:0:0:0/32

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

    Reason: Oy Crea Nova range with Mullvad and Cryptostorm hits. Klinetalkcontribs 17:40, 12 January 2026 (UTC)[reply]

     Completed. CIDR is /48, blocked as a colocation webhost provider with Adguard and Mullvad VPNs observed. --Malcolmxl5 (talk) 21:25, 12 January 2026 (UTC)[reply]

    158.173.154.0/24

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

    Reason: Datacamp range with CyberGhost VPN hits. Klinetalkcontribs 17:43, 12 January 2026 (UTC)[reply]

    158.173.155 and 158.173.156 appear to be the same as well. Klinetalkcontribs 17:44, 12 January 2026 (UTC)[reply]
     Completed. And a few others, /21 seems to cover them all. Blocked as a colocation webhost provider with multiple PIA and Cyber Ghost VPNs observed. Malcolmxl5 (talk) 22:09, 12 January 2026 (UTC)[reply]

    Automated lists and tools

    • 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

    Subpages
    Related pages
    Sister projects (defunct)