<?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: Be Careful How You Title Your Domains</title>
	<atom:link href="http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/</link>
	<description></description>
	<lastBuildDate>Fri, 19 Mar 2010 06:10:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alan Cardiff</title>
		<link>http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/comment-page-1/#comment-7734</link>
		<dc:creator>Alan Cardiff</dc:creator>
		<pubDate>Tue, 02 Sep 2008 11:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=948#comment-7734</guid>
		<description>Thankyou so much for this information. I would never would have thouht that it would come to this. 
Domain names in a Will, this is really something.</description>
		<content:encoded><![CDATA[<p>Thankyou so much for this information. I would never would have thouht that it would come to this.<br />
Domain names in a Will, this is really something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/comment-page-1/#comment-7731</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 01 Sep 2008 23:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=948#comment-7731</guid>
		<description>Personally I&#039;m rather curious how their team created for that purpose resolves those disputes despite its inherent risks. It&#039;s tough enough dealing with this every other day in my past registrar life, and we had been sued (which none fortunately prospered) a few times when we refused to intervene.

But...I guess they can manage them.</description>
		<content:encoded><![CDATA[<p>Personally I&#8217;m rather curious how their team created for that purpose resolves those disputes despite its inherent risks. It&#8217;s tough enough dealing with this every other day in my past registrar life, and we had been sued (which none fortunately prospered) a few times when we refused to intervene.</p>
<p>But&#8230;I guess they can manage them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MHB</title>
		<link>http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/comment-page-1/#comment-7725</link>
		<dc:creator>MHB</dc:creator>
		<pubDate>Mon, 01 Sep 2008 19:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=948#comment-7725</guid>
		<description>Richard

Excellent point, I have seen many domains lost when the hosting or web developer put it in their name and then went out of business</description>
		<content:encoded><![CDATA[<p>Richard</p>
<p>Excellent point, I have seen many domains lost when the hosting or web developer put it in their name and then went out of business</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Too Many Secrets</title>
		<link>http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/comment-page-1/#comment-7724</link>
		<dc:creator>Too Many Secrets</dc:creator>
		<pubDate>Mon, 01 Sep 2008 18:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=948#comment-7724</guid>
		<description>Mike,

Yep we see this all the time in our hosting business.  Many times the domain registration is done in the name of a web hosting company or web developer and not the owner&#039;s of the domain.

We always advise clients who switch their hosting to us to get the registration information changed to their own name or company name asap and cite the some reasons you mention in your post.

Unfortunately, we have seen too many domains be held by a former web hosting company, web developers or employees.  Lots of shady people out there I guess.

- Richard.</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>Yep we see this all the time in our hosting business.  Many times the domain registration is done in the name of a web hosting company or web developer and not the owner&#8217;s of the domain.</p>
<p>We always advise clients who switch their hosting to us to get the registration information changed to their own name or company name asap and cite the some reasons you mention in your post.</p>
<p>Unfortunately, we have seen too many domains be held by a former web hosting company, web developers or employees.  Lots of shady people out there I guess.</p>
<p>- Richard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Use Caution When Updating Whois Information &#124; Elliot's Blog</title>
		<link>http://www.thedomains.com/2008/09/01/be-careful-how-you-title-your-domains/comment-page-1/#comment-7723</link>
		<dc:creator>Use Caution When Updating Whois Information &#124; Elliot's Blog</dc:creator>
		<pubDate>Mon, 01 Sep 2008 16:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=948#comment-7723</guid>
		<description>[...] Mike Berkens wrote an important post today about keeping your Whois information current and updated. ICANN regulations require that Whois information is accurate, and if the information isn&#8217;t accurate, there is a chance that your domain name could possibly be taken. There are also many legal reasons to do so, which Mike outlines in his post. It just makes sense to keep your information updated, and if you are worried about spam emails or privacy, just buy the privacy guard. [...]</description>
		<content:encoded><![CDATA[<p>[...] Mike Berkens wrote an important post today about keeping your Whois information current and updated. ICANN regulations require that Whois information is accurate, and if the information isn&#8217;t accurate, there is a chance that your domain name could possibly be taken. There are also many legal reasons to do so, which Mike outlines in his post. It just makes sense to keep your information updated, and if you are worried about spam emails or privacy, just buy the privacy guard. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
