SeekportBot

65.108.103.105

[Bewenched]

65.108.103.105 (United States)
Mozilla/5.0 (compatible; SeekportBot; https ://bot.seekport.com)
Hungry bugger.

Not one hit on the robots.txt file

[not2easy]

I have that IP listed as Hetzner (DE)
65.108.0.0 - 65.109.255.255
CIDR: 65.108.0.0/15

seekport bot is not one I've seen but coming from a server farm, it might be a distributed bot so UA block might keep it out better than CIDR.

[lucy24]

Not one hit on the robots.txt file

Huh, that's odd. On my site they do ask for robots.txt, and were authorized after demonstrating compliance. (Unfortunately I don't keep careful records of this point, so I don't know how long it's been. But it must be pretty recent; for much of last year I only see them requesting robots.txt.) If not authorized, they would be blocked on header grounds.

I see them from 65.108.various, and from 65.21 and less often from 135.181. The latter is Hetzner; I've never had occasion to look up the other two.

[not2easy]

135.181. is also Hetzner for the /16 and so is 65.21.0.0/16

[tangor]

Never seen much value in Hetzner hits, usually far from valid!

[lucy24]

fwiw, Hetzner is one of the few areas I still end up blocking by IP (another, no surprise, is OVH) even after moving primarily to header-based access controls.

[OldFaces]

huh. same here. They crawl like mad...I even went through the hosting company with these Hetzner guys asking them to stop crawling us. It trimmed down a bit.

[Bewenched]

I finally block via the useragent to make them stop.