Talk:Google Safe Browsing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Privacy?[edit]

Isn't this an enormous invasion of the user's privacy? I haven't looked into it, but I read this and I'm surprised nothing about privacy is in the article or even on this Talk page... --82.170.113.123 (talk) 23:57, 9 February 2013 (UTC)[reply]

Quotes:

"It's a time capsule on anyone who ever did anything in Chrome or Firefox ... they can be de-anonymized way after the fact, months or years after using those browsers and the settings are turned off," Hansen says.
And the cookie can be used to identify the IP addresses he or she visits, for instance.
"Ultimately, any time they store any kind of information on the browser and echo it back to the Internet, there is a potential leak of user's privacy."
But a Google spokesperson said IP addresses and cookies are not combined with data from other services, nor used for tracking. "All such data is deleted after two weeks" and not anonymized, the spokesperson said.

This article is awfully written. It just doesn't make any sense. There is no risk analysis, nothing. Only a bunch of words. Could as well be the words of a politician!

And yes, we need a section on privacy here. --WPcorrector (talk) 05:34, 16 December 2013 (UTC)[reply]

Section started J05HYYY (talk) 01:50, 13 June 2014 (UTC)[reply]

Thanks for starting this important section. It would be interesting to specify which implementations use the API in such a privacy-invasive way. Mozilla Firefox for instance doesn't seem to tell Google about the visited websites, instead it queries a local database: [1] [2] (I don't know how up to date those articles are, but I still see relevant configuration settings in about:config for Firefox 53.0.3). The option to query Google for every URL was removed in Firefox 3, AFAICT. --Nemo 11:58, 13 July 2017 (UTC)[reply]
There's been some research on the privacy of Safe Browsing independent of Google such as this paper. It would be great if this section drew more on independent research rather than Google's own claims. --Suhacker256 (talk) 18:22, 21 October 2021 (UTC)[reply]

Listing of google.com on Safe Browsing[edit]

Google's own results for google.com and their lack of being therefore listed as suspicious seems, well, suspicious

What is the current listing status for google.com?

   This site is not currently listed as suspicious.
   Part of this site was listed for suspicious activity 20 time(s) over the past 90 days.

What happened when Google visited this site?

   Of the 1389615 pages we tested on the site over the past 90 days, 1198 page(s) resulted in malicious software being downloaded and installed without user consent. The last time Google visited this site was on 2013-11-27, and the last time suspicious content was found on this site was on 2013-11-27.
   Malicious software includes 248 trojan(s), 243 exploit(s), 126 scripting exploit(s). Successful infection resulted in an average of 5 new process(es) on the target machine.
   Malicious software is hosted on 175 domain(s), including earnmoneydo.com/, gilmoregirlspodcast.com/, markforge.biz/.
   121 domain(s) appear to be functioning as intermediaries for distributing malware to visitors of this site, including journaldugeek.com/, x-cornerz.com/, thepullbox.com/.
   This site was hosted on 3 network(s) including AS15169 (GOOGLE), AS43515 (YOUTUBE), AS1221 (TELSTRA).

Has this site acted as an intermediary resulting in further distribution of malware?

   Over the past 90 days, google.com appeared to function as an intermediary for the infection of 61 site(s) including carleton.ca/, realmomkitchen.com/, bit.ly/.

Has this site hosted malware?

   Yes, this site has hosted malicious software over the past 90 days. It infected 33 domain(s), including joomfa.org/, burguscircus.free.fr/, philkearnycwrt.org/.

-- comment of 50.133.134.194 made on article instead of discussion page --WPcorrector (talk) 04:49, 16 December 2013 (UTC)[reply]

Booke site visit[edit]

Booke site visit 1.39.232.39 (talk) 14:02, 11 March 2023 (UTC)[reply]