Symantec crawling blogs?
Etanisla is complaining about the bot
65.88.178.10
I’ve got a few sites, and tracked it across several. Only interested in blogs, and occasionally will hit other pages. My guess is they’re linked to from blogs somewhere.
It does HEAD on images.
And the IP number appears to belong to Symantec, if the address in the tracking info is correct.
Why does Symantec crawl blogs? No idea…
March 4th, 2005 at 8:43 am
I saw the same since writing something about (D)DOS on my blog.
March 4th, 2005 at 9:30 am
they have hit me too.
March 4th, 2005 at 5:22 pm
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.
March 4th, 2005 at 8:56 pm
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.
February 13th, 2006 at 12:38 pm
I have got the same experience. I captured the communication and here is the brief result:
[HTTP_HOST] => demo.webdevelopers.cz
[HTTP_CONNECTION] => close
[CONTENT_LENGTH] => 0
[HTTP_USER_AGENT] => Mozilla/4.0
[HTTP_ACCEPT_LANGUAGE] => en-us
[SERVER_NAME] => Elixon CMS
[REMOTE_ADDR] => 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.
February 13th, 2006 at 3:02 pm
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!
May 3rd, 2007 at 12:53 pm
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!