Forum Moderators: open

Message Too Old, No Replies

Seeing GoogleBot on 50.234.128.0/17 (Comcast) ?

         

SumGuy

2:17 am on Mar 13, 2018 (gmt 0)

5+ Year Member Top Contributors Of The Month



Today I'm seeing a bot-hit from 50.234.200.*. This is pretty much the first hit I've ever seen from 50.234/16.

The user-agent is this:
Mozilla/5.0 (compatible; Googlebot/2.1; +http//www.google.com/bot.html)

Best I can figure out, it belongs to this:
50.234.128.0/17 Comcast Cable Communications
Can't get any better granularity than that /17 listing.

Geo-IP location puts the IP in Pasadena Texas (I didn't know there was a Pasadena in Texas). The rDNS of that ip is 50.234.200.*.regus.net. No idea how Comcast delegates that IP to "regus.net".

Anyone else see any bot traffic from 50.234/16 claiming to be a Googlebot?

Should I treat this as a fake GoogleBot?


- - -

[edited by: keyplyr at 2:22 am (utc) on Mar 13, 2018]
[edit reason] obscured private IP address [/edit]

keyplyr

2:21 am on Mar 13, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Hi SumGuy

Fake UA. Googlebot is the most faked UA of all.

Many site owners install code to allow certain UAs access from verified IP ranges, while blocking those that come from other IPs.

That discussion would be done in the Apache Code Forum [webmasterworld.com]

lucy24

7:53 am on Mar 13, 2018 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



It's interesting that you rendered it twice as “GoogleBot” with capital B, because at one time that was a form used by certain fakers. (Like the assorted misspelled headers* over the years, it didn't last long.)


* “Referer” doesn’t count.

TravisDGarrett

10:04 am on Mar 13, 2018 (gmt 0)



Should I treat this as a fake GoogleBot?

Of-course. The Reverse DNS Lookup of the IP has to be from the domain googlebot.com or google.com