Jump to content
Wikipedia The Free Encyclopedia

Wikipedia:Open proxies noticeboard

From Wikipedia, the free encyclopedia
For information about open proxies, see WP:Open proxies.
Open proxies collaboration
Wikipedia's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles,
content
Page handling
User conduct
Other
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.

Pre-2012 Archives

Old archives

New archives


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.

Before reporting any suspected open proxies here, please remember that not all vandals are open proxies and vandals should not get an automatic check here; remember that it takes the volunteers here about 5-10 minutes to give a request a thorough check.
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)



2012-present Archives
6, 7, 8, 9, 10, 11, 12, 13, 14, 15
16, 17, 18, 19, 20, 21, 22, 23, 24, 25
26, 27, 28, 29, 30, 31, 32, 33, 34, 35
36, 37, 38, 39, 40, 41, 42, 43, 44, 45
46, 47, 48, 49, 50, 51, 52, 53, 54, 55

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 ]

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 ]

144.130.171.182

[edit ]

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

Reason: FortiClient VPN hit by Spur. Kline • talk • contribs 22:53, 19 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)
This is a WikiProject, an open group of Wikipedia editors. New participants are welcome; feel free to talk to us!
General
Directories and reports
Culture and the arts
Geographical
History and society
Science, technology
and engineering
Wikipedia assistance
and tasks

AltStyle によって変換されたページ (->オリジナル) /