softplus
msg:766851 | 6:08 pm on Jun 25, 2006 (gmt 0) |
Has anyone found logical groups for these datacenters yet? or Geo-targeting?
|
LuckyGuy
msg:766852 | 6:37 pm on Jun 25, 2006 (gmt 0) |
it is off topic: But how could you explain this: ping google.de shows up 216.239.39.104
ping www.google.de shows up 66.239.85.104 Url google.de in browser redirects to www.google.de. shouldn´t that be the same? or is a simple redirect?
|
softplus
msg:766853 | 6:42 pm on Jun 25, 2006 (gmt 0) |
>ping google.de shows up 216.239.39.104
>ping www.google.de shows up 66.239.85.104
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 [ 216.239.39.104 ]
and get "please go to www.google.de"
and then the final response at
www.google.de [ 66.239.85.104 ] It's a bit back and forth, but it works :-)
|
g1smd
msg:766854 | 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?
|
g1smd
msg:766855 | 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. 66.102.11.19
66.102.11.44
66.102.11.80
66.102.11.81
66.102.11.83
66.102.11.84
66.102.11.115
66.102.11.133
66.102.11.184
66.102.11.189 72.14.203.19
72.14.203.44
72.14.203.80
72.14.203.81
72.14.203.83
72.14.203.84
72.14.203.91
72.14.203.93
72.14.203.115
72.14.203.133
72.14.203.184
72.14.205.19
72.14.205.44
72.14.205.80
72.14.205.81
72.14.205.83
72.14.205.84
72.14.205.91
72.14.205.93
72.14.205.95
72.14.205.115
72.14.205.133
72.14.205.184
72.14.205.189
72.14.207.19
72.14.207.44
72.14.207.80
72.14.207.81
72.14.207.83
72.14.207.84
72.14.207.91
72.14.207.93
72.14.207.115
72.14.207.133
72.14.207.184
72.14.209.19
72.14.209.44
72.14.209.80
72.14.209.81
72.14.209.83
72.14.209.84
72.14.209.115
72.14.209.133
72.14.209.184
72.14.211.19
72.14.211.44
72.14.211.80
72.14.211.81
72.14.211.83
72.14.211.84
72.14.211.115
72.14.211.133
72.14.211.184
72.14.217.19
72.14.217.44
72.14.217.80
72.14.217.81
72.14.217.83
72.14.217.84
72.14.217.115
72.14.217.133
72.14.217.184
72.14.219.18
72.14.219.19
72.14.219.44
72.14.219.80
72.14.219.81
72.14.219.83
72.14.219.84
72.14.219.115
72.14.219.133
72.14.219.184
72.14.221.18
72.14.221.19
72.14.221.44
72.14.221.80
72.14.221.81
72.14.221.83
72.14.221.84
72.14.221.91
72.14.221.93
72.14.221.115
72.14.221.133
72.14.221.184
72.14.223.18
72.14.223.19
72.14.223.44
72.14.223.80
72.14.223.81
72.14.223.83
72.14.223.84
72.14.223.115
72.14.223.133
72.14.223.184
72.14.235.18
72.14.235.19
72.14.235.44
72.14.235.80
72.14.235.81
72.14.235.83
72.14.235.84
72.14.235.115
72.14.235.133
72.14.235.184
72.14.253.18
72.14.253.19
72.14.253.44
72.14.253.80
72.14.253.81
72.14.253.83
72.14.253.84
72.14.253.115
72.14.253.133
72.14.253.184 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.
|
unreviewed
msg:766856 | 1:02 am on Jul 4, 2006 (gmt 0) |
>>Is this all the Class C blocks in use, or are there more? [ws.arin.net...] 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. ;)
|
g1smd
msg:766857 | 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.
|
unreviewed
msg:766858 | 12:10 am on Jul 5, 2006 (gmt 0) |
>> I have no idea why they would need that many. Three words, ISP.
|
Komodo_Tale
msg:766859 | 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.
|
g1smd
msg:766860 | 9:32 am on Jul 5, 2006 (gmt 0) |
These are the major IP ranges that Google have: 8.6.48.0 - 8.6.55.255
64.68.80.0 - 64.68.87.255
64.233.160.0 - 64.233.191.255 - In Use
66.102.0.0 - 66.102.15.255 - In Use
66.249.64.0 - 66.249.95.255 - In Use
72.14.192.0 - 72.14.255.255 - In Use
209.85.128.0 - 209.85.255.255
216.239.32.0 - 216.239.63.255 - In Use Only a few selected IP addresses are in use out of millions of possible combinations.
|
gcc_llc
msg:766861 | 3:26 pm on Jul 5, 2006 (gmt 0) |
Funny observation. 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. Go figure.
|
balam
msg:766862 | 5:07 am on Jul 6, 2006 (gmt 0) |
> pinging 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.
|
ogletree
msg:766863 | 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.
|
straylite
msg:766864 | 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: [ws.arin.net...] 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) 216.239.32.0 - 216.239.63.255
Google Inc. GOOGLE (NET-64-233-160-0-1) 64.233.160.0 - 64.233.191.255
Google Inc. GOOGLE (NET-66-249-64-0-1) 66.249.64.0 - 66.249.95.255
Google Inc. GOOGLE (NET-72-14-192-0-1) 72.14.192.0 - 72.14.255.255
Google Inc. GOOGLE (NET-209-85-128-0-1) 209.85.128.0 - 209.85.255.255 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...
|
g1smd
msg:766865 | 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.
|
g1smd
msg:766866 | 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 66.102.11.40 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.
|
claus
msg:766867 | 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.
|
g1smd
msg:766868 | 9:56 pm on Jul 6, 2006 (gmt 0) |
I think these are all the Class-C blocks that respond: 64.233.161.x
64.233.163.x
64.233.167.x
64.233.169.x
64.233.171.x
64.233.179.x
64.233.183.x
64.233.185.x
64.233.187.x
64.233.189.x 66.102.1.x
66.102.7.x
66.102.9.x
66.102.11.x 66.249.81.x
66.249.83.x
66.249.85.x
66.249.89.x
66.249.91.x
66.249.93.x 72.14.203.x
72.14.205.x
72.14.207.x
72.14.209.x
72.14.211.x
72.14.215.x
72.14.217.x
72.14.219.x
72.14.221.x
72.14.223.x
72.14.235.x
72.14.253.x 216.239.33.x - X
216.239.35.x - X
216.239.37.x
216.239.39.x
216.239.41.x - X
216.239.51.x
216.239.53.x
216.239.55.x - X
216.239.57.x
216.239.59.x
216.239.63.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?
|
g1smd
msg:766869 | 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.
|
lgn1
msg:766870 | 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.
|
g1smd
msg:766871 | 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?
|
f123
msg:3000767 | 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?
|
g1smd
msg:3001597 | 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.
|
g1smd
msg:3007422 | 3:15 pm on Jul 14, 2006 (gmt 0) |
What are these URLs? http://gfe-ar.google.com/
http://gfe-fg.google.com/
http://gfe-po.google.com/ Where do they fit into things? Are there any more like these?
|
g1smd
msg:3007463 | 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.
|
g1smd
msg:3007524 | 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
|
g1smd
msg:3011301 | 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?
|
g1smd
msg:3015148 | 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: 66.249.89.160
66.249.89.161
66.249.89.162
64.233.189.160
64.233.189.161
64.233.189.162
66.102.7.160
66.102.7.161
66.102.7.162
72.14.203.160
72.14.203.161
72.14.203.162 Direct IP access results in a redirect to www.google.co.uk instead.
|
colin_h
msg:3015488 | 6:28 am on Jul 20, 2006 (gmt 0) |
Anyone else noticing that Google.co.uk is missing its cache links at the moment?
|
g1smd
msg:3022396 | 10:38 am on Jul 26, 2006 (gmt 0) |
Here is a list of IP addreses matched with active GFE domain names. 72.14.223.104 - gfe-ar
72.14.223.99 - gfe-ar2
72.14.223.147 - gfe-ar3 72.14.211.104 - gfe-au
72.14.211.99 - gfe-au2 72.14.209.104 - gfe-bf
72.14.209.99 - gfe-bf2 216.239.63.104 - gfe-bp
216.239.63.99 - gfe-bp2 72.14.217.104 - gfe-bu
72.14.217.99 - gfe-bu2 66.249.81.104 - gfe-bx
66.249.81.99 - gfe-bx2
66.249.81.147 - gfe-bx3 216.239.57.104 - gfe-cw
216.239.57.99 - gfe-cw2
216.239.57.147 - gfe-cw3
216.239.57.103 - gfe-cw4 216.239.39.104 - gfe-dc
216.239.39.99 - gfe-dc2 72.14.219.104 - gfe-ed
72.14.219.99 - gfe-ed2
72.14.219.147 - gfe-ed3 72.14.207.104 - gfe-eh
72.14.207.99 - gfe-eh2 66.249.85.104 - gfe-ff
66.249.85.99 - gfe-ff2 72.14.221.104 - gfe-fg
72.14.221.99 - gfe-fg2
72.14.221.147 - gfe-fg3 216.239.59.104 - gfe-gv
216.239.59.99 - gfe-gv2
216.239.59.147 - gfe-gv3
216.239.59.103 - gfe-gv4 66.102.1.104 - gfe-he 64.233.189.104 - gfe-hk 64.233.179.104 - gfe-hs (*)
64.233.179.99 - gfe-hs2 72.14.215.104 - gfe-hu
72.14.215.99 - gfe-hu2 66.249.91.104 - gfe-ik
66.249.91.99 - gfe-ik2
66.249.91.147 - gfe-ik3 216.239.53.104 - gfe-in
216.239.53.99 - gfe-in2
216.239.53.147 - gfe-in3 64.233.187.104 - gfe-jc
64.233.187.99 - gfe-jc2 66.249.89.104 - gfe-jp
66.249.89.99 - gfe-jp2 216.239.51.104 - gfe-kc
216.239.51.99 - gfe-kc2 66.102.11.104 - gfe-kr
66.102.11.99 - gfe-kr2 66.102.9.104 - gfe-lm
66.102.9.99 - gfe-lm2
66.102.9.147 - gfe-lm3 66.102.7.104 - gfe-mc
66.102.7.99 - gfe-mc2
66.102.7.147 - gfe-mc3 64.233.183.104 - gfe-nf
64.233.183.99 - gfe-nf2
64.233.183.147 - gfe-nf3
64.233.183.103 - gfe-nf4 64.233.163.104 - gfe-nz
64.233.163.99 - gfe-nz2 64.233.161.104 - gfe-od
64.233.161.99 - gfe-od2
64.233.161.147 - gfe-od3 72.14.253.104 - gfe-po
72.14.253.99 - gfe-po2
72.14.253.147 - gfe-po3 64.233.167.104 - gfe-py
64.233.167.99 - gfe-py2
64.233.167.147 - gfe-py3 72.14.205.104 - gfe-qb
72.14.205.99 - gfe-qb2 64.233.171.104 - gfe-rn
64.233.171.99 - gfe-rn2
64.233.171.147 - gfe-rn3 72.14.203.104 - gfe-ro
72.14.203.99 - gfe-ro2 72.14.235.104 - gfe-tw
72.14.235.99 - gfe-tw2
72.14.235.147 - gfe-tw3 66.249.93.104 - gfe-ug
66.249.93.99 - gfe-ug2 64.233.179.104 - gfe-ui (*) 216.239.37.104 - gfe-va
216.239.37.99 - gfe-va2 64.233.185.104 - gfe-wr
64.233.185.99 - gfe-wr2 66.249.83.104 - gfe-wx
66.249.83.99 - gfe-wx2 64.233.169.104 - gfe-yo
64.233.169.99 - 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. 66.249.87.104 - gfe-lo - Not Responding
66.249.87.99 - 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....
|
g1smd
msg:3024957 | 10:01 pm on Jul 27, 2006 (gmt 0) |
Some new IP addresses for www.google.cn discovered today: 59.151.21.100
59.151.21.101 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 [2] 3 ) > > |
|
|
