| 6:08 pm on Jun 25, 2006 (gmt 0)|
Has anyone found logical groups for these datacenters yet? or Geo-targeting?
| 6:37 pm on Jun 25, 2006 (gmt 0)|
it is off topic: But how could you explain this:
ping google.de shows up 220.127.116.11
ping www.google.de shows up 18.104.22.168
Url google.de in browser redirects to www.google.de.
shouldn´t that be the same? or is a simple redirect?
| 6:42 pm on Jun 25, 2006 (gmt 0)|
>ping google.de shows up 22.214.171.124
>ping www.google.de shows up 126.96.36.199
Both are domain names that need to get resolved.
Once they are resolved, the server might issue a redirect or answer directly. But for that to happen, it will need to get resolved first.
you might get
google.de [ 188.8.131.52 ]
and get "please go to www.google.de"
and then the final response at
www.google.de [ 184.108.40.206 ]
It's a bit back and forth, but it works :-)
| 12:35 am on Jul 4, 2006 (gmt 0)|
Post 27 should have said:
>> been listed so far and perhaps a few more <<
Can you separately list those that you have added that are not on my posted lists, because the list on my hard drive is already bigger than what is posted here, and my list also includes a lot of information about what is live, and what is history?
| 12:36 am on Jul 4, 2006 (gmt 0)|
Post 28 should have said:
That newer list hints that there may be yet more undiscovered IP addresses.
I think that I have now found most of them. There are more than a hundred.
There may well be a few more to be found yet.
I did a Google search for a few of the new IP addresses discovered and found several of them to be highly discussed in Chinese and other Asian language forums.
Maybe some of those IPs are never shown to US or European searchers.
| 1:02 am on Jul 4, 2006 (gmt 0)|
>>Is this all the Class C blocks in use, or are there more?
That list also includes Google’s IPV6 block,
2001:4860:0000:0000:0000:0000:0000:0000 - 2001:4860:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
That block alone is 79 billion billion billion addresses.
Good luck on your endeavor g1smd. ;)
| 11:21 pm on Jul 4, 2006 (gmt 0)|
I have no idea why they would need that many. Seems more than a bit OTT to me.
Anyway, thanks for the list. It confirms that we have probably found almost all of the current IP addresses that are in use right now, and that there are two other blocks to look at in the future.
| 12:10 am on Jul 5, 2006 (gmt 0)|
>> I have no idea why they would need that many.
Three words, ISP.
| 1:32 am on Jul 5, 2006 (gmt 0)|
If someone knows PHP or Perl or such they could easily write a program to loop through each of the class c blocks and loop from 0 to 999 to test the last part.
I would do this myself except my outgoing firewall disallows pinging.
| 9:32 am on Jul 5, 2006 (gmt 0)|
These are the major IP ranges that Google have:
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199
188.8.131.52 - 184.108.40.206 - In Use
220.127.116.11 - 18.104.22.168 - In Use
22.214.171.124 - 126.96.36.199 - In Use
188.8.131.52 - 184.108.40.206 - In Use
220.127.116.11 - 18.104.22.168
22.214.171.124 - 126.96.36.199 - In Use
Only a few selected IP addresses are in use out of millions of possible combinations.
| 3:26 pm on Jul 5, 2006 (gmt 0)|
When I search with site:domain.com with no filter on I get 90k results.
When I search with a strict filter on I get 140k results.
| 5:07 am on Jul 6, 2006 (gmt 0)|
A ping will tell you if a server is at a given IP address (and responding), but it won't tell you if it's a web server.
Hasn't anyone done a port scan of the ranges? You'd only have to look at Port 80...
I scanned the 64.233.160-191.x addresses, and received over 1600 responses. I don't doubt that there are more servers in that range that I missed, since I had my timeout threshold set very low.
Am I about to post all 1600+ IPs? Hah, no - no one "reads" a post like that, and I'm sure it would count as bad netiquette. But, if you have 32KB free space in your StickyMail, then the list is yours for the asking...
A note to The Future
If this post is more than 2 or 3 weeks old, then chances are excellent that I've deleted the list. Data like this can go stale pretty quickly... Do a port scan for your own, up-to-date list.
| 3:11 pm on Jul 6, 2006 (gmt 0)|
This thread [webmasterworld.com] has a lot of good videos that shed some light on this for me.
| 3:51 pm on Jul 6, 2006 (gmt 0)|
If you're trying to find out where Google's data centres are, searching the web for lists of IPs is just going to flood you with data.
Google, like other large companies is fairly well organised, and like every other Internet company has to have its IPs allocated to it by places such as ARIN (the American Registry for Internet Names). You can search ARIN by name, so:
gets you all of the ARIN-registered netblocks for google, assuming they use the Google name everywhere:
Google Inc. GOOGLE (NET-216-239-32-0-1) 188.8.131.52 - 184.108.40.206
Google Inc. GOOGLE (NET-64-233-160-0-1) 220.127.116.11 - 18.104.22.168
Google Inc. GOOGLE (NET-66-249-64-0-1) 22.214.171.124 - 126.96.36.199
Google Inc. GOOGLE (NET-72-14-192-0-1) 188.8.131.52 - 184.108.40.206
Google Inc. GOOGLE (NET-209-85-128-0-1) 220.127.116.11 - 18.104.22.168
You can do this on other NCCs too, like APNIC, AfrNIC, RIPE and so on.
If you're looking for geographical locations, you could just cross-reference those addresses with some GeoIP data and you'd have a map. You could even use Google Maps to map google's IP addresses :)
Remember that the hierarchy of information is there - but it helps if you go top-down, instead of bottom-up...
| 9:00 pm on Jul 6, 2006 (gmt 0)|
Thanks for the longer explanation of the hints posted in #36, though the post in #36 also links to a much longer list of ARIN IP assignments to Google. That has confirmed the bounds of possible addresses.
| 9:22 pm on Jul 6, 2006 (gmt 0)|
>> I scanned the 64.233.160-191.x addresses, and received over 1600 responses. <<
Oh yes, there are many IPs that get a response from Google, with a logo, and a "Server Error" message, like 22.214.171.124 and many others.
I have seen lists of bot IPs, and other lists too. I have been focussing only on IPs that allow you to search the web.
| 9:34 pm on Jul 6, 2006 (gmt 0)|
>> server, port 80
A web server alone does not cut it. Google serves up many other things than search results.
Some of those will be Gmail, some google directory, some blogs, and then all kinds of other stuff. What you would want to identify would probably only be the subset that serves a search box.
| 9:56 pm on Jul 6, 2006 (gmt 0)|
I think these are all the Class-C blocks that respond:
216.239.33.x - X
216.239.35.x - X
216.239.41.x - X
216.239.55.x - X
These IP addresses respond only for selected values of x, where x can be any one of these:
17, 18, 19, 44, 80, 81, 83, 84, 91, 93, 95, 99, 100, 101, 102, 103, 104, 107, 115, 133, 147, 184, 189, 214.
Not every single possible combination from this list is actually in use - but the vast majority of them are.
All of those that do respond give a Google search box labelled "Google English".
Items marked with an X are no longer in use.
Are there any more Class-C blocks in use?
Are there any other values for the final number that work?
| 8:40 am on Jul 7, 2006 (gmt 0)|
I also see 66.249.87.x mentioned in some lists, but those do not work at the moment.
| 10:19 am on Jul 7, 2006 (gmt 0)|
Im sure that Google is clustering servers also.
Rather than having a list of hundreds or thousands of individual Google servers, we should concentrate on grouping of servers, that show the same results.
Im sure Google does not roll updates out to one individual server at a time.
Thats my 2 cents worth.
| 10:50 am on Jul 7, 2006 (gmt 0)|
What I see happen most of the time is that if you query google.com or any other doogle country TLD, you are served something from x.x.x.99 or x.x.x.104 or x.x.x.107 or x.x.x.147 every time (even though many more than that exist), and over the course of a month or two you'll only ever see about 7 or 8 Class-C blocks (even though many more than that exist). So, that does appear to leave a very large number of IPs that you never see.
The question is, are those other IPs seen by people elsewhere instead, or are they another route in to the same servers, a backup address should the main one fail due to DNS failure or something?
| 6:03 am on Jul 10, 2006 (gmt 0)|
Wow g1smd! Thanks for all your research.
I'm still new to posting and this may be a pointless question, but do you know of any DC IP lists for Yahoo, MSN, Ask and/or DMOZ?
| 7:05 pm on Jul 10, 2006 (gmt 0)|
I have seen a list for Yahoo. Google for it. :-)
No idea about MSN or Ask. The ODP has one IP only.
| 3:15 pm on Jul 14, 2006 (gmt 0)|
What are these URLs?
Where do they fit into things?
Are there any more like these?
| 3:24 pm on Jul 14, 2006 (gmt 0)|
Reports of the demise of the old www-va.google.com style Google datacentre URLs were way too early.
They are over here instead, and have grown in number:
gfe-au, gfe-ar, gfe-bf, gfe-bp, gfe-bu, gfe-bx, gfe-cw, gfe-dc, gfe-ed, gfe-eh, gfe-ff, gfe-fg, gfe-gv, gfe-he, gfe-hk, gfe-hs, gfe-hu, gfe-ik, gfe-in, gfe-jc, gfe-jp, gfe-kc, gfe-kr, gfe-lm, gfe-lo, gfe-mc, gfe-nf, gfe-nz, gfe-od, gfe-po, gfe-py, gfe-qb, gfe-rn, gfe-ro, gfe-tw, gfe-ug, gfe-ui, gfe-va, gfe-wr, gfe-wx, gfe-yo
Several two-letter pairs match the old lists. Many are missing and there are very many new ones.
| 3:42 pm on Jul 14, 2006 (gmt 0)|
There are 41 class-C blocks in my earlier list, and 41 URLs in the above "two letter" list.
Draw your own conclusions.
Additionally, as well as the gfe-cw.google.com type URLs, many of them also respond to these formats too:
gfe-cw2.google.com and gfe-cw3.google.com
| 10:22 am on Jul 17, 2006 (gmt 0)|
>> For those who are keeping track, this is probably a good point for a review. Here are all the datacenters that have been listed so far and perhaps a few more. <<
Actually, it was quite a bad time for a review, as the list you published doesn't include extra stuff that I have here, but not yet published, and now dozens of sites have copied that list, which is incomplete.
Additionally, I asked by PM if you could flag up the items in your list that are new and not already in my list. Please can you do that?
| 10:52 pm on Jul 19, 2006 (gmt 0)|
Google China has its own DCs.
They use the following IPs for www.google.cn and these cannot be directly acessed by IP address from here:
Direct IP access results in a redirect to www.google.co.uk instead.
| 6:28 am on Jul 20, 2006 (gmt 0)|
Anyone else noticing that Google.co.uk is missing its cache links at the moment?
| 10:38 am on Jul 26, 2006 (gmt 0)|
Here is a list of IP addreses matched with active GFE domain names.
126.96.36.199 - gfe-ar
188.8.131.52 - gfe-ar2
184.108.40.206 - gfe-ar3
220.127.116.11 - gfe-au
18.104.22.168 - gfe-au2
22.214.171.124 - gfe-bf
126.96.36.199 - gfe-bf2
188.8.131.52 - gfe-bp
184.108.40.206 - gfe-bp2
220.127.116.11 - gfe-bu
18.104.22.168 - gfe-bu2
22.214.171.124 - gfe-bx
126.96.36.199 - gfe-bx2
188.8.131.52 - gfe-bx3
184.108.40.206 - gfe-cw
220.127.116.11 - gfe-cw2
18.104.22.168 - gfe-cw3
22.214.171.124 - gfe-cw4
126.96.36.199 - gfe-dc
188.8.131.52 - gfe-dc2
184.108.40.206 - gfe-ed
220.127.116.11 - gfe-ed2
18.104.22.168 - gfe-ed3
22.214.171.124 - gfe-eh
126.96.36.199 - gfe-eh2
188.8.131.52 - gfe-ff
184.108.40.206 - gfe-ff2
220.127.116.11 - gfe-fg
18.104.22.168 - gfe-fg2
22.214.171.124 - gfe-fg3
126.96.36.199 - gfe-gv
188.8.131.52 - gfe-gv2
184.108.40.206 - gfe-gv3
220.127.116.11 - gfe-gv4
18.104.22.168 - gfe-he
22.214.171.124 - gfe-hk
126.96.36.199 - gfe-hs (*)
188.8.131.52 - gfe-hs2
184.108.40.206 - gfe-hu
220.127.116.11 - gfe-hu2
18.104.22.168 - gfe-ik
22.214.171.124 - gfe-ik2
126.96.36.199 - gfe-ik3
188.8.131.52 - gfe-in
184.108.40.206 - gfe-in2
220.127.116.11 - gfe-in3
18.104.22.168 - gfe-jc
22.214.171.124 - gfe-jc2
126.96.36.199 - gfe-jp
188.8.131.52 - gfe-jp2
184.108.40.206 - gfe-kc
220.127.116.11 - gfe-kc2
18.104.22.168 - gfe-kr
22.214.171.124 - gfe-kr2
126.96.36.199 - gfe-lm
188.8.131.52 - gfe-lm2
184.108.40.206 - gfe-lm3
220.127.116.11 - gfe-mc
18.104.22.168 - gfe-mc2
22.214.171.124 - gfe-mc3
126.96.36.199 - gfe-nf
188.8.131.52 - gfe-nf2
184.108.40.206 - gfe-nf3
220.127.116.11 - gfe-nf4
18.104.22.168 - gfe-nz
22.214.171.124 - gfe-nz2
126.96.36.199 - gfe-od
188.8.131.52 - gfe-od2
184.108.40.206 - gfe-od3
220.127.116.11 - gfe-po
18.104.22.168 - gfe-po2
22.214.171.124 - gfe-po3
126.96.36.199 - gfe-py
188.8.131.52 - gfe-py2
184.108.40.206 - gfe-py3
220.127.116.11 - gfe-qb
18.104.22.168 - gfe-qb2
22.214.171.124 - gfe-rn
126.96.36.199 - gfe-rn2
188.8.131.52 - gfe-rn3
184.108.40.206 - gfe-ro
220.127.116.11 - gfe-ro2
18.104.22.168 - gfe-tw
22.214.171.124 - gfe-tw2
126.96.36.199 - gfe-tw3
188.8.131.52 - gfe-ug
184.108.40.206 - gfe-ug2
220.127.116.11 - gfe-ui (*)
18.104.22.168 - gfe-va
22.214.171.124 - gfe-va2
126.96.36.199 - gfe-wr
188.8.131.52 - gfe-wr2
184.108.40.206 - gfe-wx
220.127.116.11 - gfe-wx2
18.104.22.168 - gfe-yo
22.214.171.124 - gfe-yo2
216.239.33.x - www-ex - Gone long ago.
216.239.35.x - www-sj - Gone long ago.
216.239.41.x - www-fi - Gone long ago.
216.239.55.x - www-zu - Gone long ago.
126.96.36.199 - gfe-lo - Not Responding
188.8.131.52 - gfe-lo2 - Not Responding
Beware that there are likely to be a number of additional active x.x.x.99 and x.x.x.147 and x.x.x.103 IP addresses that do not yet have a domain name assigned to them.
(*) Note that gfe-hs and gfe-ui both point to the same IP address at the moment, and that that address was the test "Big Daddy" datacentre.
I assume that gfe-hs (x104) and gfe-hs2 (x99) are the regular names, and they aliased gfe-ui (x104) on to it for testing purposes internally, as in gfe-ui.google.com as the full URL.
More to follow....
| 10:01 pm on Jul 27, 2006 (gmt 0)|
Some new IP addresses for www.google.cn discovered today:
These are in a new Class-C block, that I haven't seen Google use before.
Continued in: [webmasterworld.com...]
[edited by: engine at 11:04 am (utc) on Oct. 2, 2006]
| This 61 message thread spans 3 pages: < < 61 ( 1  3 ) > > |