I have it coming from Leaseweb, Amsterdam: 22.214.171.124 - 126.96.36.199
Other Leaseweb ranges: 188.8.131.52 - 184.108.40.206
I've blocked them for quite a while.
You may wish to expand on that range a bit. The RIPE route info indicates they've got the whole /16:
twengabot also coming from another Leaseweb range:
220.127.116.11 - 18.104.22.168
I saw it today coming from 94.75.247.nnn
Took robots.txt and stepped right into the honeypot.
Then left to go wash its feet ;)
In addition to asking for but ignoring robots.txt, it appears TwengaBot has already changed its name and URL string/country. This just in:
06/19 11:51:38 /robots.txt
06/19 11:51:39 /
No robots.txt, grabbed every page:
94.75.229.zzz - - [18/Jun/2010:14:32:48 -0600] "GET / HTTP/1.1" 200 5356 "-" "Mozilla/5.0 (compatible; Purebot/1.1; +http://www.puritysearch.net/)"
Interesting press release from Twenga.
However, most of the Internet traffic is generated via Twenga’s crawler. "A good search engine that displays accurate results with the right products and prices needs a lot of capacity," says Anes. "At this moment the TwengaBot uses about 100 dedicated servers that together scan around 100 million web pages per day. But I expect to be needing at least 500 dedicated servers at the data center within two years." As a result, the Twenga crawler also needs a huge quantity of bandwidth. "We consume a total of 2000 Terabytes of data traffic per month. Three- quarters of that is generated by the crawler, but fortunately LeaseWeb operates a hosting network with a lot of bandwidth," laughs Anes.
Nice to know that while Twenga is expanding on the backs of small businesses they are getting a good laugh at your expense.
having a NOSCRIPT installed in FF, and only allowing the site it self allowed, it makes think it is just another bottom feeder. Withou a GOOG spyware allowed it is good for NARA.
This new TwengaBot-Discover showed up twice today. Took 4 copies of robots.txt, then went on to grab every page on the site. Just a couple of hours later, it came back and took another complete copy of every page. It wouldn't be so bad, but the site doesn't sell anything.
Same IP address reported by Pfui.
As it ignores robots.txt it shouldn't have surprised me that it does not understand Crawl-delay.
Name/string change #3 -- for the worse. Again from Leaseweb:
(Asterisk in string is original. "n" in IP is obfuscation.)
LEASEWEB IP Ranges from RIPE: [db.ripe.net...]
All though I only have wider ranges, 2-2-2 much abuse over the years that comes from that Hosting Company:
start_ip - end_ip
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206
UA: TwengaBot-Discover (http://www.twenga.fr/bot-discover.html)
Sucking up (100s of) pages, like there's no tomorrow ;-)
Will let it run for a while and see.
@Web_Savvy: If it ignored your robots.txt, block it ASAP. Why let some stranger abuse your resources -- content and cash -- for their own purposes, with no apparent benefit to you?
Project Honeypot on 220.127.116.11
Geographic Location [Netherlands] Netherlands
Spider First Seen approximately 3 months, 1 week ago
Spider Last Seen within 1 week
Spider Sightings 4,347 visit(s)
User-Agents seen with 4 user-agent(s)
Threat Rating 46 (Read More)
First Rule-Break On approximately 2 months, 4 weeks ago
Last Rule-Break On within 2 months, 4 weeks
Rule Breaks 2 web page navigation rule(s) broken by this IP
18.104.22.168's User Agent Strings
Interesting. I recently enabled this bot (IPs 22.214.171.124-126.96.36.199) as an apparently reasonable SE. I'll keep an eye on it.
Haven't seen it on the 85.17 range yet but 85.17/16 is leaseweb, hence banned anyway, so it may not have registered with me beyond "another leaseweb hit".
@Pfui: Thanks for the input.
Actually, this site of ours is a kind of 'working experiment' - we're deriving a lot of research data and intelligence out of all this and that's why we let these bots ply their trade awhile.
Twenga just followed a nofollow link into a trap in a folder that was disallowed in robots.txt. Stupid Twenga! Going to have to watch this bot. <sigh>
Well, I gave it a fair shot. Accepted a high rate of access on the grounds they were new sites to the bot, even allowed it a minor indiscretion as regards forms, but when it hit every blocked mail-a-friend page, that's it. Banned.