Google Safe Browsing

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Google Safe Browsing
Google Safe Browsing.svg
Screenshot
Google Safe Browsing Screenshot.png
Screenshot of the Google Safe Browsing in an Android device blocking a deceptive site.
Original author(s)Google
Developer(s)Google
Operating systemAndroid, Chrome OS, Windows, macOS, iOS, Web browsers
TypeInternet Security
Websitesafebrowsing.google.com

Google Safe Browsing is a service from Google that attempts to help protect devices by showing warnings to users when they attempt to navigate to dangerous sites or download dangerous files. Safe Browsing also notifies webmasters when their websites are compromised by malicious actors and helps them diagnose and resolve the problem so their visitors stay safe. This protection works across Google products and is claimed to “power safer browsing experiences across the Internet”.[1] It lists URLs for web resources that contain malware or phishing content.[2][3] Browsers like Google Chrome, Safari, Firefox, Vivaldi, Brave and GNOME Web use these lists from Google Safe Browsing service to check pages against potential threats.[4][5] Google also provides a public API for the service.[6]

Google provides information to Internet service providers, by sending e-mail alerts to autonomous system operators regarding threats hosted on their networks.[3]

As of September 2017, over 3 billion Internet devices are protected by the service.[7] Alternatives are offered by both Tencent and Yandex.[8]

Clients protected[edit]

Privacy[edit]

Google maintains the Safe Browsing Lookup API, which has a privacy drawback: "The URLs to be looked up are not hashed so the server knows which URLs the API users have looked up". The Safe Browsing Update API, on the other hand, compares 32-bit hash prefixes of the URL to preserve privacy.[9][10] The Chrome, Firefox and Safari browsers use the latter.[11]

Safe Browsing also stores a mandatory preferences cookie on the computer.[12]

Google Safe Browsing "conducts client-side checks. If a website looks suspicious, it sends a subset of likely phishing and social engineering terms found on the page to Google to obtain additional information available from Google's servers on whether the website should be considered malicious". Logs, which include an IP address and one or more cookies, are kept for two weeks and are tied to the other Safe Browsing requests made from the same device.[13]

In most applications - apart from Apples Safari where Apple uses a proxy - the API is installed in a ways that Google continuously gets the actual IP address of the user.[14] This enables Google - at last technically - to constantly track users in great detail on their way through the internet, while sending Emails to Gmail-Accounts or using Google services.

Criticism[edit]

Websites not containing malware have been blacklisted by Google Safe Browsing due to the presence of infected ads. Requesting removal from the blacklist requires the webmaster to create a Google Webmaster's Tool account and wait several days for removal to come into effect.[15] There have also been concerns that Google Safe Browsing may be used for censorious purposes in the future, however this has not yet occurred.[16]

See also[edit]

References[edit]

  1. ^ "Google Safe Browsing". safebrowsing.google.com. Retrieved 2021-12-29.
  2. ^ Schwartz, Barry (May 23, 2008). "Google's Safe Browsing Diagnostic Tool". Search Engine Land. Retrieved 2012-09-01.
  3. ^ a b Constantin, Lucian (Dec 2, 2011). "Google Safe Browsing Alerts Network Admins About Malware Distribution Domains". PCWorld.com. Retrieved 2012-09-01.
  4. ^ "Firefox Phishing and Malware Protection". Mozilla Foundation. Retrieved 2012-09-01.
  5. ^ "Phishing and malware detection". Google Inc. Retrieved 2012-09-01.
  6. ^ "Safe Browsing API". Google Inc. Retrieved 2012-09-01.
  7. ^ "Safe Browsing: Protecting more than 3 billion devices worldwide, automatically". The Google Blog. September 2017.
  8. ^ Gerbet, Thomas; Kumar, Amrit; Lauradoux, Cedric (June 2016). "A Privacy Analysis of Google and Yandex Safe Browsing" (PDF). 2016 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN). Toulouse, France: IEEE: 347–358. doi:10.1109/DSN.2016.39. ISBN 978-1-4673-8891-7. S2CID 17276613.
  9. ^ "Developer's Guide (v3)". Google Developers. 18 March 2015.
  10. ^ "Safe Browsing API - Google Developers". Google Developers. 18 March 2015.
  11. ^ Bott, Ed. "Did Google withhold malware protection details from partners?". ZDNet.
  12. ^ "Cookies from Nowhere". Ashkan Soltani.
  13. ^ "Google Chrome Privacy Whitepaper". google.com.
  14. ^ "Apple redirects Google Safe Browsing traffic through its own proxy servers to prevent disclosing users' IP addresses to Google in iOS 14.5". 9 February 2021.
  15. ^ "Google Safe Browsing Makes the Innocent Look Guilty". PCWorld. Archived from the original on 23 June 2021. Retrieved 2018-07-29.
  16. ^ "The New Censorship". 22 June 2016.{{cite web}}: CS1 maint: url-status (link)

External links[edit]