<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>searchengineland.com &#187; Google: Security</title>
	<atom:link href="http://searchengineland.com/library/google/google-security/feed" rel="self" type="application/rss+xml" />
	<link>http://searchengineland.com</link>
	<description>Search Engine Land: Must Read News About Search Marketing &#38; Search Engines</description>
	<lastBuildDate>Sun, 22 Nov 2009 16:39:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How To Avoid Getting Your Search Rankings Trashed By Malware</title>
		<link>http://searchengineland.com/how-to-avoid-getting-your-search-rankings-trashed-by-malware-25199</link>
		<comments>http://searchengineland.com/how-to-avoid-getting-your-search-rankings-trashed-by-malware-25199#comments</comments>
		<pubDate>Fri, 04 Sep 2009 21:25:50 +0000</pubDate>
		<dc:creator>Jonathan Hochman</dc:creator>
				<category><![CDATA[Google: Security]]></category>
		<category><![CDATA[How To: SEO]]></category>
		<category><![CDATA[Search Features: Safety]]></category>

		<guid isPermaLink="false">http://searchengineland.com/?p=25199</guid>
		<description><![CDATA[As if SEOs don’t have enough things to worry about already, add malware to the list. Why does malware matter to SEOs? If the site you are working on gets infected, its search traffic will plummet. Search engines attempt to remove infected pages from their search results, or they label them with an ominous warning, [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fhow-to-avoid-getting-your-search-rankings-trashed-by-malware-25199"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fhow-to-avoid-getting-your-search-rankings-trashed-by-malware-25199" height="61" width="51" /></a></div><p>As if SEOs don’t have enough things to worry about already, add malware to the list. Why does malware matter to SEOs? If the site you are working on gets infected, its search traffic will plummet. Search engines attempt to remove infected pages from their search results, or they label them with an ominous warning, such as <em>This site may damage your computer</em>. </p>
<p>Back in 2008 <a href="http://googleonlinesecurity.blogspot.com/2008/02/all-your-iframe-are-point-to-us.html">Google reported</a> that malware infected pages had increased to more than 1% of all search results. Google posted a <a href="http://googleonlinesecurity.blogspot.com/2009/08/malware-statistics-update.html">malware statistics update</a> last week.  Malware infections have more than doubled since April 2009. Search results containing a url labeled as harmful have remained level in the range of 0.5% to 0.9%, an improvement. While the web as a whole has become more dangerous, Google’s been doing an even better job clearing their search results.</p>
<p>I know one reason why there’s been a dramatic rise in malware on the Web since April. A <a href="http://www.internetevolution.com/author.asp?section_id=732&amp;doc_id=180663&amp;">nasty malware attack</a> has been targeting web developers to steal their passwords. Stolen passwords are used by the bad guys to automatically deploy iframe injection attacks to innocent web page.</p>
<p>If you access web sites via File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP), this attack is targeting you. All you need to do is browse an infected page using an insecure browser. Badware will be deployed to your machine, and it will find the files used by FileZilla, or possibly other FTP programs to store passwords, and silently send those files back to a server in China. Then an automated bot attack will use FTP to edit your web pages, infecting them with malware. Then your sites will drop out of the search results. Can you image the uncomfortable conversations when all your sites get hacked at once and you have to admit responsibility?</p>
<p>What can be done to reduce this risk of search Armageddon?  </p>
<ol>
<li>Use a more secure browser such as <a href="http://www.google.com/chrome">Chrome</a> or Firefox with the <a href="http://noscript.net/">NoScript</a> add on for routine browsing.</li>
<li>Don’t use any FTP program that stores passwords locally in <a href="http://en.wikipedia.org/wiki/Plaintext">plaintext</a>, such as FileZilla. To date, Dreamweaver has not been reported to have been compromised. Dreamweaver encrypts passwords and stores them in the Windows registry.</li>
<li>Consider using a Mac or Linux instead of Windows. As the most popular operating system, Windows is the most popular target for attacks.</li>
<li>Make sure your machine and server are fully updated and patched. Turn off unnecessary services and software to reduce the <a href="http://en.wikipedia.org/wiki/Attack_surface">attack surface</a>.</li>
<li>Register your site with <a href="https://www.google.com/webmasters/tools/home?hl=en">Google Webmaster Tools</a> and <a href="http://www.bing.com/webmaster">Bing Webmaster Center</a>. Check regularly to see if there are any malware reports (or other issues) with your sites.</li>
<li>If you suspect a malware infection, check <a href="http://www.unmaskparasites.com/">Unmask Parasites</a>,</li>
<li>View <a href="http://www.siteadvisor.com/sites/searchengineland.com">your site’s reputation</a> at McAfee SiteAdvisor.</li>
<li>Reduce the number of people and computers that have access to your web server.</li>
<li>Keep a backup copy of your web pages. In case of infection, it’s a race to see if you can fix the site before search engines (and users) discover the problem and dump you.</li>
<li> Choose the hosting provider that has the quickest response time, not the cheapest price. If your site gets hacked, you may need their help to change all the passwords.</li>
</ol>
<p>As the web becomes more dangerous, customers become more suspicious, reducing opportunities for everyone. Please do your part to make the web safer, and to reduce your risks.</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/how-to-avoid-getting-your-search-rankings-trashed-by-malware-25199/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Working On New File System</title>
		<link>http://searchengineland.com/googles-working-on-new-file-system-23868</link>
		<comments>http://searchengineland.com/googles-working-on-new-file-system-23868#comments</comments>
		<pubDate>Wed, 12 Aug 2009 13:09:08 +0000</pubDate>
		<dc:creator>Barry Schwartz</dc:creator>
				<category><![CDATA[Google: Business Issues]]></category>
		<category><![CDATA[Google: General]]></category>
		<category><![CDATA[Google: Security]]></category>
		<category><![CDATA[Top News]]></category>

		<guid isPermaLink="false">http://searchengineland.com/?p=23868</guid>
		<description><![CDATA[We often don&#8217;t think about the core file system and servers that power Google&#8217;s properties, from Search and Gmail to YouTube and Wave, but Google does.  The Register reports that after ten years with the original Google File System, GFS for short, Google is working on a version two to replace it.  The [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fgoogles-working-on-new-file-system-23868"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fgoogles-working-on-new-file-system-23868" height="61" width="51" /></a></div><p>We often don&#8217;t think about the core file system and servers that power Google&#8217;s properties, from Search and Gmail to YouTube and Wave, but Google does.  The Register <a href="http://www.theregister.co.uk/2009/08/12/google_file_system_part_deux/">reports</a> that after ten years with the original Google File System, GFS for short, Google is working on a version two to replace it.  The Google File System is different from the underlining <a href="http://searchengineland.com/caffeine-googles-new-search-index-23823">Caffeine infrastructure</a> update, as I understand it, Caffeine runs on top of the Google File System, like you run Microsoft Word on Windows.</p>
<p>The original GFS wasn&#8217;t built to handle applications such as Gmail or YouTube, but that is exactly what it has been powering for the past couple years.  It was originally designed to be the platform to power search queries and is now being asked to do a lot more. Version two, will take this into account.  The release date is unknown, but The Register goes through all the <A href="http://www.theregister.co.uk/2009/08/12/google_file_system_part_deux/">technical details</a> that would make any system administrator raise their eye brows.  Personally, I don&#8217;t fully grasp these details, but conceptually, it make sense.</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/googles-working-on-new-file-system-23868/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Bogus Google Give-Away</title>
		<link>http://searchengineland.com/the-bogus-google-give-away-21656</link>
		<comments>http://searchengineland.com/the-bogus-google-give-away-21656#comments</comments>
		<pubDate>Sat, 27 Jun 2009 18:21:18 +0000</pubDate>
		<dc:creator>Danny Sullivan</dc:creator>
				<category><![CDATA[Google: Security]]></category>

		<guid isPermaLink="false">http://searchengineland.com/?p=21656</guid>
		<description><![CDATA[Here&#8217;s a new one on me. I just got an email telling me that I&#8217;ve won nearly $1 million from a &#8220;drawing&#8221; randomly selected from those searching on Google. Suffice to say, it&#8217;s a scam. I can assure you that Google&#8217;s done no drawing like this. Add the spam to those about missing fortunes in [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fthe-bogus-google-give-away-21656"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fthe-bogus-google-give-away-21656" height="61" width="51" /></a></div><p>Here&#8217;s a new one on me. I just got an email telling me that I&#8217;ve won nearly $1 million from a &#8220;drawing&#8221; randomly selected from those searching on Google. Suffice to say, it&#8217;s a scam. I can assure you that Google&#8217;s done no drawing like this. Add the spam <a href="http://daggle.com/spam-filter-ate-my-legit-offer-677">to those</a> about missing fortunes in Nigeria or government grants.</p>
<p>I did some looking around, and the Google scam seems relatively recent. Apparently<a href="http://www.svbizlaw.com/lottery.googleanniversarygiveaway.htm"> there was</a> a Google &#8220;anniversary&#8221; scam in April 2008. For this latest &#8220;give-away&#8221; one, I <a href="http://www.google.com/support/forum/p/AppSecurity/thread?tid=34ddfa90739a1f74&amp;hl=en">spotted</a> talk of it from April of this year. But since this particular spam made it past the filters in Gmail (but not past Outlooks spam filtering), perhaps more people will be exposed to it.</p>
<p>For the curious, the pitch:</p>
<blockquote><p><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:DoNotOptimizeForBrowser /> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val=" " /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--> GOOGLE GIVE-AWAY WINNING NOTIFICATION!!!
This E-mail is to inform you that your e-mail emerged as a winner of £500,000.00 GBP (Five Hundred Thousand British Pounds) in our online Give-away draws. Over £20,000,000.00 (Twenty Million British pounds) is to be given out for this Draws. No purchases of  tickets were required. Participants for the draws were randomly selected from a world wide range of web searchers who use the Google search engine
(Googler) and other Google ancillary services. Google is now the biggest search engine worldwide and in an effort to make sure that it remains the most widely used search engine, Google is running an e-mail beta test.</p>
<p>Your email address was linked with our Computer Generated Profile Numbers(CGPN) and attached to the following details:  Computer Generated Profile Numbers (CGPN):7-22-71-00-66-12, Ticket number:
00869575733664, Serial numbers:/BTD/8070447706/06, Lucky numbers:  12-12-23-35-40-41(12), was picked among our lucky winners to receive £500, 000.00 British pounds. Winners were selected randomly through a computer ballot system from worldwide users of the Google search engine.</p>
<p>YOUR WINNING DETAILS ARE AS FOLLOW:
Computer Generated Profile Numbers (CGPN):7-22-71-00-66-12 Ticket number: 00869575733664 Serial numbers: / BTD/8070447706/06 Lucky numbers: 12-12-23-35-40-41(12)</p>
<p>To claim your give-away prize, send the following. Your full names&#8230;&#8230;&#8230;&#8230;&#8230;.. , sex&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.,Location&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.Alternate e-mail address&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;Your winning details&#8230;&#8230;&#8230;&#8230;&#8230;..</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/the-bogus-google-give-away-21656/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Russian Roulette: McAfee Details Web&#8217;s Riskiest Search Terms</title>
		<link>http://searchengineland.com/russian-roulette-webs-riskiest-search-terms-20742</link>
		<comments>http://searchengineland.com/russian-roulette-webs-riskiest-search-terms-20742#comments</comments>
		<pubDate>Tue, 09 Jun 2009 19:05:52 +0000</pubDate>
		<dc:creator>Matt McGee</dc:creator>
				<category><![CDATA[Ask: Web Search]]></category>
		<category><![CDATA[Google: Security]]></category>
		<category><![CDATA[Google: Web Search]]></category>
		<category><![CDATA[Microsoft: Bing]]></category>
		<category><![CDATA[SEO: Spamming]]></category>
		<category><![CDATA[Stats: General]]></category>
		<category><![CDATA[Top News]]></category>
		<category><![CDATA[Yahoo: Search]]></category>

		<guid isPermaLink="false">http://searchengineland.com/?p=20742</guid>
		<description><![CDATA[Somewhere online right now there&#8217;s a music fan who&#8217;s big on free downloads, likes Coldplay&#8217;s &#8220;Viva La Vida&#8221; but doesn&#8217;t know the lyrics, is looking for free ringtones, uses MySpace, likes to play solitaire and wants the latest game cheats. Like many of us, s/he uses a search engine to find all of these things.
This [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Frussian-roulette-webs-riskiest-search-terms-20742"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Frussian-roulette-webs-riskiest-search-terms-20742" height="61" width="51" /></a></div><p>Somewhere online right now there&#8217;s a music fan who&#8217;s big on free downloads, likes Coldplay&#8217;s &#8220;Viva La Vida&#8221; but doesn&#8217;t know the lyrics, is looking for free ringtones, uses MySpace, likes to play solitaire and wants the latest game cheats. Like many of us, s/he uses a search engine to find all of these things.</p>
<p>This person may as well be playing Russian roulette. </p>
<p>In a <a href="http://us.mcafee.com/en-us/local/docs/most_dangerous_searchterm_us.pdf">recent report (PDF)</a>, online security company McAfee says those are some of the most dangerous search terms on the web. </p>
<p><img src="http://searchengineland.com/figz/wp-content/seloads/2009/06/risky.gif" alt="risky" title="risky" width="540" height="250" /></p>
<p>That&#8217;s just a sample of the report&#8217;s list of the 50 riskiest search terms in the U.S. &#8220;Maximum Risk&#8221; describes the percentage of pages on a single search results page that were dangerous; i.e., on a search for &#8220;lyrics,&#8221; there was one search results page on which 50% of the ranked pages were risky. &#8220;Average Risk&#8221; is the overall risk from all five pages of search results for each term.</p>
<p>McAfee analyzed the first five search results pages of 2,600 popular keywords across five search engines: Google, Yahoo, Live, AOL, and Ask. They analyzed both organic and paid listings and counted the number of links that led to pages that McAfee&#8217;s <a href="http://www.siteadvisor.com/">SiteAdvisor</a> tool flagged as dangerous. The study ultimately reviewed more than 413,000 unique URLs. </p>
<p>McAfee&#8217;s study also found that certain categories of keywords were more riskier than others. Searches related to &#8220;lyrics&#8221; and &#8220;free&#8221; had both the highest average risk and highest maximum risk.</p>
<p><img src="http://searchengineland.com/figz/wp-content/seloads/2009/06/lyrics.gif" alt="lyrics" title="lyrics" width="540" height="276" /></p>
<p><img src="http://searchengineland.com/figz/wp-content/seloads/2009/06/free.gif" alt="free" title="free" width="540" height="278" /></p>
<p>It should be no surprise that McAfee also found scammers like to look at popular trends when choosing what keywords to target. Here&#8217;s a chart showing some of the riskiest terms related to the economic crisis:</p>
<p><img src="http://searchengineland.com/figz/wp-content/seloads/2009/06/crisis.gif" alt="crisis" title="crisis" width="540" height="294" /></p>
<p>The report also has charts detailing the most dangerous search terms in other U.S categories, as well as several other countries including Canada, France, Italy, Spain, Germany, and others. Here&#8217;s the <a href="http://us.mcafee.com/en-us/local/docs/most_dangerous_searchterm_us.pdf">PDF download link (2.2mb)</a> if you&#8217;re interested in more details. </p>
<p>To some degree, the McAfee report calls into question how well the search engines themselves do at notifying users of risky sites. Yahoo uses <a href="http://searchengineland.com/yahoo-adds-searchscan-alerts-to-risky-search-results-13931">McAfee&#8217;s SearchScan</a>, Ask uses <a href="http://searchengineland.com/askcom-symantec-partner-to-detect-malicious-sites-16408">Symantec</a>, while <s>Live Search</s> <a href="http://searchengineland.com/live-search-adds-malware-warnings-15695">Bing</a> and <a href="http://searchengineland.com/google-search-results-now-may-display-malware-warnings-10502">Google</a> have their own malware detection tools. But, on a purely anecdotal level, if you search for the terms listed in the McAfee report, Google, Yahoo, and Bing show very few warnings in the first five pages of results. </p>
<p>(found via <a href="http://lifehacker.com/5284540/the-webs-most-dangerous-search-terms">Lifehacker</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/russian-roulette-webs-riskiest-search-terms-20742/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hackers Take Control Of Google Morocco For Several Hours</title>
		<link>http://searchengineland.com/hackers-take-control-of-google-morocco-for-several-hours-18943</link>
		<comments>http://searchengineland.com/hackers-take-control-of-google-morocco-for-several-hours-18943#comments</comments>
		<pubDate>Mon, 11 May 2009 12:46:57 +0000</pubDate>
		<dc:creator>Barry Schwartz</dc:creator>
				<category><![CDATA[Google: Security]]></category>

		<guid isPermaLink="false">http://searchengineland.com/?p=18943</guid>
		<description><![CDATA[TechCrunch reported that Google Morocco was taken over by hackers for several hours.
The reports say that the hackers gained access to Google&#8217;s domain name through the country&#8217;s registrar, NIC.ma.  The DNS information was then changed to point to a different server until Google regained access and pointed the domain name back to the Google [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fhackers-take-control-of-google-morocco-for-several-hours-18943"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fhackers-take-control-of-google-morocco-for-several-hours-18943" height="61" width="51" /></a></div><p>TechCrunch <a href="http://www.techcrunch.com/2009/05/09/hackers-temporarily-seize-control-of-google-morocco-domain-name/">reported</a> that <a href="http://www.google.co.ma/">Google Morocco</a> was taken over by hackers for several hours.</p>
<p>The reports say that the hackers gained access to Google&#8217;s domain name through the country&#8217;s registrar, <a href="http://www.nic.ma/">NIC.ma</a>.  The DNS information was then changed to point to a different server until Google regained access and pointed the domain name back to the Google servers.</p>
<p>Google has been <a href="http://searchengineland.com/google-security-google-mac-blog-hacked-google-calendar-users-not-being-safe-11031">hacked before</a>, including domain names taken over and blogs hacked into and seized. </p>
<p>Postscript: Google <a href="http://www.informationweek.com/news/internet/google/showArticle.jhtml?articleID=217400310">said</a> this was not a &#8220;hack&#8221; of the Google web site.  Right, Google technically was not hacked into, but their domain name was taken control over and redirected.</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/hackers-take-control-of-google-morocco-for-several-hours-18943/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Suggests Ways To Prevent Hacking</title>
		<link>http://searchengineland.com/google-suggests-ways-to-prevent-hacking-16639</link>
		<comments>http://searchengineland.com/google-suggests-ways-to-prevent-hacking-16639#comments</comments>
		<pubDate>Fri, 20 Feb 2009 18:01:15 +0000</pubDate>
		<dc:creator>Matt McGee</dc:creator>
				<category><![CDATA[Google: Security]]></category>
		<category><![CDATA[Google: Webmaster Central]]></category>
		<category><![CDATA[SEO: Spamming]]></category>

		<guid isPermaLink="false">http://searchengineland.com/?p=16639</guid>
		<description><![CDATA[If you run a popular/successful blog, there&#8217;s a pretty good chance you&#8217;re plenty familiar with hacking and how to deal with it. But hacking comes in many forms and can hit any kind of web site that isn&#8217;t secure. 
In a post today, Google&#8217;s Webmaster Central blog talks about ways to prevent hacking, including using [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fgoogle-suggests-ways-to-prevent-hacking-16639"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fgoogle-suggests-ways-to-prevent-hacking-16639" height="61" width="51" /></a></div><p>If you run a popular/successful blog, there&#8217;s a pretty good chance you&#8217;re plenty familiar with hacking and how to deal with it. But hacking comes in many forms and can hit any kind of web site that isn&#8217;t secure. </p>
<p>In a <a href="http://googlewebmastercentral.blogspot.com/2009/02/best-practices-against-hacking.html">post today</a>, Google&#8217;s Webmaster Central blog talks about ways to prevent hacking, including using Google search to find out if you&#8217;ve been hacked. The <em>site:</em> command can help identify if a hacker has added common spam content to your site when you do a search like</p>
<p><em>site:searchengineland.com viagra</em></p>
<p>Most webmasters are probably familiar with and use the <em>site:</em> command often. But Google also suggests something many probably aren&#8217;t doing, i.e., using Google Alerts to monitor spammy words and phrases:</p>
<blockquote><p>&#8220;In order to constantly keep an eye on the presence of suspicious keywords on your website, you could also use Google Alerts to monitor queries like:</p>
<p>site:example.com viagra OR casino OR porn OR ringtones</p>
<p>You will receive an email alert whenever these keywords are found in the content of your site.&#8221;</p></blockquote>
<p>Finally, Google suggests using Webmaster Tools to help prevent and identify hacking, too. The &#8220;Top Search Queries&#8221; panel may show if any pages on your site are ranking for unrelated, spammy words or phrases. And Webmaster Tools is also where you&#8217;ll want to submit a reconsideration request if you were hacked and removed from Google&#8217;s index.</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/google-suggests-ways-to-prevent-hacking-16639/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Blogger Makes Up 2% Of All Malware Hosts</title>
		<link>http://searchengineland.com/googles-blogger-makes-up-2-of-all-malware-hosts-14440</link>
		<comments>http://searchengineland.com/googles-blogger-makes-up-2-of-all-malware-hosts-14440#comments</comments>
		<pubDate>Thu, 24 Jul 2008 13:01:57 +0000</pubDate>
		<dc:creator>Barry Schwartz</dc:creator>
				<category><![CDATA[Google: Blogger]]></category>
		<category><![CDATA[Google: Security]]></category>
		<category><![CDATA[Legal: Security]]></category>

		<guid isPermaLink="false">http://searchengineland.com/beta/googles-blogger-makes-up-2-of-all-malware-hosts-14440.php</guid>
		<description><![CDATA[
]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fgoogles-blogger-makes-up-2-of-all-malware-hosts-14440"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fgoogles-blogger-makes-up-2-of-all-malware-hosts-14440" height="61" width="51" /></a></div><p><a href="http://news.cnet.com/8301-1009_3-9997978-83.html">Blogspot.com cited as the No. 1 host for malware</a> from News.com reports Google&#8217;s Blogger accounts &#8220;for nearly 2 percent of all malware hosts.&#8221;  Sophos, an antivirus vendor, <a href="http://www.sophos.com/pressoffice/news/articles/2008/07/security-report.html">published</a> a report showing the state of malware injections and attacks throughout the web.</p>
<p>Specifically, hackers can set up &#8220;malicious blogs&#8221; on the Blogger service, plus they can inject dangerous web links and content into Blogger blogs.</p>
<p><span id="more-14440"></span>
The Google web search team takes malware attacks seriously.  They have <a href="http://searchengineland.com/070814-083602.php">reviews in webmaster tools</a> and they <a href="http://searchengineland.com/070213-085816.php">label</a> malicious web sites in web search results.  So isn&#8217;t it ironic that Google hosts the number one problem of malware on the Internet?</p>
<p>Yesterday, I <a href="http://searchengineland.com/080723-111732.php">said</a> that we had reports of <a href="http://www.labnol.org/internet/search/internet-drug-scams-on-google-sites/3953/">spam</a> on Google Sites, as well as spam on Google Groups.  But this report shows that Google&#8217;s Blogger is worse than both of those.</p>
<p>A Google spokesperson gave News.com a statement:</p>
<blockquote><p>Google takes the security of our users very seriously, and we work hard to protect them from malware. Using Blogger, or any Google product, to serve or host malware is a violation of our product policies. We actively work to detect and remove sites that serve malware from our network.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/googles-blogger-makes-up-2-of-all-malware-hosts-14440/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Safe Browsing Diagnostic Tool</title>
		<link>http://searchengineland.com/googles-safe-browsing-diagnostic-tool-14064</link>
		<comments>http://searchengineland.com/googles-safe-browsing-diagnostic-tool-14064#comments</comments>
		<pubDate>Fri, 23 May 2008 11:59:27 +0000</pubDate>
		<dc:creator>Barry Schwartz</dc:creator>
				<category><![CDATA[Google: SEO]]></category>
		<category><![CDATA[Google: Security]]></category>

		<guid isPermaLink="false">http://searchengineland.com/beta/googles-safe-browsing-diagnostic-tool-14064.php</guid>
		<description><![CDATA[A week ago Google announced the release of a safe browsing diagnostic tool.  To use the tool, just append a URL to the end of http://www.google.com/safebrowsing/diagnostic?site=.
For example, to test this site, you would enter http://www.google.com/safebrowsing/diagnostic?site=http://searchengineland.com/.  Google will then return four sets of security information about that page.

(1) The current listing status of a [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fgoogles-safe-browsing-diagnostic-tool-14064"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fgoogles-safe-browsing-diagnostic-tool-14064" height="61" width="51" /></a></div><p>A week ago Google <a href="http://googleonlinesecurity.blogspot.com/2008/05/safe-browsing-diagnostic-to-rescue.html">announced</a> the release of a safe browsing diagnostic tool.  To use the tool, just append a URL to the end of http://www.google.com/safebrowsing/diagnostic?site=.</p>
<p>For example, to test this site, you would enter <a href="http://www.google.com/safebrowsing/diagnostic?site=http://searchengineland.com/">http://www.google.com/safebrowsing/diagnostic?site=http://searchengineland.com/</a>.  Google will then return four sets of security information about that page.</p>
<p><span id="more-14064"></span>
(1) The current listing status of a site and also information on how often a site or parts of it were listed in the past.
(2) The last time Google analyzed the page, when it was last malicious, what kind of malware Google encountered and so fourth.
(3) Did the site facilitated the distribution of malicious software in the past?
(4) Also, has the site has hosted malicious software in the past?</p>
<p>Google has shown an example of a site that has malicious results.  To see such results, go <a href="http://www.google.com/safebrowsing/diagnostic?site=http://malware.testing.google.test/testing/malware/">over here</a>, it is safe to click the link.  If you do not want to click the link, I have provided a full screen capture below.</p>
<p><a title="Google Safe Browsing diagnostic page for malware.testing.google.test-testing-malware- (20080523) by rustybrick, on Flickr" href="http://www.flickr.com/photos/rustybrick/2515379153/"><img src="http://farm4.static.flickr.com/3018/2515379153_d65589f87a.jpg" alt="Google Safe Browsing diagnostic page for malware.testing.google.test-testing-malware- (20080523)" width="500" height="396" /></a></p>
<p>The Zero Day blog has some <a href="http://blogs.zdnet.com/security/?p=1170">additional</a> information on this Google security release.</p>
<p><strong>NOTE:</strong> If you saw a malware warning on Jan. 31, 2009, this was due to an error that briefly impacted all web sites. See <a href="../../google-gets-fearful-flags-entire-internet-as-malware-briefly-16387">Google Gets Fearful, Flags Entire Internet As Malware Briefly</a>, for more.</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/googles-safe-browsing-diagnostic-tool-14064/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Oops! Google&#8217;s SSL Certificate Throwing Out Scary Warnings</title>
		<link>http://searchengineland.com/oops-googles-ssl-certificate-throwing-out-scary-warnings-13521</link>
		<comments>http://searchengineland.com/oops-googles-ssl-certificate-throwing-out-scary-warnings-13521#comments</comments>
		<pubDate>Wed, 05 Mar 2008 20:49:18 +0000</pubDate>
		<dc:creator>Barry Schwartz</dc:creator>
				<category><![CDATA[Google: Security]]></category>

		<guid isPermaLink="false">http://searchengineland.com/beta/oops-googles-ssl-certificate-throwing-out-scary-warnings-13521.php</guid>
		<description><![CDATA[
]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Foops-googles-ssl-certificate-throwing-out-scary-warnings-13521"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Foops-googles-ssl-certificate-throwing-out-scary-warnings-13521" height="61" width="51" /></a></div><p>Everyone is noticing that when they go to their <a href="https://google.com/accounts/">Google Account</A> through AdWords, AdSense, Analytics, or any Google page that requires SSL, they are being prompted with a security warning.  Typically, its not a major deal, right?</p>
<p>Well, not if you are trying to get customers to buy on your site.  As Tim Gross <a href="http://www.timgross.com/128-google-certificate-expired-everyone-makes-mistakes.html">explains</a>, if you are using Google Checkout on your site, this is having a major impact.  Not only that, if you are using the conversion tracking scripts for AdWords and your potential buyer clicked on your ad, they may be prompted with a security warning and leave your site.  There goes your sale, and you paid for that.</p>
<p><span id="more-13521"></span>
Here is a screen shot of the security warning on Safari. You will get a similar one on any other browser:</p>
<p><a href="http://www.flickr.com/photos/rustybrick/2313383714/" title="Google Secure Cert Expired by rustybrick, on Flickr"><img src="http://farm4.static.flickr.com/3068/2313383714_da5fccbab8.jpg" width="500" height="366" alt="Google Secure Cert Expired" /></a></p>
<p>This happens way too often, simply because it is an easy thing to forget. Late January, <A href="http://www.seroundtable.com/archives/016123.html">Yahoo forgot to renew their SSL certificate</a> for the publisher network.</p>
<p>Tim Gross&#8217;s screenshot shows a similar expiration date issue that is impacting the www.googleadservices.com URL.</p>
<p>Aside from that, our screenshot above shows a different error, because the certificate is for a slightly different domain than what it was issued for (see comments below for more about this; initially we wrote it was solely an expiration issue).</p>
<p><strong>Postscript</strong>: Google <a href="http://adwords.blogspot.com/2008/03/conversion-tracking-issue-on-march-6.html">updates</a> us that this was an issue between 9am and 2pm (PST) time, where &#8220;some web pages containing the AdWords Conversion Tracking code snippet presented visitors with a browser message indicating a Google server certificate had expired.&#8221;  Google also adds that the conversion tracking numbers may have been underreported.  You may want to call your Google AdWords representative if you use conversion tracking and see if some type of discount will be applied to your account for possibly wasted clicks.</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/oops-googles-ssl-certificate-throwing-out-scary-warnings-13521/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Study: 1.3% Google Searches Return At Least One Malicious Result</title>
		<link>http://searchengineland.com/google-study-13-google-searches-return-at-least-one-malicious-result-13358</link>
		<comments>http://searchengineland.com/google-study-13-google-searches-return-at-least-one-malicious-result-13358#comments</comments>
		<pubDate>Wed, 13 Feb 2008 13:01:26 +0000</pubDate>
		<dc:creator>Barry Schwartz</dc:creator>
				<category><![CDATA[Google: AdWords]]></category>
		<category><![CDATA[Google: Security]]></category>
		<category><![CDATA[Google: Web Search]]></category>
		<category><![CDATA[Legal: Security]]></category>
		<category><![CDATA[Search Ads: General]]></category>

		<guid isPermaLink="false">http://searchengineland.com/beta/google-study-13-google-searches-return-at-least-one-malicious-result-13358.php</guid>
		<description><![CDATA[
]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fsearchengineland.com%2Fgoogle-study-13-google-searches-return-at-least-one-malicious-result-13358"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fsearchengineland.com%2Fgoogle-study-13-google-searches-return-at-least-one-malicious-result-13358" height="61" width="51" /></a></div><p><a href="http://www.informationweek.com/news/showArticle.jhtml?articleID=206501894">Web Browsing, Search, And Online Ads Grow More Risky, Google Says</a> from InformationWeek reports on a recent Google Study named <a href="http://googleonlinesecurity.blogspot.com/2008/02/all-your-iframe-are-point-to-us.html">All Your iFRAMEs Point to Us</a> that shows 1.3% of Google searches returned at least one malicious result.</p>
<p>Niels Provos, a security engineer at Google, lead the study that took 10 months of data containing billions of URLs.  The data collection period was between January 2007 and October 2007.  They checked 66,534,330 URLs and found that 3,385,889 URLs were &#8220;suspicious&#8221; and 3,417,590 URLs were malicious, pointing to 181,699 landing sites.</p>
<p><span id="more-13358"></span>
But the real impact to the end user, as described by the study, showed that a search query at Google returned &#8220;at least one malicious result, with an average approaching 1.3% of the overall incoming search queries.&#8221;  Furthermore, of the top one-million URLs appearing in the search engine results, &#8220;about 6,000 belong to sites that have been verified as malicious at some point during our data collection.&#8221;  Here is the kicker: &#8220;about 0.6% of the top million URLs that appeared most frequently in Google’s search results led to exposure to malicious activity at some point.&#8221;</p>
<p>Where does the malware originate from?  Here is a chart from the study on that question:</p>
<p><a href="http://www.flickr.com/photos/rustybrick/2262994804/" title="Geographic locality of malware by rustybrick, on Flickr"><img src="http://farm3.static.flickr.com/2062/2262994804_df38689228.jpg" width="500" height="187" alt="Geographic locality of malware" /></a></p>
<p>Many of the malware stems from ads.  The study showed that &#8220;on average, 2% of the landing sites were delivering malware via advertisements.&#8221;  But when you look at the searchers perspective, &#8220;12% of the overall search results that returned landing pages were associated with malicious content due to unsafe Ads.&#8221;</p>
<p>There is some excellent data on search and malware in this <a href="http://research.google.com/archive/provos-2008a.pdf">Google report</a> (PDF file).</p>
]]></content:encoded>
			<wfw:commentRss>http://searchengineland.com/google-study-13-google-searches-return-at-least-one-malicious-result-13358/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
