Curtis Free's Blog

About Blog Config DB Projects Scripts Wishlist Husband, father, geek, progressive.

Not all encrypted Google searches are equal

Google offers two separate encrypted (i.e., via HTTPS) search pages: (which has been established for some time) and (a more recent development). The former has generally lagged behind the standard Google search page in terms of features; looks more like the regular Google search page.

My personal motivation for preferring Google’s HTTPS variants is not to protect my search terms: rather, I am concerned with the cookie information being passed between my browser and Google’s servers. While I do not often (okay, ever) use “open Wi-Fi,” failure to use an encrypted connection means that there is increased potential for a session hijack (as highlighted by the widely-publicized Firesheep).

Aside from differences in each version’s “frills,” there is an important security-relevant difference between the two: the underlying search result links.

Note that links in Google search results look like they point directly at the result URL; however, they actually point back to Google’s own servers, which redirect the browser to the actual result. This means that Google can track clicks, lead to particular referers, and more.

On, these underlying links point back to; however, on, search result redirect links not use HTTPS.

For example, the first hit when searching for “Arch Linux” on is (line breaks added):

On, one has:

While it is unlikely that your session will be hijacked simply by following one of these redirections, note that any cookie information related to your authenticated session that is sent across the Internet unencrypted carries some potential for misuse if it is intercepted.

Users of the EFF’s HTTPS Everywhere Firefox extension are probably already using If you’re using Chrome, you can manually add a new search engine with a search string of:

If you don’t already use the HTTPS-fortified Google search pages, give it a try.

Update (16 Mar 2012):

The EFF has published a note pointing out another security-related discrepancy between the two subdomains.