<?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"
	>
<channel>
	<title>Comments on: Verisign increases .com fee to $6.86</title>
	<atom:link href="http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/</link>
	<description>neat fun stuff</description>
	<pubDate>Fri, 25 Jul 2008 16:17:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Vinay</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125406</link>
		<dc:creator>Vinay</dc:creator>
		<pubDate>Fri, 04 Apr 2008 14:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125406</guid>
		<description>For Chetan :: Verisign is parent registry for com/net domains , godaddy also takes from them only. If Verisign increase it means increase for all.

Matt, I only want to made 1 point here, increasing pricing by 40 - 50 cents is ok, but why verisign is not converting into thick registry, while all other registries are Thick Registries today only verisign is Thin Registry.

Why dont ICANN gives a chance to Afilias, who successfully converted .ORG registry to Thick registry. This will secure MN of domain registrars (Remember Register Fly). 

Now they started RDE which will increase cost of Registrars, and in end will impact end users. For what verisign charging 6.42 USD, almost 70 MN domains they holding (450 MN USD Revenue), so why dont ask Verisign to make themselve Thick registry, and give backups of domain details. 

Waiting for your view on this Matt.</description>
		<content:encoded><![CDATA[<p>For Chetan :: Verisign is parent registry for com/net domains , godaddy also takes from them only. If Verisign increase it means increase for all.</p>
<p>Matt, I only want to made 1 point here, increasing pricing by 40 - 50 cents is ok, but why verisign is not converting into thick registry, while all other registries are Thick Registries today only verisign is Thin Registry.</p>
<p>Why dont ICANN gives a chance to Afilias, who successfully converted .ORG registry to Thick registry. This will secure MN of domain registrars (Remember Register Fly). </p>
<p>Now they started RDE which will increase cost of Registrars, and in end will impact end users. For what verisign charging 6.42 USD, almost 70 MN domains they holding (450 MN USD Revenue), so why dont ask Verisign to make themselve Thick registry, and give backups of domain details. </p>
<p>Waiting for your view on this Matt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter (IMC)</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125089</link>
		<dc:creator>Peter (IMC)</dc:creator>
		<pubDate>Mon, 31 Mar 2008 15:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125089</guid>
		<description>Matt,

Just a quick, offtopic, question. Do you guys still do something with spam reports? Seems like it's just a "feel good" feature now, but the reports are ignored?</description>
		<content:encoded><![CDATA[<p>Matt,</p>
<p>Just a quick, offtopic, question. Do you guys still do something with spam reports? Seems like it&#8217;s just a &#8220;feel good&#8221; feature now, but the reports are ignored?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125088</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 31 Mar 2008 14:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125088</guid>
		<description>Hi guys,
I think domains are too cheap in general. I'm always for price reduction but in this case I have a little problem. People buy domains by hundreds and there must be a mechanism in place to stop that practice. High price may be e deterrent to some extend, although it may never stop a spammer from buying domains in large bulks.</description>
		<content:encoded><![CDATA[<p>Hi guys,<br />
I think domains are too cheap in general. I&#8217;m always for price reduction but in this case I have a little problem. People buy domains by hundreds and there must be a mechanism in place to stop that practice. High price may be e deterrent to some extend, although it may never stop a spammer from buying domains in large bulks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Wilsdon</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125081</link>
		<dc:creator>Nick Wilsdon</dc:creator>
		<pubDate>Mon, 31 Mar 2008 08:13:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125081</guid>
		<description>Just to clear up a couple of points:

Verisign is the Registry for .COM. That means they administer the domain and can make contracts with Registrars.

A Registrar is a company who has a direct contractual relationship with a Registry, for example GoDaddy or Tucows. 

A Reseller is someone who sells domains through a program organised by a Registrar. 

This news means that Verisign is raising the cost of a .COM/NET for their Registrars. They are only ones able to buy at this price, *not the general public*. 

This does of course mean the price will go up, as both the Registrars and the Resellers need to make some money. In some cases though companies will sell domains at a loss in order to try and sell additional services to you, such as hosting. 

It's worth keeping this base cost in mind though when you buy domains though. If you see someone selling for under $10, ask yourself how much support they can realistically offer you? Will they take the time to protect my property from complaints or domain fraud/theft?  Sometimes going the cheaper way costs far more in the long run, especially as domains become more valuable.</description>
		<content:encoded><![CDATA[<p>Just to clear up a couple of points:</p>
<p>Verisign is the Registry for .COM. That means they administer the domain and can make contracts with Registrars.</p>
<p>A Registrar is a company who has a direct contractual relationship with a Registry, for example GoDaddy or Tucows. </p>
<p>A Reseller is someone who sells domains through a program organised by a Registrar. </p>
<p>This news means that Verisign is raising the cost of a .COM/NET for their Registrars. They are only ones able to buy at this price, *not the general public*. </p>
<p>This does of course mean the price will go up, as both the Registrars and the Resellers need to make some money. In some cases though companies will sell domains at a loss in order to try and sell additional services to you, such as hosting. </p>
<p>It&#8217;s worth keeping this base cost in mind though when you buy domains though. If you see someone selling for under $10, ask yourself how much support they can realistically offer you? Will they take the time to protect my property from complaints or domain fraud/theft?  Sometimes going the cheaper way costs far more in the long run, especially as domains become more valuable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maurice</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125076</link>
		<dc:creator>Maurice</dc:creator>
		<pubDate>Mon, 31 Mar 2008 07:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125076</guid>
		<description>very cheap compared to some of the country domains .ie is over $40</description>
		<content:encoded><![CDATA[<p>very cheap compared to some of the country domains .ie is over $40</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayson</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125075</link>
		<dc:creator>Jayson</dc:creator>
		<pubDate>Mon, 31 Mar 2008 07:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125075</guid>
		<description>Looks like they're taking advantage of the full 7% - it's still cheaper than many other domain registrars.</description>
		<content:encoded><![CDATA[<p>Looks like they&#8217;re taking advantage of the full 7% - it&#8217;s still cheaper than many other domain registrars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harith</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125073</link>
		<dc:creator>Harith</dc:creator>
		<pubDate>Mon, 31 Mar 2008 07:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125073</guid>
		<description>Good morning Matt,

In October 2006 you were kind to explain to me &lt;a href="http://www.mattcutts.com/blog/interview-today-with-emarketing-talk-show/#comment-88414" rel="nofollow"&gt;the difference between data push and data refresh&lt;/a&gt; .

Would you be kins, at your convenience, to explain to me whats the difference between "reshuffling" and "tweaking" that might happen at the data centers ;-)

Wish you a great day and a successful week.</description>
		<content:encoded><![CDATA[<p>Good morning Matt,</p>
<p>In October 2006 you were kind to explain to me <a href="http://www.mattcutts.com/blog/interview-today-with-emarketing-talk-show/#comment-88414" rel="nofollow">the difference between data push and data refresh</a> .</p>
<p>Would you be kins, at your convenience, to explain to me whats the difference between &#8220;reshuffling&#8221; and &#8220;tweaking&#8221; that might happen at the data centers <img src='http://www.mattcutts.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Wish you a great day and a successful week.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125070</link>
		<dc:creator>Fernando</dc:creator>
		<pubDate>Mon, 31 Mar 2008 04:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125070</guid>
		<description>I'm not quite sure if that's a good move in a period of recession risk.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not quite sure if that&#8217;s a good move in a period of recession risk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125064</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Sun, 30 Mar 2008 22:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125064</guid>
		<description>You do realize that you have to pay Verizon this prize to register your .com domain, no matter who your hosting company is?</description>
		<content:encoded><![CDATA[<p>You do realize that you have to pay Verizon this prize to register your .com domain, no matter who your hosting company is?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125046</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Sun, 30 Mar 2008 02:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattcutts.com/blog/verisign-increases-com-fee-to-686/#comment-125046</guid>
		<description>Highway robbery! lol - I use goduddy also and try to keep everything all in the same spot.  Though I have had a couple issues I don't think the grass is necessarily greener in other pastures.</description>
		<content:encoded><![CDATA[<p>Highway robbery! lol - I use goduddy also and try to keep everything all in the same spot.  Though I have had a couple issues I don&#8217;t think the grass is necessarily greener in other pastures.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
