<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Blog Moved to VPS</title>
	<atom:link href="http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/</link>
	<description>Website insecurity by example</description>
	<lastBuildDate>Sun, 05 Feb 2012 10:06:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Passerby</title>
		<link>http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/comment-page-1/#comment-1549</link>
		<dc:creator>Passerby</dc:creator>
		<pubDate>Tue, 07 Jul 2009 06:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=219#comment-1549</guid>
		<description>Google metrics can go haywire actually

http://www.moon-blog.com/2009/01/google-search-results-in-warning-entire-internet.html

When its large scale it gets detected. For small sites they are indeed unresponsive!</description>
		<content:encoded><![CDATA[<p>Google metrics can go haywire actually</p>
<p><a href="http://www.moon-blog.com/2009/01/google-search-results-in-warning-entire-internet.html" rel="nofollow">http://www.moon-blog.com/2009/01/google-search-results-in-warning-entire-internet.html</a></p>
<p>When its large scale it gets detected. For small sites they are indeed unresponsive!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rohn</title>
		<link>http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/comment-page-1/#comment-1529</link>
		<dc:creator>Rohn</dc:creator>
		<pubDate>Wed, 01 Jul 2009 14:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=219#comment-1529</guid>
		<description>This is to say a Thank you for your communications via email and a small off topic note : how what we think is not always what Google thinks http://mashable.com/2009/06/27/michael-jackson-google/</description>
		<content:encoded><![CDATA[<p>This is to say a Thank you for your communications via email and a small off topic note : how what we think is not always what Google thinks <a href="http://mashable.com/2009/06/27/michael-jackson-google/" rel="nofollow">http://mashable.com/2009/06/27/michael-jackson-google/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rohn</title>
		<link>http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/comment-page-1/#comment-1523</link>
		<dc:creator>Rohn</dc:creator>
		<pubDate>Tue, 30 Jun 2009 00:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=219#comment-1523</guid>
		<description>Thanks for taking time and I understand you  must be very busy at the moment.

What Google does is probably a similar alogarithm like you so that even when things have been cleaned thoroughly or some sub directory pages that were never unclean are also marked by them as malicious. I have read in details how to clear up with Google and made repeated submissions by webmastertools. But Google is NOT responsive.

That apart have you figured out how to separate which  “document.write(unescape(&quot; are bad and which are not bad? As I said encrypting html produces &quot;“document.write(unescape(&quot; which Unmaskparasite marks as suspicious. There are friends and close contacts who do not trust Google or use FF but do visit Unmaskparasite to check sanity of the sites.</description>
		<content:encoded><![CDATA[<p>Thanks for taking time and I understand you  must be very busy at the moment.</p>
<p>What Google does is probably a similar alogarithm like you so that even when things have been cleaned thoroughly or some sub directory pages that were never unclean are also marked by them as malicious. I have read in details how to clear up with Google and made repeated submissions by webmastertools. But Google is NOT responsive.</p>
<p>That apart have you figured out how to separate which  “document.write(unescape(&#8221; are bad and which are not bad? As I said encrypting html produces &#8220;“document.write(unescape(&#8221; which Unmaskparasite marks as suspicious. There are friends and close contacts who do not trust Google or use FF but do visit Unmaskparasite to check sanity of the sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis</title>
		<link>http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/comment-page-1/#comment-1516</link>
		<dc:creator>Denis</dc:creator>
		<pubDate>Sat, 27 Jun 2009 20:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=219#comment-1516</guid>
		<description>Hi Rohn,

Unmask Parasites can&#039;t block anything. It&#039;s an independent service that checks web pages and provides advice to webmasters to look at certain items that may look suspicious. 

If you as a site owner don&#039;t find the highligted items suspicious (it&#039;s your site and you know what should be ther) just ignore the the Unmask Parasites report.

Firefox users cannot view your site because Google has found malicious content on your site (not that encrypted form) and blacklisted your site. This blacklist is used by Firefox, Safari and Google Chrome.

To remove your site from that list you should request a review via Google Webmaster Tools.
http://googlewebmastercentral.blogspot.com/2008/08/hey-google-i-no-longer-have-badware.html</description>
		<content:encoded><![CDATA[<p>Hi Rohn,</p>
<p>Unmask Parasites can&#8217;t block anything. It&#8217;s an independent service that checks web pages and provides advice to webmasters to look at certain items that may look suspicious. </p>
<p>If you as a site owner don&#8217;t find the highligted items suspicious (it&#8217;s your site and you know what should be ther) just ignore the the Unmask Parasites report.</p>
<p>Firefox users cannot view your site because Google has found malicious content on your site (not that encrypted form) and blacklisted your site. This blacklist is used by Firefox, Safari and Google Chrome.</p>
<p>To remove your site from that list you should request a review via Google Webmaster Tools.<br />
<a href="http://googlewebmastercentral.blogspot.com/2008/08/hey-google-i-no-longer-have-badware.html" rel="nofollow">http://googlewebmastercentral.blogspot.com/2008/08/hey-google-i-no-longer-have-badware.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rohn</title>
		<link>http://blog.unmaskparasites.com/2009/06/06/blog-moved-to-vps/comment-page-1/#comment-1510</link>
		<dc:creator>Rohn</dc:creator>
		<pubDate>Sat, 27 Jun 2009 05:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=219#comment-1510</guid>
		<description>I am not sure where to report this - probably a forum here will be great. I sent you email already but just to make a prominent note :

Many pages, which were cleaned or are never infected, when checked by unmaskparasite gives erroneous result BLOCKING Firefox users driving them away from our site - this happens when the words &quot;document.write(unescape(...&quot; are there, even for valid reasons and in a clean way for useful means.

I used http://dynamicdrive.com/dynamicindex9/encrypter.htm to hide certain html from view source to prevent copying. Now those are being reported as suspicious code.

Can unmaskparasite immediately explore this, add patches to its code and rectify the situation ?</description>
		<content:encoded><![CDATA[<p>I am not sure where to report this &#8211; probably a forum here will be great. I sent you email already but just to make a prominent note :</p>
<p>Many pages, which were cleaned or are never infected, when checked by unmaskparasite gives erroneous result BLOCKING Firefox users driving them away from our site &#8211; this happens when the words &#8220;document.write(unescape(&#8230;&#8221; are there, even for valid reasons and in a clean way for useful means.</p>
<p>I used <a href="http://dynamicdrive.com/dynamicindex9/encrypter.htm" rel="nofollow">http://dynamicdrive.com/dynamicindex9/encrypter.htm</a> to hide certain html from view source to prevent copying. Now those are being reported as suspicious code.</p>
<p>Can unmaskparasite immediately explore this, add patches to its code and rectify the situation ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

