The page searchdomaincheck returns your preferred Google domain. For me, visiting it returns https://www.google.com/
normally, but https://www.google.com.py/
in a temporary profile and incognito mode.
This is its main function, although I fail to see why it is needed if you're not using the Google search engine. To make this possible, Chromium has to be sending your Google cookies.
The request to searchdomaincheck is made by the GoogleURLTracker class, which says in its comments:
// This object is responsible for checking the Google URL once per network
// change, and if necessary prompting the user to see if they want to change to
// using it. The current and last prompted values are saved to prefs.
A "network change" will be detected, e.g., by the function OnIPAddressChanged()
.
I'm desperately trying not to behave tinfoilhattish here, but this sounds like a cheap way to associate a tracking cookie with an IP address.
According to List of Chromium Command Line Switches, the command-line switch --google-search-domain-check-url
should be able to stop this behavior.
Try invoking Chromium as follows:
chromium-browser --google-search-domain-check-url=localhost
Have you tried to open chrome://net-internals/#events ? I guess, it must be done BEFORE chromium connects to google. Not sure about this. – int – 2013-03-21T19:22:54.223
I see a
– Simon – 2013-03-21T19:27:01.473URL_REQUEST
to https://www.google.com/searchdomaincheck?format=url&type=chrome and then aSOCKET
tossl/www.google.com:443
If it is only url, chromium connects at startup, you should't worry. Otherwise you can just block all connections to google via firewall. – int – 2013-03-21T19:30:16.427
Do you know what this request is for? – Simon – 2013-03-21T19:32:16.187
It lets chromium to find default search domain for google (for example, google.co.uk, if user is from UK). I do now know why it sends this request, if you set another default search engine. – int – 2013-03-21T19:36:56.947