Wikipedia:WikiProject on open proxies

From Wikipedia, the free encyclopedia
  (Redirected from Wikipedia:ROP)
Jump to: navigation, search
Administration index MetaProject on open proxies (en-Wikipedia chapter)
 If you've been blocked as an open proxy, please see: Help:blocked.

The multiwiki MetaProject 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.


Contents

Proxyblock.png
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 criteria 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 For unblock requests
Replace "IP" below with the IP address you are reporting.


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]

217.115.10.133[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

217.115.10.133 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Blocked same as above, but seems to be a tor exit node (see whois info and https://www.ccc.de/anonymizer/). Tijfo098 (talk) 06:02, 18 October 2012 (UTC)

Blocked as tor. This is a small part of a wide tor project resolving to anonymizer.ccc.de, anonymizer.hamburg.ccc.de, torXX.anonymizer.ccc.de (where XX is a number from 1 to at least 33), etc., i.e., again, the tip of an iceberg. Materialscientist (talk) 05:54, 20 October 2012 (UTC)
Indeed. A few random tests:
  • tor5.anonymizer.ccc.de -> 80.237.226.75
  • tor10.anonymizer.ccc.de -> 62.113.219.3
  • tor15.anonymizer.ccc.de -> not registered
  • tor20.anonymizer.ccc.de -> 31.172.30.3
  • tor25.anonymizer.ccc.de -> not registered
  • tor30.anonymizer.ccc.de -> 77.244.254.230
They belong to various IPSs, but all are rented out to "Chaos Computer Club e.V." Tijfo098 (talk) 06:17, 20 October 2012 (UTC)
It's a bit more tricky: you can type the url into robtext and get their ranges, but those ranges are shared and the tor takes only a small part. For example, for 217.115.10.133, only 3 nearby IPs (trial-and-error check, not 100% sure) clearly relate to tor33.anonymizer.ccc.de, many others from the range belong to something else. And as usual, such shared ranges often host other semilegal services. Materialscientist (talk) 06:21, 20 October 2012 (UTC)
The whois info in this case is more helpful: 217.115.10.128 - 217.115.10.143 (a /28 it would seem) are all registered to CCC.de, although this is indeed less than the whole 217.115.0.0/20 Netsign PA Route. So you could issue a more discerning range block to the CCC /28. In the 80.237.226.72 - 80.237.226.79 case it's a /29 that is leased by CCC (out of the whole /17 route). If we go by the 80.237 precedent, the tor node(s) are eventually moved around the range(s) CCC rents. And it looks like the same R&I banned user was the sole editor from both of these. Tijfo098 (talk) 06:59, 20 October 2012 (UTC)

Known CCC.de ranges[edit]

Tijfo098 (talk) 07:07, 20 October 2012 (UTC)

Thanks. /29 contains only 6 IPs. If you check them individually in [1] you'll find that most of them (if not all) are already blocked one way or another, or don't clearly belong to the targeted tor. Materialscientist (talk) 07:17, 20 October 2012 (UTC)
Which ones do not? Tijfo098 (talk) 07:21, 20 October 2012 (UTC)
I judge that by robtex, which shows a different server for some nearby IPs in the range. Those tors usually take about 4 IPs/range, but ranges are many. Off course, we can always rangeblock a wider range if it is inactive, but then we might get justified unblock requests. Materialscientist (talk) 07:32, 20 October 2012 (UTC)
It looks to me like the only controversy here is over the 217.115.10.135 - 217.115.10.142 range (because you blocked the lower IPs of the last /28 I listed above) The 135-142 range is listed as allocated to CCC.de in whois, but none of those IPs respond to ping (unlike the lower IPs), so it looks like there's simply no hardware behind them, just yet. Tijfo098 (talk) 08:11, 20 October 2012 (UTC)

67.142.168.22 et al[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

67.142.168.22 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
67.142.168.23 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
67.142.168.25 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
67.142.168.27 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

All 3 4 IPs' geolocation data says "Confirmed proxy server". This, combined with several suspicious edits seem to suggest that something else is in play here.—Ryulong (琉竜) 20:42, 9 November 2012 (UTC)

  • The range 67.142.168.16/28 has been blocked by User:Coren - "Webhost/server farm hosting proxies". - Mike Rosoft (talk) 20:57, 24 November 2012 (UTC)
    • Being a confirmed proxy server isn't a problem by itself. This is a very odd range to have for farming, owned by DirecPC. Dennis Brown - © Join WER 14:43, 12 December 2012 (UTC)


69.22.184.113[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

69.22.184.113 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock.--Jezebel'sPonyobons mots 20:29, 25 July 2013 (UTC)

Sooooo..... this one is an oddball. It definitely belonged to the notorious anchorfree vpn service at one point. Now however, it seems like it's been passed on to a colo/backbone company. However, that doesn't mean it isn't a proxy. There's nothing saying it's not still in posession of anchorfree, nor is there any reason an editor would normally be editing from a colocation/internet backbone IP. Sooooo, could the editor maybe provide more information on why they need to be unblocked on this IP? Sailsbystars (talk) 01:38, 26 July 2013 (UTC)
I can see the associated user has access to a regular (unblocked) IP. As such I'm going to decline to unblock the possible proxy and advise them to edit through their regular IP only.--Jezebel'sPonyobons mots 17:25, 26 July 2013 (UTC)

User talk:Ukexpat[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

5.56.23.148 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
62.152.39.158 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
176.53.45.15 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
200.53.156.244 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
31.3.154.189 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
62.152.39.188 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
128.127.107.49 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
185.25.87.20 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
Posting not to forget, can't check myself now. Looks like VPN, all have http (80) and pptp (1723) ports open, altushost.com, but not only. Materialscientist (talk) 09:01, 26 July 2013 (UTC)


Doing A quick search, both the formermost and The lattermost appear to be Anon Proxys Happy_Attack_Dog (Throw Me a Bone) 18:37, 3 October 2014 (UTC)

All but one are currently rangeblocked. 200.53.. does not appear to be currently open. -- zzuuzz (talk) 20:59, 26 January 2015 (UTC)

212.74.97.221[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

212.74.97.221 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits/editing from a confirmed corporate proxy. — Preceding unsigned comment added by GabeMc (talkcontribs)

 Unlikely IP is an open proxy Does not appear to be an open proxy. The only source claiming proxy is the hopelessly useless (for proxy status) whatismyipaddress.com. It looks like a regular broadband ISP IP as far as I can tell, and the host was down when I investigated. Sailsbystars (talk) 04:33, 21 April 2014 (UTC)

178.162.193.199[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

178.162.193.199 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock via UTRS.--Jezebel'sPonyobons mots 16:38, 24 April 2014 (UTC)

Part of a VPN service offering a free trial. Also has weird behavior on port 80 (doesn't seem exploitable as an open proxy though). I thought VPN with free trial IPs were generally treated as open proxies, ergo remain blocked. Incidentally the IP is softblocked globally, so if we wait 4 months it will switch from a hard to a soft block on en.wiki when the current en.wiki block expires. Sailsbystars (talk) 04:37, 26 April 2014 (UTC)

TheREALCableGuy[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

178.21.175.159 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
178.21.175.169 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
81.10.82.107 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
94.252.21.225 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: There are suspicions at Wikipedia:Sockpuppet investigations/TheREALCableGuy that some of these may be open proxies. I was not able to find evidence for any of them; maybe people here can do better. -- King of ♠ 06:33, 6 June 2014 (UTC)

Just close this; I've waited a week waiting for a response and TRCG has moved on to yet another range of IP's. Nate (chatter) 04:24, 15 June 2014 (UTC)
The 178's look like a colocation serverfarm, so likely a proxy. The exact mechanism isn't available. The other IPs don't appear to be proxies. Sorry for slow response. Sailsbystars (talk) 05:47, 15 June 2014 (UTC)
178.21.160.0/20 blocked. Thanks for the check. -- King of ♠ 08:05, 15 June 2014 (UTC)

IP66.54.67.166[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

66.54.67.166 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits

I did not see any edits from the IP, it has yet to edit anything. 41.58.92.163 (talk) 03:28, 12 June 2014 (UTC)
Looks like a server for the nokia/Microsoft maps program. Given lack of edits, there's not need to block. Sailsbystars (talk) 06:08, 15 June 2014 (UTC)

148.64.124.142[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

148.64.124.142 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Likely proxy-using ref-desk troll we've been having lots of trouble from lately, based on edits. --Jayron32 03:54, 13 June 2014 (UTC)

Satellite ISP. It might be a caching proxy but it doesn't seem to be an open proxy. Not open on any of the standard proxy ports... I've seen satellite IPs come up here before, but they never seem to be a proxy. Sailsbystars (talk) 06:15, 15 June 2014 (UTC)

216.120.248.30[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

216.120.248.30 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP Part of an 0/19 range. Says it's a closed proxy he uses himself. Daniel Case (talk) 21:21, 19 June 2014 (UTC)
Well, the proxy that I found on that range back in 2011 seems to have moved on to another blocked range, but the original range should probably stay blocked. I'd explain that the software only allows rangeblocks, not rangeholes so we can't safely allow one vouched for server to edit from a rotten range (and the ownership of the range is the same as before). The user is welcome to edit wikipedia with his or her proxy disabled, though. Sailsbystars (talk) 02:21, 21 June 2014 (UTC)
We can make it a soft block and see how that progresses, if problematic, we reblock. The spammers will still be held out as the creation bit will still be on. Remember that we are meant to be looking to let people edit, and to be reasonable in our blocks. — billinghurst sDrewth 07:07, 21 June 2014 (UTC)
That's true, and I don't object to that interpretation either. There weren't any other edits at all from that range for four years before the block.... IPBE is also an option. But my reading of M:NOP is basically if your webhost isn't blocked carryon. If it is, then meh. Most people seem to forget proxies exist and I don't really think the policy has been vigorously debated in quite some time. Sailsbystars (talk) 13:59, 21 June 2014 (UTC)
While being reasonable is something we should be as administrators, let me shine a different light on to it. This could be a blocked user who has obtained proxy services from this company, and is playing the innocent game. I know, it's assuming bad faith but time and time again I come across it with CU, and socks turn up. There should be a exceptional circumstance in which he absolutely needs to use a proxy to edit. If not, what is the issue with using a normal IP. Also why we have {{webhostblock}} -- DQ (ʞlɐʇ) 16:53, 23 June 2014 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────I asked him this and he says "Because it gives me a stable machine on a stable IP." Daniel Case (talk) 02:13, 26 June 2014 (UTC)

161.112.232.111[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

161.112.232.111 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Says servers are a university's that were incorrectly blocked. Daniel Case (talk) 21:50, 24 June 2014 (UTC)

Not an open proxy I can verify their statement is accurate. The proxy is closed and legit. Unblock away! Sailsbystars (talk) 06:15, 25 June 2014 (UTC)
I've unblocked the IP.--Jezebel'sPonyobons mots 18:18, 25 June 2014 (UTC)

175.28.15.91[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

175.28.15.91 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: See these recent edits to Wikipedia:Sockpuppet investigations/L'Aquotique ([2], [3]) from 175.28.15.91 (talk+ · tag · contribs · filter log · WHOIS · RBLs · block user · block log · cross-wiki contribs · checkuser (log)) impersonating Materialscientist. Additionally, per http://ping.eu/proxy/ 175.28.15.91 (talk · contribs · WHOIS) is a proxy for port 80. JoeSperrazza (talk) 21:20, 25 June 2014 (UTC)

Confirmed, blocked, thanks. Materialscientist (talk) 21:45, 25 June 2014 (UTC)

190.102.28.173[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

190.102.28.173 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
92.46.132.40 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits

See 3RR report closed on 29 June (permalink). The first IP who joined in the edit war, 190.102.28.173 (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) is advertised on the web as being a proxy server offered by http://letushide.com, though I wasn't able to activate it. The second IP, 92.46.132.40 (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) is on various anti-spam lists but not widely advertised as a proxy. EdJohnston (talk) 02:25, 30 June 2014 (UTC)

Verified and blocked 190.102.28.173, but 92.46.132.40 is unlikely. Materialscientist (talk) 04:26, 30 June 2014 (UTC)
IP is an open proxy 92.46.132.40 (talk · contribs · WHOIS) is a wide open proxy, I just left a message as that IP on its talk page. I'd recommend blocking the IP for 3 months or so. Sailsbystars (talk) 05:45, 30 June 2014 (UTC)
No wait, it's jumping around that son of a bitch. I came out as 92.46.158.203 (talk · contribs · WHOIS). A website listed the original IP as the outlet earlier today. I don't know if we can block the whole range without collateral or if maybe we just want to block the 2 /24s.... it's the same ISP on both ranges... Sailsbystars (talk) 05:49, 30 June 2014 (UTC)
Looking at 92.46.132.0/24 [4] I only see that one edit, so not sure of the utility of a range block. 190.102.28.173/24 only has a half dozen edits outside of this one IP [5], all from 2012 or older, but not sure any of those were problematic. I'm inclined to not range block unless there is shown to be a larger problem on the range. Suggest leaving open and monitoring these ranges. I would note that .40 does have one port open but it isn't relaying. Dennis Brown |  | WER 10:40, 24 July 2014 (UTC)

178.76.152.89[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

178.76.152.89 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock via UTRS #11262.--Jezebel'sPonyobons mots 16:21, 2 July 2014 (UTC)

Not an open proxy No longer functions as a proxy. It was in a lot of proxy lists, but it seems to have been closed at some point in March/April. Safe to unblock. Sailsbystars (talk) 21:30, 6 July 2014 (UTC)
Cheers for that. Unblocked.--Jezebel'sPonyobons mots 20:49, 10 July 2014 (UTC)

182.52.118.23[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

182.52.118.23 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: blocked by Procseebot on 30 June; unblock requested at User talk:1above. JohnCD (talk) 16:10, 6 July 2014 (UTC)

Hesitant about this. On the one hand, it looks like it's a dynamic range, and that the proxy was only there for a few days (until ~July 1). The proxy is not open now. On the other hand there's currently a horribly unsecured router at that IP. If I had to decide, I'd say unblock on the benefit of the doubt. Sailsbystars (talk) 21:25, 6 July 2014 (UTC)
Wow, you weren't kidding. I would consider that an open proxy only because of the security problems that could turn it on and off in a matter of seconds. I will leave a note on the users page that they need to secure their router if they want to get unblocked. Dennis Brown |  | WER 23:09, 23 July 2014 (UTC)
The block also will expire in one month. But I think your solution is a fair one as well.... you might add mentioning the expiry time of the block. I got pretty wide eyed when I realized just how insecure that router was.... Anyway, closing as there's nothing more to do here until another unblock request comes through. Sailsbystars (talk) 01:49, 24 July 2014 (UTC)
That isn't so uncommon, sadly, and if you understand default vs. brands, well....WP:BEANS. Regardless, in the past, I think we've always required someone to fix their gear if it can be easily abuse. Dennis Brown |  | WER 10:44, 24 July 2014 (UTC)

93.115.95.6[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

93.115.95.6 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits. Edit warring, inserting identical content as a recentnly blocked IP editor. Likely an open proxy (see also [6].- MrX 15:19, 13 July 2014 (UTC)

  • Not an open proxy but a web host, I've already blocked for evading blocks. Closing. Dennis Brown |  | WER 22:21, 13 July 2014 (UTC)

Anti-semitic troll[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

190.204.146.169 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
186.88.193.144 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
190.77.253.38 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
186.93.160.116 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
190.36.56.215 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
200.219.239.11 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Previously blocked open proxies spewing anti-semitic things. Fast IP hopping and past history of open proxies indicate that these are still open proxies, but I will leave it up to the experts to determine. -- Gogo Dodo (talk) 05:32, 14 July 2014 (UTC)

Reblocked four, can't check 200.219.239.11 and 190.77.253.38 at the moment. Materialscientist (talk) 06:16, 14 July 2014 (UTC)
200.219.239.11 is now globally blocked. Can't verify 190.77.253.38 but it looks like it was active as of a week ago when this report was submitted. Sailsbystars (talk) 01:56, 24 July 2014 (UTC)

173.58.171.174[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

173.58.171.174 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP Says it's not a proxy in their unblock request. Daniel Case (talk) 19:57, 23 July 2014 (UTC)
The proxy is apparently gone, I've unblocked. Materialscientist (talk) 21:28, 23 July 2014 (UTC)
Just double checking out of boredom, found nothing, so closing. Dennis Brown |  | WER 23:05, 23 July 2014 (UTC)

154.20.35.245[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

154.20.35.245 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Very old proxy block that is likely no longer needed. Double checking prior to unblocking.--Jezebel'sPonyobons mots 22:58, 23 July 2014 (UTC)

Not an open proxy Looks remarkably clean to me. There was a tor node at one point but it seems to be long gone. Sailsbystars (talk) 01:45, 24 July 2014 (UTC)
I've unblocked the IP. --Jezebel'sPonyobons mots 22:37, 29 July 2014 (UTC)

208.87.233.180[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

208.87.233.180 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

See User talk:Bobamnertiopsis. IP was blocked by Procseebot on 22 July. If this is a proxy, any objection to my giving this editor IPBE? Here since 2007, clean block log. JohnCD (talk) 14:09, 28 July 2014 (UTC) Reason: Requested unblock.

IP is an open proxy - has been since last month. --Glaisher (talk) 16:27, 10 August 2014 (UTC)
Thanks. User says he does not expect to continue using this IP, so IPBE not required. JohnCD (talk) 08:56, 13 August 2014 (UTC)

115.112.64.30[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

115.112.64.30 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: ACC check. My testing shows a web filtering firewall which may spark off proxy issues. but other then that, no ports open. - RichT|C|E-Mail 11:56, 29 July 2014 (UTC)

It certainly was an open proxy during mid-June, but not at present from what I can see. --Glaisher (talk) 16:47, 10 August 2014 (UTC)

216.45.53.189[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

216.45.53.189 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. Comment on block log entry: QuadraNet Datacenters Hosting. עוד מישהו Od Mishehu 11:36, 5 August 2014 (UTC)

Belongs to a webhosting service. If there is abuse, ranges belonging to webhosts are usually left blocked. --Glaisher (talk) 16:38, 10 August 2014 (UTC)

103.16.70.11[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

103.16.70.11 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. See User talk:Bellus Delphina. JohnCD (talk) 10:03, 14 August 2014 (UTC)

  • Note: user says their ISP has closed the proxy, and requests unblock. JohnCD (talk) 11:29, 14 August 2014 (UTC)
    Negative, there is still an active proxy on 8080, same port as detected by the ProcseeBot. Materialscientist (talk) 11:38, 14 August 2014 (UTC)
Confirmed; there is still a wide open HTTP proxy on 8080. Kuru (talk) 12:02, 14 August 2014 (UTC)

217.115.65.15[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

217.115.65.15 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
217.115.65.17 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

User is currently edit-warring. Sockmaster was a registered user but has resorted to these proxies to avoid scrutiny. SPI has been opened accordingly at Wikipedia:Sockpuppet investigations/Fcbelmontejr. Elizium23 (talk) 00:42, 17 August 2014 (UTC) Reason: Suspicious edits

 Likely IP is an open proxy On a hosting range and at least one of them had "proxy" in the host name in the past few months. Already blocked for a year, so nothing more to do here. Sailsbystars (talk) 13:58, 29 August 2014 (UTC)

80.12.96.21[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

80.12.96.21 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: See WP:VPT#What on Earth? for the initial discovery.

How to edit with this proxy:

  1. Open http://lookup-api.apple.com.edgesuite.net/en.wikipedia.org/wiki/Wikipedia:Sandbox?action=edit
  2. The proxy only accepts enwiki URLs like en.wikipedia.org/wiki/*, so you can't save the edit normally. Replace the action parameter of the form element with http://lookup-api.apple.com.edgesuite.net/en.wikipedia.org/wiki/Wikipedia:Sandbox?action=submit
  3. Make your changes and save

Here's an example edit I've made via the proxy: [7]. Zhaofeng Li [talk... contribs...] 02:29, 28 August 2014 (UTC)

IP is an open proxy Any admins watching this page? Probably needs at least a year block... Sailsbystars (talk) 14:20, 29 August 2014 (UTC)
Blocked for a year. Materialscientist (talk) 21:38, 29 August 2014 (UTC)

209.164.3.228[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

209.164.3.228 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Belongs to web hosting company HostMySite.com. Some other abusive edits in the past years in their 209.164.0.0/18 range. Stickee (talk) 06:18, 31 August 2014 (UTC)

Anonblocked 209.164.0.0/18 for 2 years. Materialscientist (talk) 04:40, 13 September 2014 (UTC)

93.115.92.240[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

93.115.92.240 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Belongs to CactusVPN (tried myself). Range belongs to Voxility. Stickee (talk) 03:07, 13 September 2014 (UTC)

Blocked, thanks. Materialscientist (talk) 04:45, 13 September 2014 (UTC)

95.104.6.145[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

95.104.6.145 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP User says they no longer have a proxy at that address. Daniel Case (talk) 04:43, 20 September 2014 (UTC)
I've declined the unblock. Port 3128 is an open proxy, not sure about the rest of it, but I've seen enough. -- zzuuzz (talk) 20:34, 20 September 2014 (UTC)

80.67.172.1[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

80.67.172.1 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP Says they're not an open proxy. Daniel Case (talk) 14:34, 10 October 2014 (UTC)
They are no longer requesting unblock; apparently it was filed by a sock of a banned editor. Daniel Case (talk) 15:26, 10 October 2014 (UTC)

IP 5.32.67.139[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

5.32.67.139 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits
Reported at ANI for abusive edit summaries. According to cleantalk.org this particular IP has been found to be spamming at 101 sites. Suggests to me it may be an open proxy. Currently blocked two weeks for the abuse, but a proxy check might justify a longer block. EdJohnston (talk) 17:27, 10 October 2014 (UTC)

I have confirmed that it si an open proxy, as shown here. I have blocked the IP address for a year. The editor who uses the pseudonym "JamesBWatson" (talk) 20:54, 10 October 2014 (UTC)

156.62.9.20[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

156.62.9.20 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP Says they're not an open proxy. Daniel Case (talk) 02:28, 29 October 2014 (UTC)
I've unblocked, as the proxy seems gone. This is Auckland University of Technology IP, thus rapid reaction is not unusual. I hope ProxyBot will reblock if they resume (the entrance of the tunnel, 156.62.100.35, still has open ports) Materialscientist (talk) 02:54, 29 October 2014 (UTC)

202.28.25.118[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

202.28.25.118 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: This IP was blocked back in 2006. The whois says it's a inter-University ISP, so I think it might be just a shared IP rather than an open proxy. — Parent5446 (msg email) 05:47, 4 November 2014 (UTC)

Unblocked. Materialscientist (talk) 23:42, 5 November 2014 (UTC)
Reblocked. Checked ports now, 1723 ppt is open (among a few others), which is a bad sign of a compromised computer. Materialscientist (talk) 21:59, 7 November 2014 (UTC)

173.196.129.100[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

173.196.129.100 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: This IP address has repeatedly used for vandalism, and is listed in the Composite Blocking List as being infected with Conficker according to http://cbl.abuseat.org/lookup.cgi?ip=173.196.129.100&.pubmit=Lookup . Could someone please confirm that this is some sort of zombie proxy? I have blocked it in order to stop the vandalism. Jesse Viviano (talk) 16:39, 5 November 2014 (UTC)

It's not in the CBL anymore, no surprise since this is a Road Runner Commercial IP and RR Security doesn't tolerate nonsense. Based on the edits, I'd say this more than likely is a shared IP with immature users (it's been {{schoolblock}}ed before), and one of their computers got infected with a virus which spewed out a bunch of spam. PCHS-NJROTC (Messages) 00:27, 4 February 2015 (UTC)

192.73.240.188[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

192.73.240.188 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: According to the WHOIS for this report, this IP address belongs to Host Virtual, which appears to be a data center. It has been used for comment spam according to Project Honey Pot according to http://www.projecthoneypot.org/ip_192.73.240.188 . Its IP's reverse DNS resolves to "sea11.web.isheriff.com". I therefore believe this to be some sort of proxy. Jesse Viviano (talk) 21:40, 5 November 2014 (UTC)

See below. Materialscientist (talk) 23:38, 5 November 2014 (UTC)

192.73.240.188[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

192.73.240.188 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits Reported at AIV - 198.96.22.242 (talk · contribs · deleted contribs · edit filter log · WHOIS · RDNS · RBLs · http · block user · block log) – On Call of Duty: Advanced Warfare: vandalism after final warning. May need a range block on 241-.254 as appears to be hopping around this subnet. Amortias (T)(C) 21:29, 5 November 2014 (UTC). http://whois.domaintools.com/192.73.240.188 leads one to http://www.hostvirtual.com/ Ronhjones  (Talk) 21:44, 5 November 2014 (UTC)

Issued a general webhost block of 192.73.240.0/20. This particular IP shows a proxy-like behavior in CU logs. Materialscientist (talk) 23:38, 5 November 2014 (UTC)

217.115.65.15[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

217.115.65.15 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock via UTRS #12278.--Jezebel's Ponyobons mots 00:05, 27 November 2014 (UTC)

This IP is mentioned elsewhere on this page. proxy1-ext.my-it-solutions.net and 217.115.65.17 is proxy2-ext.my-it-solutions.net. At a guess this is a private server, not particularly open (no more than a school for example). I'd normally give this IP a green light, except there's a technically valid user block behind it. I doubt a full hardblock is necessary though, TBH. -- zzuuzz (talk) 08:23, 27 November 2014 (UTC)
Not an open proxy. The IP remains blocked. -- zzuuzz (talk) 21:00, 26 January 2015 (UTC)

182.253.73.28[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

182.253.73.28 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock by Ayomaju. Block has a comment: 8080. עוד מישהו Od Mishehu 06:30, 8 December 2014 (UTC)

Comment: http://dronebl.org/lookup lists an open proxy, but the check seems rather stale (December 2013). No other blacklists reported by robtex. Host up with no open ports at this moment. I see no reason not to unblock, but am too unfamiliar with the process to do so myself for the moment. Martijn Hoekstra (talk) 10:50, 8 December 2014 (UTC)
Unblocked - don't see a proxy anymore. Materialscientist (talk) 11:07, 8 December 2014 (UTC)

85.230.127.244[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

85.230.127.244 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits. in ja.wikipedia.org .

  • Comment: Reverse DNS yields
    • openports.info
    • furnituredepots.com
    • www.proxysmart.info
    • www.proxyget.info
    • www.proxyactive.info
    • proxyget.info
    • proxyactive.info
    • proxysmart.info
which definitely suggests a proxy. Then again, I'm only seeing open ports on 80 and 3306, which suggests nothing to worry about - but that may be temporary, with forwarded ports down. Martijn Hoekstra (talk) 10:40, 8 December 2014 (UTC)
Blocked. This is a type of proxy where you connect through a web page, not through a port. Materialscientist (talk) 10:46, 8 December 2014 (UTC)

216.246.109.198[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

216.246.109.198 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .

Confirmed, blocked, thanks. Materialscientist (talk) 11:10, 9 December 2014 (UTC)

94.124.85.18[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

94.124.85.18 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .

Confirmed, blocked, thanks. Materialscientist (talk) 10:53, 12 December 2014 (UTC)

2a01:4a0:11::92c5:98f0[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

2a01:4a0:11::92c5:98f0 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .

63.223.73.164[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

63.223.73.164 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .

Confirmed, blocked, thanks. Materialscientist (talk) 11:40, 13 December 2014 (UTC)

103.246.18.22[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

103.246.18.22 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .

Blocked, thanks. Materialscientist (talk) 10:50, 14 December 2014 (UTC)

59.151.103.45[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

59.151.103.45 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .

Blocked, thanks. Materialscientist (talk) 11:25, 14 December 2014 (UTC)

62.109.25.136[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

62.109.25.136 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org . --HotKorokke (talk) 12:38, 22 December 2014 (UTC)

Confirmed, blocked, thanks. Materialscientist (talk) 12:47, 22 December 2014 (UTC)

162.220.8.43[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

162.220.8.43 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock, as it's my own VPS server (its rDNS points to zhaofeng.li) with no open proxies running on it (I do run a closed proxy for my friends to circumvent censorship). Although I have IPBE and can edit via the IP, but unblocking will make it easier in case someone else want to edit with my proxy. Please note that I control only this specific IP address, not the other ones in the subnet. Thank you for your time. Zhaofeng Li [talk... contribs...] 10:41, 28 December 2014 (UTC)

We can't unblock one IP on a range, we can only unblock the whole range locally on this wiki. Vituzzu globally blocked 162.220.8.0/21 for 5 years. If you wish to lift it locally, ask him about the reasons for such a long rangeblock. Materialscientist (talk) 10:48, 28 December 2014 (UTC)
Okay, will do. Happy holidays! Zhaofeng Li [talk... contribs...] 11:22, 28 December 2014 (UTC)

176.103.143.217[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

176.103.143.217 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org . --HotKorokke (talk) 12:24, 30 December 2014 (UTC)

Blocked, thanks. This is zpanelcp webhost, which is a kind of "open proxy". Materialscientist (talk) 12:36, 30 December 2014 (UTC)

162.218.211.128[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

162.218.211.128 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org . --HotKorokke (talk) 12:26, 30 December 2014 (UTC)

Blocked, thanks. This is vivalaproxy.com, and also a webhost. Materialscientist (talk) 12:39, 30 December 2014 (UTC)

66.102.6.164[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

66.102.6.164 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits Sudden spate of vandalism - short block for that. On checking http://whatismyipaddress.com/ip/66.102.6.164 - says "Suspected proxy server" Ronhjones  (Talk) 01:41, 1 January 2015 (UTC)

Hard-blocked 66.102.0.0/20 as Google proxy. This page [8], for example, explains how to user Google services as open proxies. This IP range in particular has been abused in the last few months. Materialscientist (talk) 02:12, 1 January 2015 (UTC)

46.20.37.133[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

46.20.37.133 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

webproxy.yt

Reason: Suspicious edits. Likely using a German proxy for sockpuppetry by a recently blocked user. See contributions at Faithful Word Baptist Church. Than k you.- MrX 22:47, 2 January 2015 (UTC)

Blocked, thanks. Materialscientist (talk) 22:52, 2 January 2015 (UTC)

204.93.60.60[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

204.93.60.60 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Anonymous proxy per https://www.robtex.com/en/advisory/ip/204/93/60/60/, used here JoeSperrazza (talk) 20:40, 3 January 2015 (UTC)

Open proxy blocked -- zzuuzz (talk) 18:01, 24 January 2015 (UTC)

204.93.60.53[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

204.93.60.53 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Anonymous proxy per https://www.robtex.com/en/advisory/ip/204/93/60/53/, used here JoeSperrazza (talk) 20:45, 3 January 2015 (UTC)

Open proxy blocked -- zzuuzz (talk) 18:01, 24 January 2015 (UTC)

15.203.169.105[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

15.203.169.105 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits

Bad faith editing on Reformed Presbyterian Church of Scotland; I removed unhelpful content from this page twice (both added by Orange (UK) addresses from Scotland), and the last addition was by this Hewlett Packard address in Switzerland that http://whatismyipaddress.com/ip/15.203.169.105 says is a suspected proxy server. If it's not that, we've got a multinational group of trollers. Nyttend (talk) 15:15, 24 January 2015 (UTC)

Though this is a proxy it does not appear to be open. A work IP address, from anywhere in Europe, is likely. -- zzuuzz (talk) 18:06, 24 January 2015 (UTC)
zzuuzz, are you the proxy checker (i.e. I should withdraw this request), or are you just guessing, i.e. it should remain open for now? Nyttend (talk) 20:11, 24 January 2015 (UTC)
I should leave it open for now or a second opinion, as new revelations can turn up and no one can ever really confirm a proxy IP is closed. I am giving you an educated initial pointer in the meantime. Consider the IP unconfirmed and unblocked unless things change. -- zzuuzz (talk) 20:48, 24 January 2015 (UTC)
Okay, thank you. I don't remember previously making any reports here, so I wasn't sure how things worked. Nyttend (talk) 22:31, 24 January 2015 (UTC)
I can find no evidence that it's an open proxy. No ports are open. The editor who uses the pseudonym "JamesBWatson" (talk) 15:40, 5 February 2015 (UTC)

Blocked user allegedly using 36.81.86.109--CU needed[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

36.81.86.109 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

User talk:Riskykurniawan claims to be using this IP address and that it is caught in an open proxy block, although it is not an open proxy. Could a checkuser a) confirm that he's using it and b) see if it's an open proxy? Thanks, Origamite 04:08, 26 January 2015 (UTC) Reason: Requested unblock.

Not an open proxy (it was one recently), unblocked. -- zzuuzz (talk) 19:58, 26 January 2015 (UTC)

162.119.231.132[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

162.119.231.132 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. I understand the need for this process, but I think it is unnecessary at this time for this IP. Please see the user's talk page for details. Thank you. Lightbreather (talk) 18:37, 26 January 2015 (UTC)

Not an open proxy. Despite the open ports, it doesn't seem to be open. Nor do any others in the range. -- zzuuzz (talk) 19:56, 26 January 2015 (UTC)
@Zzuuzz: Can you double check your findings? I was just able to connect and download content through port 443 (HTTPS). Mike VTalk 20:35, 26 January 2015 (UTC)
Yes, but it does not change your IP address to 162.119.231.132 ? -- zzuuzz (talk) 20:42, 26 January 2015 (UTC)

61.37.31.80[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

61.37.31.80 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .--HotKorokke (talk) 11:39, 30 January 2015 (UTC)

There are several open ports, but I am unable to connect to any of them, and I can't find the IP address listed anywhere as an open proxy. The editor who uses the pseudonym "JamesBWatson" (talk) 15:30, 5 February 2015 (UTC)
Also, the IP address geolocates to South Korea, and all the anon edits from the IP address are to either ja.wikipedia or ko.wikipedia. Open proxies commonly get used by people in different parts of the world from where the proxies are situated. That encourages me to think it less likely that it's an open proxy. The editor who uses the pseudonym "JamesBWatson" (talk) 15:34, 5 February 2015 (UTC)

162.119.240.70[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

162.119.240.70 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Requesting unblock here. Origamite 13:50, 30 January 2015 (UTC) Reason: Requested unblock.

Not a proxy, leaving a note to the blocking admin. Materialscientist (talk) 23:36, 30 January 2015 (UTC)
Unblocked. Materialscientist (talk) 21:33, 31 January 2015 (UTC)

182.18.177.170[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

182.18.177.170 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: This IP belongs to Data Center India, a cloud hosting company. PCHS-NJROTC (Messages) 17:33, 31 January 2015 (UTC)

Various IPs[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

5.164.192.80 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
5.164.195.56 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
5.166.206.214 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
27.150.228.6 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
27.150.239.206 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
46.151.55.4 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
46.235.44.156 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
58.23.18.178 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
58.23.232.2 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
58.23.233.86 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
120.33.220.135 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
223.240.128.58 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
223.240.136.18 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

See the admin-only spam-blacklist hitlist - a couple of days already we have a continuous list of hits on the blacklist due to attempts to add blacklisted domains. I will make a permanent record on meta shortly.

This morning I started to hand-out 1-week blocks (to give people time to find a more permanent solution), please reblock them appropriately (globally??!!??). Note, that I may extend this list when they move again to other IPs during the day. --Dirk Beetstra T C 04:43, 9 February 2015 (UTC)

Another spammer[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

5.166.206.214 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

See the admin-only spam-blacklist hitlist, seems unrelated to above system (this is a viagra spammer). --Dirk Beetstra T C 04:52, 9 February 2015 (UTC)

No comment on the proxy status but this IP was actively spamming on 2 March. I've blocked for three months. EdJohnston (talk) 15:17, 2 March 2015 (UTC)

103.7.250.251[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

103.7.250.251 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Unblock request at User talk:Nahiyan8 - user states that their IP is no longer open. ​—DoRD (talk)​ 17:41, 13 February 2015 (UTC)

Completed by User:Kuru. Thank you. Proof: User talk:Nahiyan8– Nahiyan8 (talk | contribs) 17:22, 14 February 2015 (UTC)

Geoproxy[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot. This is a long list of open proxies that can be used on the Geoproxy plugin on Chrome. (I have not checked if they were blocked or not. It takes 3 mins just to open the sandbox.) Albania

46.19.231.190 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
77.242.29.161 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080

Argentina

190.230.39.142 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
190.188.3.194 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
200.43.56.249 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
181.88.198.141 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
200.114.243.42 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
200.123.162.45 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
190.3.14.44 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128

Hong Kong

113.52.134.28 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
103.248.254.172 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
101.1.16.123 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
218.188.16.123 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
210.6.237.191 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
103.248.254.174 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
103.248.254.173 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
210.209.116.90 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
103.246.244.161 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:44338
103.248.254.171 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128

Great Britain

78.157.209.37 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
128.199.97.184 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
128.199.195.26 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
128.199.115.194 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
78.110.175.75 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
31.25.187.202 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
128.199.226.223 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
82.146.147.112 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
128.199.238.109 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
78.157.209.36 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3129

The USA

104.237.143.165 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
199.180.252.73 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
69.164.213.244 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
104.237.157.98 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
165.24.10.16 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
131.109.42.105 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
54.194.10.207 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
54.186.7.200 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128

South Korea

101.79.241.40 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
183.86.209.117 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
14.63.165.60 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128

Australia

115.70.67.58 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080

Brazil

186.215.108.200 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
177.220.153.181 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
177.128.28.12 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
177.22.175.183 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
200.254.121.118 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
179.199.118.106 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
177.184.132.123 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
177.223.7.214 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
186.215.65.47 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
200.178.118.82 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80

China

119.90.127.5 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
119.90.127.3 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
119.90.127.2 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
211.162.0.170 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
175.25.243.22 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
111.161.126.101 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
125.39.66.66 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
111.161.126.98 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
125.39.66.68 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
103.27.24.113 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8090

Singapore

119.81.161.58 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128

Sigh.... Clubjustin3 (talk) 03:40, 18 February 2015 (UTC)

Most of them were already blocked by the proxy bot, and I've blocked the rest. Materialscientist (talk) 03:54, 18 February 2015 (UTC)
Thx, 'cause i was in a (sort of) hurry when I posted this. Clubjustin3 (talk) 09:29, 18 February 2015 (UTC)

More geoproxy[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot. Same reason as above

213.187.247.191 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
95.211.99.111 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
188.166.17.183 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
217.23.8.205 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
105.237.124.149 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
154.126.200.13 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
41.160.147.130 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
190.189.90.91 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
190.230.39.142 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
190.3.14.44 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:3128
190.188.3.194 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
200.85.121.5 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8089
41.46.192.195 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
41.46.217.34 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
41.46.208.112 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
41.46.213.33 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:80
62.241.149.173 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
41.46.192.203 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP:8080
  • Just clicking on the "current blocks" links above shows whether they are blocked or not. All but one were blocked, and I have blocked that one. The editor who uses the pseudonym "JamesBWatson" (talk) 15:09, 24 February 2015 (UTC)

197.85.132.8[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

197.85.132.8 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock for Mr Rapano (talk · contribs). PhilKnight (talk) 18:15, 20 February 2015 (UTC)

  • I am unable to connect to the proxy. Online searches indicate that the IP address was once used for dubious purposes, but I can find no evidence anywhere of recent abuse. For example, Project Honey Pot has not detected suspicious activity for over 11 months. I am therefore inclined to unblock, But I shall wait a while for anyone else to comment. The editor who uses the pseudonym "JamesBWatson" (talk) 16:07, 23 February 2015 (UTC)
  • I have checked again, and can still find no evidence that this IP address is currently hosting an open proxy, and a CheckUser has failed to find any problems, so I have unblocked the IP address. For the moment, however, I will leave this request open, in case anyone else has any evidence that I haven't seen, meaning that the block should be restored. The editor who uses the pseudonym "JamesBWatson" (talk) 14:57, 24 February 2015 (UTC)
  • I have checked again, and can still find no evidence that this IP address is currently hosting an open proxy, so I am closing this case. The editor who uses the pseudonym "JamesBWatson" (talk) 14:19, 2 March 2015 (UTC)

59.120.0.127[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

59.120.0.127 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits

  • This IP adress has been blocked before, but seem to be editing pages again. It deletes original sources and replace them with other links, probably for spam-purposes.--Securitymarket (talk) 21:57, 25 February 2015 (UTC)
Blocked by EdJohnston for 2 years. The editor who uses the pseudonym "JamesBWatson" (talk) 14:21, 2 March 2015 (UTC)

67.220.22.228[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

67.220.22.228 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock.

  • Unblock requested by User talk:602p. IP blocked for two months by ProcseeBot on 15 February. This IP was advertised on some proxy lists on the web as recently as 15 February, with an open port on 3128, but when I tried to activate it just now it didn't work. User says he has fixed his firewall problem. EdJohnston (talk) 21:22, 26 February 2015 (UTC)
The port at 3128 is no longer open, but 1723 is now open. However, repeated attempts to connect to that port have failed, and I have not found the IP address on any proxy lists since 21 February, and all the listings I have seen have been for the now-closed port 3128, so I shall unblock the IP address. The editor who uses the pseudonym "JamesBWatson" (talk) 14:31, 2 March 2015 (UTC)

2607:FF48:1:301:0:0:5C1B:BFCE[edit]

Symbol comment vote.svg – This proxy check request is closed and will shortly be archived by a bot.

2607:FF48:1:301:0:0:5C1B:BFCE - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Suspicious edits in ja.wikipedia.org .--HotKorokke (talk) 23:24, 28 February 2015 (UTC)

Very likely (see their edit). Blocked. Materialscientist (talk) 12:36, 5 March 2015 (UTC)

69.63.114.3[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

69.63.114.3 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock, due to the fact that the CBCSD has now enforced auth on it's proxy.


Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

69.63.114.3 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. PhilKnight (talk) 15:55, 5 March 2015 (UTC)

  • This IP address certainly did host an open proxy in the past. At present there are no open ports, but since many open proxies sporadically come on and off line, that is no proof. If there is still no evidence of an open proxy after a day or so, I shall be willing to change the block to anon-only, which will allow logged-in accounts to edit, but in my opinion there is no case for completely unblocking, because apart from a few edits to this page in connection with the block, the edits from this IP address have been 100% vandalism (as is often the way with school IP addresses). If anyone knows any reason why I should not lift the blcok on logged-in editing, please let me know. The editor who uses the pseudonym "JamesBWatson" (talk) 14:48, 6 March 2015 (UTC)
  • Since I wrote the above message, I have found that the IP address has been the source of spam up to less than three weeks ago. That makes me somewhat less willing to lift the block, and I am inclined to wait for more than just a few days before considering doing so. The editor who uses the pseudonym "JamesBWatson" (talk) 15:05, 6 March 2015 (UTC)

62.212.85.119[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

62.212.85.119 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. PhilKnight (talk) 19:28, 8 March 2015 (UTC)

The IP address is assigned to "LeaseWeb B.V." and its hostname is "hosted-by.leaseweb.com". That looks to me pretty much like an indication that it is a web host, despite the denial by the person making the unblock request. The editor who uses the pseudonym "JamesBWatson" (talk) 17:28, 9 March 2015 (UTC)

CyberGhost proxies[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

79.141.160.64 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
  • 109.236.87.xx
  • 109.236.90.xx
  • 161.202.76.xx
  • 162.244.81.xx
  • 168.1.69.xx
  • 169.57.1.xx
  • 176.10.98.xx
  • 176.116.153.xx
  • 185.8.107.xx
  • 194.187.250.xx
  • 194.187.251.xx
  • 199.195.199.xx
  • 199.231.208.xx
  • 209.58.130.xx
  • 212.232.25.xx
  • 217.23.12.xx
  • 217.23.5.xx
  • 217.23.7.xx
  • 69.46.6.xx
  • 77.243.181.xx
  • 77.243.189.xx
  • 79.141.160.xx
  • 79.141.162.xx
  • 79.141.164.xx
  • 79.141.165.xx
  • 79.141.166.xx
  • 79.141.167.xx
  • 79.141.170.xx
  • 79.141.172.xx
  • 79.141.173.xx
  • 82.103.129.xx
  • 82.103.130.xx
  • 82.103.140.xx
  • 82.103.142.xx
  • 82.221.102.xx
  • 84.19.169.xx
  • 85.9.20.xx
  • 91.135.65.xx
  • 93.190.138.xx
  • 93.190.139.xx
  • 95.141.20.xx
  • 95.141.27.xx
  • 95.141.29.xx
  • 95.141.31.xx

Reason: These are IPs that I found through the CyberGhost webhost application. Rangeblocks might be applicable for some cases. Sorry for the long list; I couldn't think of a better way to format it. Conifer (talk) 02:31, 9 March 2015 (UTC)

94.249.128.0[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

94.249.128.0 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock for Hagrid (talk · contribs) PhilKnight (talk) 20:44, 14 March 2015 (UTC).

Why not asking the blocking admin? Materialscientist (talk) 22:15, 14 March 2015 (UTC)

92.36.165.127[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

92.36.165.127 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Origamite 02:28, 15 March 2015 (UTC) Reason: Requested unblock.

Decline. This is a checkuser block, and the unblock request comes from the person who was targeted by the block. Materialscientist (talk) 02:42, 15 March 2015 (UTC)
@Materialscientist:If this is a checkuser block, then why is the reason {{blocked proxy}}, not {{checkuserblock}}?עוד מישהו Od Mishehu 13:17, 15 March 2015 (UTC)
Because it is both a proxy block and a checkuserblock :-D. Materialscientist (talk) 23:21, 15 March 2015 (UTC)

213.55.89.14[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

213.55.89.14 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: See https://www.robtex.com/en/advisory/ip/213/55/89/14/ - blacklists. Used for vandalization (reported at WP:AIV. JoeSperrazza (talk) 01:20, 28 March 2015 (UTC)

you== 73.39.248.199 ==

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

73.39.248.199 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock for AfroThundr3007730 (talk · contribs). PhilKnight (talk) 16:50, 12 April 2015 (UTC)

I can't determine if it's still completely open, but there's some very fishy things going on with that IP. Reaper Eternal (talk) 16:10, 13 April 2015 (UTC)
http://73.39.248.199 displays a holding page (if you click through all the warnings about bad certificates). I'd recommend a {{webhostblock}}. This IP has been originating Wordpress Viagra spam as recently as March, so if the machine is owned by AfroThundr3007730, he does not keep it well secured. EdJohnston (talk) 20:02, 13 April 2015 (UTC)
Port 8080 is set up as a http proxy (though I couldn't connect with a few attempts), and there are a few other open ports that are commonly used for proxy setting, thus I won't unblock. Materialscientist (talk) 22:26, 13 April 2015 (UTC)
Hi, I may be able to clear up a few questions regarding this IP. It belongs to my router, which has port forwarding set up for multiple services I run for personal use. See here for details regarding what specific services are running. While there are quite a few, I do not host any services that would serve as an open proxy on this IP. Hopefully this clears up some of the confusion. I also have a few questions, which are listed in the relevant section of my talk page. AfroThundr3007730 (talk) 05:12, 15 April 2015 (UTC)
And I'm back again. It seems nobody is willing to outright remove the block. Be that as it may, I still have a few questions on this issue:
  1. Is there a way to modify this block to allow logged in users to edit, as in only block the IP edits?
  2. Barring that, can an exception be made for a specific user account, namely my own?
  3. Can the settings be changed so I can edit more than just my talk page, e.g the rest of my user pages?
It has been extremely annoying trying to get anything done on here, as to modify anything other than my talk page (including to post this comment), I have to tether my laptop through my phone. It's an imperfect solution, of course, as I do not have unlimited data. As I was saying on my talk page, I am also only able to edit User_talk:AfroThundr3007730 and nothing else in my userspace. What needs to happen in order to resolve this? AfroThundr3007730 (talk) 03:11, 22 April 2015 (UTC)
Unblocked. There is no extraneous traffic in recent CU logs. There might have been some email spamming activity routed through this IP, but this, even if correct, is hardly a problem for this wiki. Materialscientist (talk) 03:16, 22 April 2015 (UTC)
Thank You! AfroThundr3007730 (talk) 03:39, 22 April 2015 (UTC)

186.244.253.7[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

186.244.253.7 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. PhilKnight (talk) 22:09, 25 April 2015 (UTC)

Nothing on 8080, or any other open ports I could see. Kuru (talk) 02:10, 28 April 2015 (UTC)

152.26.69.36[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

152.26.69.36 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Requested unblock. PhilKnight (talk) 17:27, 27 April 2015 (UTC)

Lots of oddness there. 8080 is still open, and there's some kind of proxy there. I could not connect, however. The IP/port combo shows up on hundreds of proxy lists, some very recent. Kuru (talk) 02:03, 28 April 2015 (UTC)
Note the reverse DNS. I've been trying it, but I believe it may have closed and have unblocked it. It remains under a schoolblock, and no doubt ProcseeBot will catch it if it opens again. -- zzuuzz (talk) 19:49, 28 April 2015 (UTC)

Multiple IPs in block/unblock requests[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

87.58.124.203 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
188.228.120.184 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP
212.242.162.167 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Several unblock requests popped up that seemed to be from someone editing through a proxy tunnel. They included the message "If you're seeing this message, then this IP should be blocked as an open proxy." Many of the IPs were already covered in range blocks, but the three above were not. I'll scan myself when I get a chance, but I wanted to annotate here for people who are actually good at this. Kuru (talk) 13:31, 2 May 2015 (UTC)

87.58.124.203 and 188.228.120.184 don't seem to have open ports; 212.242.162.167 has 2034/tcp open scoremgr and 2121/tcp open ccproxy-ftp, but I don't know how to connect to those. http://212.242.162.167:2121 says "password required". Materialscientist (talk) 23:09, 2 May 2015 (UTC)
Add me in too. This is Zeke Essiestudy, just to let you know. I'm editing through this link. 107.150.32.226 (talk) 00:52, 4 May 2015 (UTC)
Confirmed that one through the given interface. What did you use to connect to the others? Kuru (talk) 01:08, 4 May 2015 (UTC)
Sorry to say the initial 3 above aren't me, I just decided to use proxy.org, use the "Random proxy" feature, and see if I was able to edit Wikipedia through the proxy instead of seeing seeing a global block + local block notice. I'll tell you if I catch any others. Zeke Essiestudy (talk) 01:12, 4 May 2015 (UTC)
If the IPs offered at proxy.org are currently working proxies, then maybe User:ProcseeBot could add them to its list to be checked. EdJohnston (talk) 02:56, 4 May 2015 (UTC)

45.55.180.126[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

45.55.180.126 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: Recently used for large-scale harassment of other editors. Hostname cloud.unblockwebsites.ninja — Brianhe (talk) 14:52, 11 May 2015 (UTC)

  • It was blocked today on another wiki as a proxy. Ports 80 and 8000 are open amongst other standard ports. zadmin is master login but I don't know how to connect.
     — Berean Hunter (talk) 17:56, 11 May 2015 (UTC)

43.249.38.98[edit]

Symbol merge vote.svg – A user has requested a proxy check. A proxy checker will shortly look into the case.

43.249.38.98 - talk - edits - block - log - current blocks - Robtex/WHOIS - Google - HTTP

Reason: This Singapore IP reverted at this talk page to restore edit made by an earlier IP from Kolkata, India [9]. Seems like a proxy. Mar4d (talk) 10:25, 12 May 2015 (UTC)

See also[edit]

Subpages[edit]

Related pages[edit]

Chapters[edit]