Linespider

(quasi update)

[Pfui]

This bot's come up before in recent years what with its Naver-Yahoo-etc. history. But I thought I'd mention that while it's respected robots.txt in the past, it's semi-sneaky about it now...

Initial hits to robots.txt were 25 minutes apart from --

crawl.147-92-246-90.search.line-apps.com
crawl.147-92-246-40.search.line-apps.com

-- with both using:

Mozilla/5.0 (compatible; Linespider/1.1; +https://lin.ee/4dwXkTH)

But two hours later, look who's back, with a cloaked UA and hitting disallowed pages:

crawl.147-92-246-160.search.line-apps.com
Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1

Tsk-tsk.

FWIW re Line Corporation, Japan (host site: www.naver.jp):

147.92.224.0 - 147.92.255.255
147.92.224.0/19

[not2easy]

Things evolve, not always for the better, interesting behavior. :( Good catch.

[lucy24]

:: quick run to raw logs ::

Heh. Every last request I find from ^147.92.2\d\d (keeping it simple) is (a) for an image, (b) blocked and (c) more narrowly 147.92.234-238.

I find Linespider most from 147.92.53.various, including all robots.txt requests.

:: further detour to domaintools, because I haven't updated my IP notes in ages ::

The entire bottom half of 147.92, including but not limited to the offending range under discussion, is LINE corp. in Japan; 147.92.52-55 on the other hand is an American entity calling itself Blazing SEO. Seems like it should be the other way around, doesn’t it?