{"id":927,"date":"2010-05-22T00:00:00","date_gmt":"2010-05-22T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/05\/22\/google-rolls-out-encrypted-search\/"},"modified":"2021-12-30T11:38:24","modified_gmt":"2021-12-30T11:38:24","slug":"google-rolls-out-encrypted-search","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2010\/05\/22\/google-rolls-out-encrypted-search\/","title":{"rendered":"Google Rolls Out Encrypted Search"},"content":{"rendered":"<p>Google kept this one until after the Google I\/O 2010 conference, but it&#8217;s certainly a big announcement.  Google has now enabled SSL (Secure Sockets Layer) encryption of its search engine ensuring that any web search user&#8217;s conduct stays private.  The service includes a modified logo to help indicate that you&#8217;re searching using SSL and that you may encounter a somewhat different Google search experience,&#8221; he explained.  Google has started adopting https:\/\/ secure connections for some of its services, most notably for Gmail, for which SSL connections are enabled by default for all traffic.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The new encrypted Google search is in beta for now, as the service is not yet on par with the regular search engine.  For one, secure connections are only enabled for the core search engine and not for things like Image Search or Google Maps.  <\/p>\n<p>Images will still show up in the results thanks to the Universal Search feature, but following the links will switch you to the regular, unencrypted search.<\/p>\n<p>http:\/\/news.softpedia.com\/news\/Google-Rolls-Out-Encrypted-Search-142722.shtml<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-927","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/927","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=927"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/927\/revisions"}],"predecessor-version":[{"id":3414,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/927\/revisions\/3414"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=927"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=927"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}