I accidentally got a previously verified site 'unverified' in Google WMTs because I wasn't authorizing all their IPs for the Google-Site-Verification bot when it came knocking recently.
Here's the two ranges I see them cavorting around in and there may be others.
74.125.0.0-74.125.255.255 or 74.125.0.0/16
and
209.85.128.0-209.85.255.255 or 209.85.128.0/17
YMMV
g1smd
6:31 am on Jul 27, 2012 (gmt 0)
What's the full UA?
incrediBILL
7:40 am on Jul 27, 2012 (gmt 0)
Google-Site-Verification/1.0
dstiles
8:20 pm on Jul 27, 2012 (gmt 0)
I've been seeing a lot of verification visits over the past few weeks. Since they do not come from valid bot ranges with approved rDNS they've been blocked.
I particulary will not enable 74.125.0.0/16 - I've just posted the reason in another thread: look up mocality.
It is quite possible my sites are gradually becoming unverified - I haven't returned to WMT for a couple of years now and have no desire to do so.
incrediBILL
12:45 am on Jul 28, 2012 (gmt 0)
I particulary will not enable 74.125.0.0/16
GSV operates primarily in that range so not enabling it is risking losing your WMT validation for sure.
FWIW, very few of Google's bots actually support rDNS so the only choice is to validate them thru known Google IP ranges and headers.
wilderness
1:46 am on Jul 28, 2012 (gmt 0)
I haven't returned to WMT for a couple of years now and have no desire to do so.
dstiels, Its been longer than that for me. I registered one site and went through the verification and believe I checked the WMT site one or two times more and simply abandoned the thing.
The only Google range I have open is the 66.249.64-95
