<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Symantec crawling blogs?</title>
	<atom:link href="http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/</link>
	<description>writes on spam and admin issues</description>
	<pubDate>Wed, 07 Jan 2009 00:46:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IJ</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-175951</link>
		<dc:creator>IJ</dc:creator>
		<pubDate>Thu, 03 May 2007 18:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-175951</guid>
		<description>While this is a bit late, I run a webserver with a few sites on it, both mine and not.

I got hit by these things last night.  I figured I'd take charge of these guys.

I have a Cisco 2611 directly ahead of my server.  My solution to this was simple:

Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#ip route 65.88.178.10 255.255.255.255 null0
Router(config)#end
Router#copy run start
Destination filename [startup-config]?
Building configuration...
[OK]

Not only can they not talk to my webserver, they can't talk to ANYTHING behind that router!</description>
		<content:encoded><![CDATA[<p>While this is a bit late, I run a webserver with a few sites on it, both mine and not.</p>
<p>I got hit by these things last night.  I figured I&#8217;d take charge of these guys.</p>
<p>I have a Cisco 2611 directly ahead of my server.  My solution to this was simple:</p>
<p>Router#conf t<br />
Enter configuration commands, one per line.  End with CNTL/Z.<br />
Router(config)#ip route 65.88.178.10 255.255.255.255 null0<br />
Router(config)#end<br />
Router#copy run start<br />
Destination filename [startup-config]?<br />
Building configuration&#8230;<br />
[OK]</p>
<p>Not only can they not talk to my webserver, they can&#8217;t talk to ANYTHING behind that router!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-3364</link>
		<dc:creator>Dirk</dc:creator>
		<pubDate>Mon, 13 Feb 2006 21:02:21 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-3364</guid>
		<description>Yep, I've noticed the same thing (same IP address) as Elixon earlier today. It's already blocked because of that dubious user agent string, but that didn't stop it from trying. It's also trying to access URLs that are listed in our robots.txt

Bad bot, bad Symantec!</description>
		<content:encoded><![CDATA[<p>Yep, I&#8217;ve noticed the same thing (same IP address) as Elixon earlier today. It&#8217;s already blocked because of that dubious user agent string, but that didn&#8217;t stop it from trying. It&#8217;s also trying to access URLs that are listed in our robots.txt</p>
<p>Bad bot, bad Symantec!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elixon</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-3359</link>
		<dc:creator>Elixon</dc:creator>
		<pubDate>Mon, 13 Feb 2006 18:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-3359</guid>
		<description>I have got the same experience. I captured the communication and here is the brief result:

    [HTTP_HOST] =&#62; demo.webdevelopers.cz
    [HTTP_CONNECTION] =&#62; close
    [CONTENT_LENGTH] =&#62; 0
    [HTTP_USER_AGENT] =&#62; Mozilla/4.0
    [HTTP_ACCEPT_LANGUAGE] =&#62; en-us
    [SERVER_NAME] =&#62; &lt;a href="http://demo.webdevelopers.cz" rel="nofollow"&gt;Elixon CMS&lt;/a&gt;
    [REMOTE_ADDR] =&#62; 65.88.178.10
 
It claims to be "Mozilla/4.0" browser with default language set to en_US. I recieved only one hit on the homepage so far. I'm not hosting any blogs.</description>
		<content:encoded><![CDATA[<p>I have got the same experience. I captured the communication and here is the brief result:</p>
<p>    [HTTP_HOST] =&gt; demo.webdevelopers.cz<br />
    [HTTP_CONNECTION] =&gt; close<br />
    [CONTENT_LENGTH] =&gt; 0<br />
    [HTTP_USER_AGENT] =&gt; Mozilla/4.0<br />
    [HTTP_ACCEPT_LANGUAGE] =&gt; en-us<br />
    [SERVER_NAME] =&gt; <a href="http://demo.webdevelopers.cz" rel="nofollow">Elixon CMS</a><br />
    [REMOTE_ADDR] =&gt; 65.88.178.10</p>
<p>It claims to be &#8220;Mozilla/4.0&#8243; browser with default language set to en_US. I recieved only one hit on the homepage so far. I&#8217;m not hosting any blogs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ady</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-41</link>
		<dc:creator>ady</dc:creator>
		<pubDate>Sat, 05 Mar 2005 02:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-41</guid>
		<description>Yeah. Got hit by it too. Sometimes sporadic and sometimes it's very insistent. I never got round to writing to them. Blocked the IP in the end.</description>
		<content:encoded><![CDATA[<p>Yeah. Got hit by it too. Sometimes sporadic and sometimes it&#8217;s very insistent. I never got round to writing to them. Blocked the IP in the end.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: loid</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-40</link>
		<dc:creator>loid</dc:creator>
		<pubDate>Fri, 04 Mar 2005 23:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-40</guid>
		<description>The Symantec IP hammered netaloid so often that I finally denied 'em access a couple of months ago. I was unable to find a legitimate reason for them to be crawling so hard and often.</description>
		<content:encoded><![CDATA[<p>The Symantec IP hammered netaloid so often that I finally denied &#8216;em access a couple of months ago. I was unable to find a legitimate reason for them to be crawling so hard and often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cindy</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-39</link>
		<dc:creator>cindy</dc:creator>
		<pubDate>Fri, 04 Mar 2005 15:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-39</guid>
		<description>they have hit me too.</description>
		<content:encoded><![CDATA[<p>they have hit me too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alfons</title>
		<link>http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-38</link>
		<dc:creator>alfons</dc:creator>
		<pubDate>Fri, 04 Mar 2005 14:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://spamhuntress.com/2005/03/04/symantec-crawling-blogs/#comment-38</guid>
		<description>I saw the same since writing something about (D)DOS on my blog.</description>
		<content:encoded><![CDATA[<p>I saw the same since writing something about (D)DOS on my blog.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
