RE: Bad exit node: freeMe69

[downie - <downgeoff2@xxxxxxxxxxx>]

> On 8/20/09, Tom Hek <tor@xxxxxxxxx> wrote:
> > On Aug 20, 2009, at 23:02 PM, KT wrote:
> >
> >> Exit node freeMe69 [1] is injecting the following snippet to
> >> response body:
> >>
> >> <script type="text/_javascript_"
> >> src=""></script>
> >>
> >> [1] http://tinyurl.com/mz9d7e
> >
> > It's actually injected by it's ISP, Comcast.
>
> Excuse my ignorance...I can imagine it might be injected upstream but
> you know this how?
>
> > The IP which s.tobban.com
> > resolves to is assigned to Comcast. I don't think the exit node admin
> > can't do anything about it.
>
> s.tobban.com resolves to the *IP address of the exit node* which is on Comcast.
>
> regards
> KT
More strangeness: resolver error page.

<h1>Charles Error Report</h1>
<h2>Name lookup failed for remote host</h2>
<p>Charles failed to resolve the name of the remote host into an IP address. Check that the URL is correct.</p>

<p>The actual exception reported was:</p>
<pre>
java.net.UnknownHostException: washingtonpost.com
</pre>

<p>
<i>Charles Proxy, <a href="http://www.xk72.com/charles/">http://www.xk72.com/charles/</a></i>

---

With Windows Live, you can organize, edit, and share your photos. Click here.