Used by stalker reverting edits
Guffydrawers (
talk) 20:13, 7 January 2011 (UTC)
{{
notaproxy}}. This is routine vandalism by a mobile phone user. I have rangeblocked 221.130.23.0/24 one month.
EdJohnston (
talk) 03:21, 8 January 2011 (UTC)
{{
notaproxy}}. Vandalism. An editor who is pursuing Guffydrawers is working from this range (e.g.
[1]), and this suggests a connection to the report above. I'm blocking 221.194.132.0/24 for one month anon-only.
EdJohnston (
talk) 03:33, 8 January 2011 (UTC)
Host is down for me, so unable to confirm or deny. Looks more like someone bored at work though. Spam listing likely due to a virus infection at some point and unrelated to proxy/not proxy.
Sailsbystars (
talk) 17:58, 9 December 2010 (UTC)
Host is up right now for me, can't connect via port 80 though. --
DQ (t) Merry Chrismasand a Happy New Year! 17:09, 21 December 2010 (UTC)
{{
notaproxy}} -- Somebody bored at work seems like the best diagnosis. Google results suggest spam but not proxying. Blocking the IP for one year anon-only for vandalism.
EdJohnston (
talk) 18:13, 8 January 2011 (UTC)
Blacklisted in at least eleven lists
[2] --
Supreme Deliciousness (
talk) 00:06, 18 January 2011 (UTC)
Reason: Suspicious edits
Inconclusive in a quick check, not on any proxy lists, leaning towards not a proxy. It's on a /14 range from Columbia and I can't find any more specific DNS or whois information than that. No proxies on standard ports, but I'm not able to run a port scan at this time. Port 80 has a webserver running, but there's no website there and it doesn't respond to proxying commands.
Sailsbystars (
talk) 18:37, 18 January 2011 (UTC)
And now the host is down, I'm going to go with not a proxy.
Sailsbystars (
talk) 23:56, 18 January 2011 (UTC)
Finally was able to do a port scan. Looks to be a normal desktop linux box with only open ports being 22 and 80. The webserver does not proxy and in fact looks rather unused.
Sailsbystars (
talk) 16:36, 19 January 2011 (UTC)
Used by stalker reverting edits
Guffydrawers (
talk) 20:13, 7 January 2011 (UTC)
{{
notaproxy}}. This is routine vandalism by a mobile phone user. I have rangeblocked 221.130.23.0/24 one month.
EdJohnston (
talk) 03:21, 8 January 2011 (UTC)
{{
notaproxy}}. Vandalism. An editor who is pursuing Guffydrawers is working from this range (e.g.
[1]), and this suggests a connection to the report above. I'm blocking 221.194.132.0/24 for one month anon-only.
EdJohnston (
talk) 03:33, 8 January 2011 (UTC)
Host is down for me, so unable to confirm or deny. Looks more like someone bored at work though. Spam listing likely due to a virus infection at some point and unrelated to proxy/not proxy.
Sailsbystars (
talk) 17:58, 9 December 2010 (UTC)
Host is up right now for me, can't connect via port 80 though. --
DQ (t) Merry Chrismasand a Happy New Year! 17:09, 21 December 2010 (UTC)
{{
notaproxy}} -- Somebody bored at work seems like the best diagnosis. Google results suggest spam but not proxying. Blocking the IP for one year anon-only for vandalism.
EdJohnston (
talk) 18:13, 8 January 2011 (UTC)
Blacklisted in at least eleven lists
[2] --
Supreme Deliciousness (
talk) 00:06, 18 January 2011 (UTC)
Reason: Suspicious edits
Inconclusive in a quick check, not on any proxy lists, leaning towards not a proxy. It's on a /14 range from Columbia and I can't find any more specific DNS or whois information than that. No proxies on standard ports, but I'm not able to run a port scan at this time. Port 80 has a webserver running, but there's no website there and it doesn't respond to proxying commands.
Sailsbystars (
talk) 18:37, 18 January 2011 (UTC)
And now the host is down, I'm going to go with not a proxy.
Sailsbystars (
talk) 23:56, 18 January 2011 (UTC)
Finally was able to do a port scan. Looks to be a normal desktop linux box with only open ports being 22 and 80. The webserver does not proxy and in fact looks rather unused.
Sailsbystars (
talk) 16:36, 19 January 2011 (UTC)