<?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: The darksides domains</title>
	<atom:link href="http://blogs.mcafee.com/mcafee-labs/2008/09/04/the-darksides-domains/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.mcafee.com/mcafee-labs/the-darksides-domains</link>
	<description></description>
	<lastBuildDate>Sat, 12 May 2012 04:55:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Chris Barton</title>
		<link>http://blogs.mcafee.com/mcafee-labs/the-darksides-domains/comment-page-1#comment-18766</link>
		<dc:creator>Chris Barton</dc:creator>
		<pubDate>Mon, 08 Sep 2008 14:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.labs.com/research/blog/?p=711#comment-18766</guid>
		<description>Hi,  Thanks for the verbose response. Permit me to comment inline.

&lt;blockquote&gt;We are extremely surprised to find that you too have made the mistake of publishing frivolous and defamatory statements, without bothering to verify its truthfulness or accuracy.
&lt;/blockquote&gt;

I posted some research mostly about EST, some opinion and some links. I welcome further discussion that does not steer away from the point of the post.

&lt;blockquote&gt;Furthermore, you have completely ignored our challenge (http://blog.directi.com) to the Knujon and Hostexploit reports, which shatters the very basis of their claims. In our blog article, we have provided specific details which will at the minimum, give you strong reason to believe that Directi is being made the scapegoat and is unfairly dragged into this story. The plausible reason for victimizing us, is for the sake of enhancing the storyâ€™s sensationalism. Think about it - without implicating the likes of ICANN and Directi, Knujon and Hostexploitâ€™s reports wouldnâ€™t have come anywhere close to the traction and exposure it has received to date.
&lt;/blockquote&gt;

Sorry I didn&#039;t ignore it.  The post was written the day before your response. We had a few hours of internal delays posting it as the editor is in the USA and I&#039;m in the UK.

Yes, Knujon shook the big tree. He might not have been 100% correct first time but he has highlighted a number of good points that were interesting. In fact my first email response to him was in your defense (in a registrar capacity), whilst I was at that concert.  I did my own research at a tangent into the supply chain and the LogicBoxes setup, and discovered for myself how EST&#039;s various registration processes worked via your systems. That I&#039;m afraid is not a scapegoats position.

I am however glad to see your &lt;a href=&quot;http://hostexploit.com/index.php?view=article&amp;id=15:joint-statement-from-directi-and-hostexploit-clarifying-previous-posts&amp;tmpl=component&amp;print=1&amp;page=&quot; rel=&quot;nofollow&quot;&gt;joint response&lt;/a&gt;. I still think there is significantly more work to be done.
This is a real opportunity to show that you are willing to listen to the community and deal with troublemakers.

&lt;blockquote&gt;It is unfortunate that you seem to make a false allegation of your own, about LogicBoxes not having an AUP for its service. Well, ever since our inception in 2001, we have a very comprehensive AUP in place, which is duly enforced with every client. A copy of the same will be followed by this post.
&lt;/blockquote&gt;

Now that I&#039;d like to see. I couldn&#039;t find on the LogicBoxes website or via google  (&lt;a href=&quot;http://www.google.co.uk/search?q=site%3Alogicboxes.com+aup&quot; rel=&quot;nofollow&quot;&gt;1&lt;/a&gt;,&lt;a href=&quot;http://www.google.co.uk/search?q=site%3Alogicboxes.com+abuse&quot; rel=&quot;nofollow&quot;&gt;2&lt;/a&gt;), I did find something about the not querying the API too much, and having a complaints address however nothing obvious that stated LogicBoxes could at their discretion terminate a relationship for continued abuse.
If it were published prominently the community would help out and quote it at abuse@ staff when making complaints.

If you do have an AUP that covers the LogicBoxes service how come it&#039;s not been used yet? I can still see *new* business spreading downloaders.

&lt;blockquote&gt;Much to the contrary of what you have written, Directi continues to be one of the most proactive players today in terms of combating abuse and implementing strict AUPs. We have a significant investment in terms of manpower and processes to achieve just this. We do so, not because weâ€™re contractually obligated, or to protect our own business interests, but because we sincerely believe in the ideology of making the internet a safer and more secure medium for conducting business. As a matter of fact, we have a ZERO tolerance policy towards unscrupulous activities, and therefore extremely shocked by this incident.
&lt;/blockquote&gt;

I have recognised that with your in-house registrars this is not in dispute.
As for making the internet a safer place, lets be frank for a second and get back to the focus of the post. You guys know the score with ESTDomains and friends but continue to provide them with the service layer for domain management.

&lt;blockquote&gt;On another note, I request you to understand the limitations registrars and related service providers face in tackling these issues. Despite having a dedicated abuse complaints processing team, it is impossible for us to deploy the necessary resources and expertise to manually authenticate the legal status of each of the 4 million + sponsored domain names. A false positive could lead to a significant loss for an innocent customer, for which we will be squarely responsible. Things get even more difficult when other registrars that use our platform, are less sensitive towards their moral responsibilities. Sure â€“ weâ€™d like to pull the plug and permanently close our business with them, but how does one protect the several hundred thousand innocent website owners that also happen to use their services?
&lt;/blockquote&gt;

I made no complaint about false data as I did not want to muddy the waters of responsibility further because I clearly realise the issues involved.
I&#039;m McAfee&#039;s representative for all domain related matters at the APWG so I do understand the limitations of registries in this area, registrars are a different kettle of fish as they have AUP&#039;s in their arsenal.  In much of this abuse I recognised that Directi are not the registrar, they are only the service platform and did my best to stress that point. I&#039;m sure you&#039;re aware that this is exactly where AUP&#039;s and proactive abuse management come in to play.  You clearly know what these customers (resellers and registrars) are up to and yet you let them continue to be new business, you can appreciate why the community want to progress this matter further.

Please don&#039;t suggest that domains on bad-guys accounts that have not had complaints are fine. Given that you appear to use an infinite reseller model I assume you can see every individual customer accounts too. The Internet community is not going to fuel your abuse operations, just the reactive abuse operations.

[&lt;strong&gt;Readers - do not visit the domains in the next paragraph&lt;/strong&gt;]
Some examples if I may:  If you get a complaint about silafine .com (domain created yesterday) for &lt;a href=&quot;http://vil.nai.com/vil/content/v_143903.htm&quot; rel=&quot;nofollow&quot;&gt;hosting some malware&lt;/a&gt; you need to look at the other domains on the account too (I&#039;m betting on : zowidicen  ytujezuruwa orelilukaryd takeworiwu .com being related somehow), rinse and repeat, and ding the reseller/registrar for repeatedly not paying attention too.  Thankfully your abuse ops took down the backend for this scam on request, and here is the proof of the pudding they moved to another domain owned by the same guy &quot;&lt;a href=&quot;http://www.google.co.uk/search?q=seodancer%40gmail.com&amp;source-id=Mozilla%20Firefox&amp;start=0&quot; rel=&quot;nofollow&quot;&gt;seodancer@gmail.com&lt;/a&gt;&quot; who also ownes malware-scan.com, spyshredderscanner.com on a different reseller and probably 100 others too, but you have previously suspended powerantivirus .net but not the others including powerantivirus .cc that was registered at the same time?

&lt;blockquote&gt;I would also sincerely request you to ensure that in the future when referencing reports of this nature, you extend to the subject, an opportunity to confirm the facts.

Weâ€™ll also be glad to clarify your doubts on the above mentioned facts, over a conference call. If youâ€™d like that, do provide us with an appropriate time and number on which you can be reached.
&lt;/blockquote&gt;

I&#039;m clearly an advocate here and I don&#039;t doubt the content of my post, but of course I&#039;m willing to discuss the points raised and I&#039;m more than willing to help if you&#039;re taking action.
I&#039;ve left you a message with my direct contact details with your assistant.

Directi&#039;s anti abuse staff also have an invite to the next APWG meeting (Wed/Thur sessions). It&#039;s a great place to discover what the criminals are actually doing and press the flesh with those fighting cybercrime.

&lt;blockquote&gt;Some of the reputation damage that has been caused as a result of this incident is probably beyond repair. However, I do hope to receive your full support in taking remedial actions for the sake of limiting this damage, and for fulfilling a moral responsibility.
&lt;/blockquote&gt;

I&#039;m inclined to disagree here too. It&#039;s an opportunity to flex that AUP and show your fortitude to protect the the online community.  Also you really shouldn&#039;t be worried about reputation if you are confident you&#039;re process is adequately dealing with situations created by black-hat customers before they get to this stage.  Acting on the perpetrators will do more good for your reputation in the long run than acting on individual domain complaints.</description>
		<content:encoded><![CDATA[<p>Hi,  Thanks for the verbose response. Permit me to comment inline.</p>
<blockquote><p>We are extremely surprised to find that you too have made the mistake of publishing frivolous and defamatory statements, without bothering to verify its truthfulness or accuracy.
</p></blockquote>
<p>I posted some research mostly about EST, some opinion and some links. I welcome further discussion that does not steer away from the point of the post.</p>
<blockquote><p>Furthermore, you have completely ignored our challenge (http://blog.directi.com) to the Knujon and Hostexploit reports, which shatters the very basis of their claims. In our blog article, we have provided specific details which will at the minimum, give you strong reason to believe that Directi is being made the scapegoat and is unfairly dragged into this story. The plausible reason for victimizing us, is for the sake of enhancing the storyâ€™s sensationalism. Think about it &#8211; without implicating the likes of ICANN and Directi, Knujon and Hostexploitâ€™s reports wouldnâ€™t have come anywhere close to the traction and exposure it has received to date.
</p></blockquote>
<p>Sorry I didn&#8217;t ignore it.  The post was written the day before your response. We had a few hours of internal delays posting it as the editor is in the USA and I&#8217;m in the UK.</p>
<p>Yes, Knujon shook the big tree. He might not have been 100% correct first time but he has highlighted a number of good points that were interesting. In fact my first email response to him was in your defense (in a registrar capacity), whilst I was at that concert.  I did my own research at a tangent into the supply chain and the LogicBoxes setup, and discovered for myself how EST&#8217;s various registration processes worked via your systems. That I&#8217;m afraid is not a scapegoats position.</p>
<p>I am however glad to see your <a href="http://hostexploit.com/index.php?view=article&amp;id=15:joint-statement-from-directi-and-hostexploit-clarifying-previous-posts&amp;tmpl=component&amp;print=1&amp;page=" rel="nofollow">joint response</a>. I still think there is significantly more work to be done.<br />
This is a real opportunity to show that you are willing to listen to the community and deal with troublemakers.</p>
<blockquote><p>It is unfortunate that you seem to make a false allegation of your own, about LogicBoxes not having an AUP for its service. Well, ever since our inception in 2001, we have a very comprehensive AUP in place, which is duly enforced with every client. A copy of the same will be followed by this post.
</p></blockquote>
<p>Now that I&#8217;d like to see. I couldn&#8217;t find on the LogicBoxes website or via google  (<a href="http://www.google.co.uk/search?q=site%3Alogicboxes.com+aup" rel="nofollow">1</a>,<a href="http://www.google.co.uk/search?q=site%3Alogicboxes.com+abuse" rel="nofollow">2</a>), I did find something about the not querying the API too much, and having a complaints address however nothing obvious that stated LogicBoxes could at their discretion terminate a relationship for continued abuse.<br />
If it were published prominently the community would help out and quote it at abuse@ staff when making complaints.</p>
<p>If you do have an AUP that covers the LogicBoxes service how come it&#8217;s not been used yet? I can still see *new* business spreading downloaders.</p>
<blockquote><p>Much to the contrary of what you have written, Directi continues to be one of the most proactive players today in terms of combating abuse and implementing strict AUPs. We have a significant investment in terms of manpower and processes to achieve just this. We do so, not because weâ€™re contractually obligated, or to protect our own business interests, but because we sincerely believe in the ideology of making the internet a safer and more secure medium for conducting business. As a matter of fact, we have a ZERO tolerance policy towards unscrupulous activities, and therefore extremely shocked by this incident.
</p></blockquote>
<p>I have recognised that with your in-house registrars this is not in dispute.<br />
As for making the internet a safer place, lets be frank for a second and get back to the focus of the post. You guys know the score with ESTDomains and friends but continue to provide them with the service layer for domain management.</p>
<blockquote><p>On another note, I request you to understand the limitations registrars and related service providers face in tackling these issues. Despite having a dedicated abuse complaints processing team, it is impossible for us to deploy the necessary resources and expertise to manually authenticate the legal status of each of the 4 million + sponsored domain names. A false positive could lead to a significant loss for an innocent customer, for which we will be squarely responsible. Things get even more difficult when other registrars that use our platform, are less sensitive towards their moral responsibilities. Sure â€“ weâ€™d like to pull the plug and permanently close our business with them, but how does one protect the several hundred thousand innocent website owners that also happen to use their services?
</p></blockquote>
<p>I made no complaint about false data as I did not want to muddy the waters of responsibility further because I clearly realise the issues involved.<br />
I&#8217;m McAfee&#8217;s representative for all domain related matters at the APWG so I do understand the limitations of registries in this area, registrars are a different kettle of fish as they have AUP&#8217;s in their arsenal.  In much of this abuse I recognised that Directi are not the registrar, they are only the service platform and did my best to stress that point. I&#8217;m sure you&#8217;re aware that this is exactly where AUP&#8217;s and proactive abuse management come in to play.  You clearly know what these customers (resellers and registrars) are up to and yet you let them continue to be new business, you can appreciate why the community want to progress this matter further.</p>
<p>Please don&#8217;t suggest that domains on bad-guys accounts that have not had complaints are fine. Given that you appear to use an infinite reseller model I assume you can see every individual customer accounts too. The Internet community is not going to fuel your abuse operations, just the reactive abuse operations.</p>
<p>[<strong>Readers - do not visit the domains in the next paragraph</strong>]<br />
Some examples if I may:  If you get a complaint about silafine .com (domain created yesterday) for <a href="http://vil.nai.com/vil/content/v_143903.htm" rel="nofollow">hosting some malware</a> you need to look at the other domains on the account too (I&#8217;m betting on : zowidicen  ytujezuruwa orelilukaryd takeworiwu .com being related somehow), rinse and repeat, and ding the reseller/registrar for repeatedly not paying attention too.  Thankfully your abuse ops took down the backend for this scam on request, and here is the proof of the pudding they moved to another domain owned by the same guy &#8220;<a href="http://www.google.co.uk/search?q=seodancer%40gmail.com&amp;source-id=Mozilla%20Firefox&amp;start=0" rel="nofollow">seodancer@gmail.com</a>&#8221; who also ownes malware-scan.com, spyshredderscanner.com on a different reseller and probably 100 others too, but you have previously suspended powerantivirus .net but not the others including powerantivirus .cc that was registered at the same time?</p>
<blockquote><p>I would also sincerely request you to ensure that in the future when referencing reports of this nature, you extend to the subject, an opportunity to confirm the facts.</p>
<p>Weâ€™ll also be glad to clarify your doubts on the above mentioned facts, over a conference call. If youâ€™d like that, do provide us with an appropriate time and number on which you can be reached.
</p></blockquote>
<p>I&#8217;m clearly an advocate here and I don&#8217;t doubt the content of my post, but of course I&#8217;m willing to discuss the points raised and I&#8217;m more than willing to help if you&#8217;re taking action.<br />
I&#8217;ve left you a message with my direct contact details with your assistant.</p>
<p>Directi&#8217;s anti abuse staff also have an invite to the next APWG meeting (Wed/Thur sessions). It&#8217;s a great place to discover what the criminals are actually doing and press the flesh with those fighting cybercrime.</p>
<blockquote><p>Some of the reputation damage that has been caused as a result of this incident is probably beyond repair. However, I do hope to receive your full support in taking remedial actions for the sake of limiting this damage, and for fulfilling a moral responsibility.
</p></blockquote>
<p>I&#8217;m inclined to disagree here too. It&#8217;s an opportunity to flex that AUP and show your fortitude to protect the the online community.  Also you really shouldn&#8217;t be worried about reputation if you are confident you&#8217;re process is adequately dealing with situations created by black-hat customers before they get to this stage.  Acting on the perpetrators will do more good for your reputation in the long run than acting on individual domain complaints.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vert</title>
		<link>http://blogs.mcafee.com/mcafee-labs/the-darksides-domains/comment-page-1#comment-18764</link>
		<dc:creator>vert</dc:creator>
		<pubDate>Sat, 06 Sep 2008 03:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.labs.com/research/blog/?p=711#comment-18764</guid>
		<description>...(and whilst Terry is dancing in doorways) ...
Rotflmao!!! ;-)</description>
		<content:encoded><![CDATA[<p>&#8230;(and whilst Terry is dancing in doorways) &#8230;<br />
Rotflmao!!! <img src='http://blogs.mcafee.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandeep Ramchandani</title>
		<link>http://blogs.mcafee.com/mcafee-labs/the-darksides-domains/comment-page-1#comment-18763</link>
		<dc:creator>Sandeep Ramchandani</dc:creator>
		<pubDate>Fri, 05 Sep 2008 13:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.labs.com/research/blog/?p=711#comment-18763</guid>
		<description>Dear Chris,

We are extremely surprised to find that you too have made the mistake of publishing frivolous and defamatory statements, without bothering to verify its truthfulness or accuracy.

Furthermore, you have completely ignored our challenge (http://blog.directi.com) to the Knujon and Hostexploit reports, which shatters the very basis of their claims. In our blog article, we have provided specific details which will at the minimum, give you strong reason to believe that Directi is being made the scapegoat and is unfairly dragged into this story. The plausible reason for victimizing us, is for the sake of enhancing the storyâ€™s sensationalism. Think about it - without implicating the likes of ICANN and Directi, Knujon and Hostexploitâ€™s reports wouldnâ€™t have come anywhere close to the traction and exposure it has received to date.

It is unfortunate that you seem to make a false allegation of your own, about LogicBoxes not having an AUP for its service. Well, ever since our inception in 2001, we have a very comprehensive AUP in place, which is duly enforced with every client. A copy of the same will be followed by this post.

Much to the contrary of what you have written, Directi continues to be one of the most proactive players today in terms of combating abuse and implementing strict AUPs. We have a significant investment in terms of manpower and processes to achieve just this. We do so, not because weâ€™re contractually obligated, or to protect our own business interests, but because we sincerely believe in the ideology of making the internet a safer and more secure medium for conducting business. As a matter of fact, we have a ZERO tolerance policy towards unscrupulous activities, and therefore extremely shocked by this incident.

On another note, I request you to understand the limitations registrars and related service providers face in tackling these issues. Despite having a dedicated abuse complaints processing team, it is impossible for us to deploy the necessary resources and expertise to manually authenticate the legal status of each of the 4 million + sponsored domain names. A false positive could lead to a significant loss for an innocent customer, for which we will be squarely responsible. Things get even more difficult when other registrars that use our platform, are less sensitive towards their moral responsibilities. Sure â€“ weâ€™d like to pull the plug and permanently close our business with them, but how does one protect the several hundred thousand innocent website owners that also happen to use their services?

I would also sincerely request you to ensure that in the future when referencing reports of this nature, you extend to the subject, an opportunity to confirm the facts.

Weâ€™ll also be glad to clarify your doubts on the above mentioned facts, over a conference call. If youâ€™d like that, do provide us with an appropriate time and number on which you can be reached.

Some of the reputation damage that has been caused as a result of this incident is probably beyond repair. However, I do hope to receive your full support in taking remedial actions for the sake of limiting this damage, and for fulfilling a moral responsibility.

Best Regards,

Sandeep Ramchandani
Strategic Partner Manager - The Directi Group
Tel : +1 (832) 295 1535 Extn: 7624
Fax : +1 (904) 369 0153</description>
		<content:encoded><![CDATA[<p>Dear Chris,</p>
<p>We are extremely surprised to find that you too have made the mistake of publishing frivolous and defamatory statements, without bothering to verify its truthfulness or accuracy.</p>
<p>Furthermore, you have completely ignored our challenge (http://blog.directi.com) to the Knujon and Hostexploit reports, which shatters the very basis of their claims. In our blog article, we have provided specific details which will at the minimum, give you strong reason to believe that Directi is being made the scapegoat and is unfairly dragged into this story. The plausible reason for victimizing us, is for the sake of enhancing the storyâ€™s sensationalism. Think about it &#8211; without implicating the likes of ICANN and Directi, Knujon and Hostexploitâ€™s reports wouldnâ€™t have come anywhere close to the traction and exposure it has received to date.</p>
<p>It is unfortunate that you seem to make a false allegation of your own, about LogicBoxes not having an AUP for its service. Well, ever since our inception in 2001, we have a very comprehensive AUP in place, which is duly enforced with every client. A copy of the same will be followed by this post.</p>
<p>Much to the contrary of what you have written, Directi continues to be one of the most proactive players today in terms of combating abuse and implementing strict AUPs. We have a significant investment in terms of manpower and processes to achieve just this. We do so, not because weâ€™re contractually obligated, or to protect our own business interests, but because we sincerely believe in the ideology of making the internet a safer and more secure medium for conducting business. As a matter of fact, we have a ZERO tolerance policy towards unscrupulous activities, and therefore extremely shocked by this incident.</p>
<p>On another note, I request you to understand the limitations registrars and related service providers face in tackling these issues. Despite having a dedicated abuse complaints processing team, it is impossible for us to deploy the necessary resources and expertise to manually authenticate the legal status of each of the 4 million + sponsored domain names. A false positive could lead to a significant loss for an innocent customer, for which we will be squarely responsible. Things get even more difficult when other registrars that use our platform, are less sensitive towards their moral responsibilities. Sure â€“ weâ€™d like to pull the plug and permanently close our business with them, but how does one protect the several hundred thousand innocent website owners that also happen to use their services?</p>
<p>I would also sincerely request you to ensure that in the future when referencing reports of this nature, you extend to the subject, an opportunity to confirm the facts.</p>
<p>Weâ€™ll also be glad to clarify your doubts on the above mentioned facts, over a conference call. If youâ€™d like that, do provide us with an appropriate time and number on which you can be reached.</p>
<p>Some of the reputation damage that has been caused as a result of this incident is probably beyond repair. However, I do hope to receive your full support in taking remedial actions for the sake of limiting this damage, and for fulfilling a moral responsibility.</p>
<p>Best Regards,</p>
<p>Sandeep Ramchandani<br />
Strategic Partner Manager &#8211; The Directi Group<br />
Tel : +1 (832) 295 1535 Extn: 7624<br />
Fax : +1 (904) 369 0153</p>
]]></content:encoded>
	</item>
</channel>
</rss>

