<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Dealing With Those Pesky Narks</title>
	<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/</link>
	<description>Advanced SEO Tactics and Techniques</description>
	<pubDate>Thu, 24 Jul 2008 16:14:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Palm Coast Coupons</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-225123</link>
		<pubDate>Wed, 30 Apr 2008 05:44:14 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-225123</guid>
					<description>i love the idea of your own hosting company to get your own complaints... brilliant</description>
		<content:encoded><![CDATA[<p>i love the idea of your own hosting company to get your own complaints&#8230; brilliant
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: oleg seo</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-222530</link>
		<pubDate>Wed, 16 Apr 2008 13:30:24 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-222530</guid>
					<description>as always great post.. keep it up... digg... lol</description>
		<content:encoded><![CDATA[<p>as always great post.. keep it up&#8230; digg&#8230; lol
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Who</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-219397</link>
		<pubDate>Thu, 03 Apr 2008 23:10:00 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-219397</guid>
					<description>I would suggest some chinese based server providers such as: http://www.7x24.cn/english/en-dedicated.htm or any other.

These chinese people really don't care about spam complaints.</description>
		<content:encoded><![CDATA[<p>I would suggest some chinese based server providers such as: <a href="http://www.7&#215;24.cn/english/en-dedicated.htm" rel="nofollow">http://www.7&#215;24.cn/english/en-dedicated.htm</a> or any other.</p>
<p>These chinese people really don&#8217;t care about spam complaints.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: david deangelo</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-203320</link>
		<pubDate>Fri, 01 Feb 2008 12:42:06 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-203320</guid>
					<description>Very crafty indeed.</description>
		<content:encoded><![CDATA[<p>Very crafty indeed.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: latecoe</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-162719</link>
		<pubDate>Sat, 29 Sep 2007 00:24:52 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-162719</guid>
					<description>Is there any way to mask affiliate links from affiliate network?</description>
		<content:encoded><![CDATA[<p>Is there any way to mask affiliate links from affiliate network?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-10268</link>
		<pubDate>Fri, 12 Jan 2007 18:30:22 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-10268</guid>
					<description>Excellent Comment!

Thanks for dropping that by us.
To answer your questions
&lt;strong&gt;&lt;em&gt;Now do you think …
1) the owner of the shared hosting server will want to risk getting the whole server disconnected?&lt;/em&gt;&lt;/strong&gt;
&lt;strong&gt; 2) most tech bloggers really do not know how to do an IPWHOIS lookup ?&lt;/strong&gt;
Absolutely not. Shared hosts would gladly drop a client to save the server and to save face with the datacenter. Its just common sense business. Thats why spammers consider it vital to prevent as many complaints to their host and their hosts datacenter as possible. Spam profits come from two factors, &lt;strong&gt;Flow&lt;/strong&gt; and &lt;strong&gt;Lifespan&lt;/strong&gt;. Flow is how much consistant money the spam is making over a given period of time. The lifespan is how long the spam will continue making money before it gets shut down. Increasing any of the two factors decreases the potential of profit loss on a spam project. If you can't be bulletproof than you are forced to deal with percentages. If its inescapable that the project will die after 7 days than you have no choice but to attempt to increase the flow percentages per site to increase profits. Likewise if you're dealing with a fixed flow than you have no choice but to do everything possible to increase your lifespan. Only a certain percentage of tech bloggers (not to single them out) will do a ipwhois. If you weed out the others(the ones who report directly to the host) than you are increasing your chances for a higher &lt;strong&gt;lifespan&lt;/strong&gt; across your spam network. Which means more profits.

The reality of the situation is no one is untouchable (with icann running the show at least). So you can understand from a spammers point of view of why its worthless to worry about the ultimate goal of becoming bulletproof. Percentages are where the money is at, not the dream of being untouchable. Every successful blackhatter in the world will tell you quantity is the golden key to blackhat. That is because creating a continuous quantity of sites is the closest a spammer can come to having an infinitely lifespan with the obvious constringent of continual reinvestments of course. Its this misconception that feeds untrue ideas like, "Blackhat is temporary." "Blackhat is for a quick buck."
To dig at what I really thinking you were poking at is the statement in the post that says "&lt;strong&gt;Your hosting is never the wiser and still happy because they don’t have to hear about your complaints."&lt;/strong&gt; To put your mind at ease, that was written in a joking way. It obviously wasn't meant to get ppl thinking that if the host found out what was going on they will be happy about it because they didn't have to read any of the spam complaints. I think its pretty obvious that they will be quite pissed as a matter of fact. :)</description>
		<content:encoded><![CDATA[<p>Excellent Comment!</p>
<p>Thanks for dropping that by us.<br />
To answer your questions<br />
<strong><em>Now do you think …<br />
1) the owner of the shared hosting server will want to risk getting the whole server disconnected?</em></strong><br />
<strong> 2) most tech bloggers really do not know how to do an IPWHOIS lookup ?</strong><br />
Absolutely not. Shared hosts would gladly drop a client to save the server and to save face with the datacenter. Its just common sense business. Thats why spammers consider it vital to prevent as many complaints to their host and their hosts datacenter as possible. Spam profits come from two factors, <strong>Flow</strong> and <strong>Lifespan</strong>. Flow is how much consistant money the spam is making over a given period of time. The lifespan is how long the spam will continue making money before it gets shut down. Increasing any of the two factors decreases the potential of profit loss on a spam project. If you can&#8217;t be bulletproof than you are forced to deal with percentages. If its inescapable that the project will die after 7 days than you have no choice but to attempt to increase the flow percentages per site to increase profits. Likewise if you&#8217;re dealing with a fixed flow than you have no choice but to do everything possible to increase your lifespan. Only a certain percentage of tech bloggers (not to single them out) will do a ipwhois. If you weed out the others(the ones who report directly to the host) than you are increasing your chances for a higher <strong>lifespan</strong> across your spam network. Which means more profits.</p>
<p>The reality of the situation is no one is untouchable (with icann running the show at least). So you can understand from a spammers point of view of why its worthless to worry about the ultimate goal of becoming bulletproof. Percentages are where the money is at, not the dream of being untouchable. Every successful blackhatter in the world will tell you quantity is the golden key to blackhat. That is because creating a continuous quantity of sites is the closest a spammer can come to having an infinitely lifespan with the obvious constringent of continual reinvestments of course. Its this misconception that feeds untrue ideas like, &#8220;Blackhat is temporary.&#8221; &#8220;Blackhat is for a quick buck.&#8221;<br />
To dig at what I really thinking you were poking at is the statement in the post that says &#8220;<strong>Your hosting is never the wiser and still happy because they don’t have to hear about your complaints.&#8221;</strong> To put your mind at ease, that was written in a joking way. It obviously wasn&#8217;t meant to get ppl thinking that if the host found out what was going on they will be happy about it because they didn&#8217;t have to read any of the spam complaints. I think its pretty obvious that they will be quite pissed as a matter of fact. <img src='http://www.BlueHatSEO.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: host</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-10260</link>
		<pubDate>Fri, 12 Jan 2007 17:49:53 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-10260</guid>
					<description>Let me comment from a web host's perspective: 

If the hosting company is not willing to take action, you can just do an ipwhois lookup and contact the datacenter's abuse department directly. 

From our experience, phishing sites or compromised hosting accounts sending spam usually get shut down very quickly - within hours. (That's of course provided that the server is not located in Russia or China.)

How it works: once they receive a complaint, the datacenter's abuse department will contact the owner of the server (hosting company) requesting to shut down the offending account within 1-24 hours (depending on their policies) or in some cases will even attempt to login to the server themselves and disable the site. If the host does not take action, the datacenter will simply disconnect the whole server or null-route the IP for terms of service violation.

Usually even if a minor complaint is received, the datacenter's abuse staff will still pass the information on to the hosting company. 

Now do you think ... 
1) the owner of the shared hosting server will want to risk getting the whole server disconnected?   
2) most tech bloggers really do not know how to do an IPWHOIS lookup ?</description>
		<content:encoded><![CDATA[<p>Let me comment from a web host&#8217;s perspective: </p>
<p>If the hosting company is not willing to take action, you can just do an ipwhois lookup and contact the datacenter&#8217;s abuse department directly. </p>
<p>From our experience, phishing sites or compromised hosting accounts sending spam usually get shut down very quickly - within hours. (That&#8217;s of course provided that the server is not located in Russia or China.)</p>
<p>How it works: once they receive a complaint, the datacenter&#8217;s abuse department will contact the owner of the server (hosting company) requesting to shut down the offending account within 1-24 hours (depending on their policies) or in some cases will even attempt to login to the server themselves and disable the site. If the host does not take action, the datacenter will simply disconnect the whole server or null-route the IP for terms of service violation.</p>
<p>Usually even if a minor complaint is received, the datacenter&#8217;s abuse staff will still pass the information on to the hosting company. </p>
<p>Now do you think &#8230;<br />
1) the owner of the shared hosting server will want to risk getting the whole server disconnected?<br />
2) most tech bloggers really do not know how to do an IPWHOIS lookup ?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Nick</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9772</link>
		<pubDate>Mon, 08 Jan 2007 08:52:15 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9772</guid>
					<description>Hi Eli,

Awesome blog pal! It rocks,really! Always eager for your next post! =)

I have one question on this...when you insert your adsense ads in the iframe (your real adsense pub id is displayed on those HTML external pages you mentioned) what about the source code? 

If u have 3 iframes for instance u just plug the "hijacked" pub id and that´s it? Is there a way they could get to know the real ID on those HTML? 

Just want to make sure that your ID is not accesible =)</description>
		<content:encoded><![CDATA[<p>Hi Eli,</p>
<p>Awesome blog pal! It rocks,really! Always eager for your next post! =)</p>
<p>I have one question on this&#8230;when you insert your adsense ads in the iframe (your real adsense pub id is displayed on those HTML external pages you mentioned) what about the source code? </p>
<p>If u have 3 iframes for instance u just plug the &#8220;hijacked&#8221; pub id and that´s it? Is there a way they could get to know the real ID on those HTML? </p>
<p>Just want to make sure that your ID is not accesible =)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eli</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9705</link>
		<pubDate>Sun, 07 Jan 2007 01:46:45 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9705</guid>
					<description>Sam,
Feel free to post the details of that technique in the contribute area :)
Soon I'm going to post seostomps' post about getting into ask quickly. it'd be awesome to have two different ideas of how to accomplish the same thing in one post.</description>
		<content:encoded><![CDATA[<p>Sam,<br />
Feel free to post the details of that technique in the contribute area <img src='http://www.BlueHatSEO.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Soon I&#8217;m going to post seostomps&#8217; post about getting into ask quickly. it&#8217;d be awesome to have two different ideas of how to accomplish the same thing in one post.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: sam</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9699</link>
		<pubDate>Sat, 06 Jan 2007 21:47:30 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9699</guid>
					<description>hey rose water

to get into ask.. reg a free acc with bloglinesdotcom and add your rss feeds there.. it will work.. hush hush ;)

if you need any help just caugh 47 times and i'll send the angels your way

:)

Eli.. THE best blog in my book!!! keep rockin' mate!!!</description>
		<content:encoded><![CDATA[<p>hey rose water</p>
<p>to get into ask.. reg a free acc with bloglinesdotcom and add your rss feeds there.. it will work.. hush hush <img src='http://www.BlueHatSEO.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>if you need any help just caugh 47 times and i&#8217;ll send the angels your way</p>
<p>:)</p>
<p>Eli.. THE best blog in my book!!! keep rockin&#8217; mate!!!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anonymous</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9532</link>
		<pubDate>Thu, 04 Jan 2007 15:55:51 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9532</guid>
					<description>&lt;strong&gt;Dealing With Those Pesky Narks&lt;/strong&gt;

Very clever way for Blackhatters to avoid having their hosting cancelled</description>
		<content:encoded><![CDATA[<p><strong>Dealing With Those Pesky Narks</strong></p>
<p>Very clever way for Blackhatters to avoid having their hosting cancelled
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: esquillo seocontest</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9460</link>
		<pubDate>Wed, 03 Jan 2007 10:44:19 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9460</guid>
					<description>Hey, great blog, just found it. I love the SEO world and your blog is a must read.</description>
		<content:encoded><![CDATA[<p>Hey, great blog, just found it. I love the SEO world and your blog is a must read.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: NSA</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9450</link>
		<pubDate>Wed, 03 Jan 2007 07:55:21 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9450</guid>
					<description>What about adding an additional layer of protection by loading the iframe part after the page has been loaded (with javascript onload)? 
Even better, checking the dns of the caller to see if it is a google bot/employee and then not displaying it (or making the fake adsense info disappear).</description>
		<content:encoded><![CDATA[<p>What about adding an additional layer of protection by loading the iframe part after the page has been loaded (with javascript onload)?<br />
Even better, checking the dns of the caller to see if it is a google bot/employee and then not displaying it (or making the fake adsense info disappear).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: afmatt</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9430</link>
		<pubDate>Tue, 02 Jan 2007 23:43:03 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9430</guid>
					<description>Yeah - but every little bit helps eh?</description>
		<content:encoded><![CDATA[<p>Yeah - but every little bit helps eh?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: drew</title>
		<link>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9415</link>
		<pubDate>Tue, 02 Jan 2007 19:26:35 +0000</pubDate>
		<guid>http://www.BlueHatSEO.com/dealing-with-those-pesky-narks/#comment-9415</guid>
					<description>This method won't get around the usual way of reporting adsense on web spam pages, by clicking the "Ads by Google" link on the ads and then filling in the form on "Send Google your thoughts on the site or the ads you just saw".</description>
		<content:encoded><![CDATA[<p>This method won&#8217;t get around the usual way of reporting adsense on web spam pages, by clicking the &#8220;Ads by Google&#8221; link on the ads and then filling in the form on &#8220;Send Google your thoughts on the site or the ads you just saw&#8221;.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
