Wikipedia:WikiProject on open proxies/Requests
 | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
 | Looking to make a new report? You're in the wrong place! Please go to Wikipedia:WikiProject on open proxies#Reporting and fill in the relevant box. |
| Index |
|
This page has archives. Sections older than 41666.5 days may be automatically archived by ClueBot III when more than 5 sections are present. |
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)
- I've checked the three /24s separately here (165.85.64.0/24 · contribs · block · log · stalk · Robtex · whois · Google - 165.85.65.0/24 · contribs · block · log · stalk · Robtex · whois · Google - 165.85.66.0/24 · contribs · block · log · stalk · Robtex · whois · Google). While the ISP is Amazon, all three ranges are currently allocated to Palo Alto Networks. The first range, 165.85.64.0/24, appears to be used for part of their GlobalProtect VPN service per Spur's data. This seems similar to the McAfee WGCS and Zscaler ranges currently reported on this page, and any hardblock on these ranges would have some collateral on legitimate users. A softblock/{{Colocationwebhost-soft}} might be appropriate here. The other two ranges in the /22 seem to be in the same data centre, and don't seem to be part of the same service, but the filter log linked above is from an IP on the third /24 so it clearly has some use somewhere. Not sure what to recommend here, and I've not been able to easily search to see if any other IPs in the range have triggered any filters, though none have any recorded contributions. Sideswipe9th (talk) 18:17, 17 July 2023 (UTC)
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)
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)
103.23.206.0/23
[edit]
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason: Requested unblock or softening. Non-proxy collateral on this range. - RichT|C|E-Mail 01:23, 15 November 2024 (UTC)
93.127.170.206
[edit]
– This proxy check request is closed and will soon be archived by a bot.
- 93.127.170.206 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: VPN; cf. Spur. Eryk Kij (talk) 15:03, 16 November 2024 (UTC)
Open proxy blocked. Spur identifies this IP as belonging to the Express VPN anonymization network. --Malcolmxl5 (talk) 15:15, 16 November 2024 (UTC)
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)
Closing without action. The range has been globally blocked and no further action is needed. --Malcolmxl5 (talk) 23:15, 16 November 2024 (UTC)
