Seeker

LookSeek.com bot

[jonasjacek]

Got hit by this bot in the last 24 hours. All requests were coming from the same IP.

UA: Seeker v.1
Protocol: HTTP/1.0
Robots.txt: Yes
Host: Rackspace US, Inc.
Country: US
NetRange: 23.253.0.0 - 23.253.255.255
CIDR: 23.253.0.0/16

Thread from 2003:
[webmasterworld.com ]

Trying to use lookseek.com from Germany brings up a 'LookSeek Search is no longer available outside the USA or Canada' message. Does anyone have experience with Seeker v.1? How does the bot behave once you grant it access (I do not have this bot whitelisted)?

[edited by: keyplyr at 8:25 am (utc) on Oct 18, 2016]
[edit reason] removed specific IP address [/edit]

[keyplyr]

As that earlier thread suggests, I've always blocked it. Doesn't show up very often anyway.

Bots from leased ranges like Rackspace always get block by default at my sites until I see who/what/why from them. Those who are unknown and do not include an info page URL in the UA string will likely stay blocked, as this one has.

[jonasjacek]

Thank you for your reply and clarification. The bot actually came with a info page URL (/seeker/) but there is nothing on it. I generally allow search engines but this one looks dubious. I'll keep it blocked.

[keyplyr]

Thanks. When documenting UAs, it's helpful to include the entire UA string, especially if it has changed since earlier sightings. Sometimes the additional attributes can help fill in the missing pieces.

It appears their SERP may be supplemented (or they crawled a lot of pages before I caught them.) I have their UA blocked yet my pages are indexed.

I may relax that block and watch them a while.

[jonasjacek]

Here's one (anonymized) request snippet with the full UA string:

23.253.XXX.XX - - [18/Oct/2016:01:01:26 +0200] "GET /robots.txt HTTP/1.0" 200 1160 "-" "Seeker v.1 http://LookSeek.com/seeker/" "example.com"

Example.com is a client website.