<P> According to Google's general privacy policy, "We (Google) may combine personal information from one service with information, including personal information, from other Google services". However, Google Public DNS's policy specifically states that "We don't correlate or combine information from our temporary or permanent logs with any personal information that you have provided Google for other services ." </P> <P> In December 2009, Google Public DNS was launched with its announcement on the Official Google Blog by product manager Prem Ramaswami, with an additional post on the Google Code blog . </P> <P> At the launch of Google Public DNS, it did not directly support DNSSEC . Although RRSIG records could be queried, the AD (Authenticated Data) flag was not set in the launch version, meaning the server was unable to validate signatures for all of the data . This was upgraded on 28 January 2013, when Google's DNS servers silently started providing DNSSEC validation information, but only if the client explicitly set the DNSSEC OK (DO) flag on its query . This service requiring a client - side flag was replaced on 6 May 2013 with full DNSSEC validation by default, meaning all queries will be validated unless clients explicitly opt out . </P> <P> Since June 2014, Google Public DNS automatically detects nameservers that support edns - client - subnet (ECS) options as defined in the IETF draft (by probing nameservers at a low rate with ECS queries and caching the ECS capability), and will send queries with ECS options to such nameservers automatically . </P>

What is the ip address of google search engine