<?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: RegisterFly Troubles and Whois Privacy</title>
	<atom:link href="http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/</link>
	<description>Just another Hosting weblog</description>
	<lastBuildDate>Wed, 17 Mar 2010 11:14:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Domainers Corner &#187; Why it Would Take a Miracle for RegisterFly to get Back off the Ground</title>
		<link>http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/comment-page-1/#comment-2529</link>
		<dc:creator>Domainers Corner &#187; Why it Would Take a Miracle for RegisterFly to get Back off the Ground</dc:creator>
		<pubDate>Fri, 23 Mar 2007 21:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/#comment-2529</guid>
		<description>[...] whois privacy service or who privacy-enhanced their domain registration details themselves, could be in for a battle to prove ownership of their domains in case RegisterFly goes out of [...]</description>
		<content:encoded><![CDATA[<p>[...] whois privacy service or who privacy-enhanced their domain registration details themselves, could be in for a battle to prove ownership of their domains in case RegisterFly goes out of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why It Would Take A Miracle For RegisterFly To Start Flying Again &#187; Daily Domainer</title>
		<link>http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/comment-page-1/#comment-657</link>
		<dc:creator>Why It Would Take A Miracle For RegisterFly To Start Flying Again &#187; Daily Domainer</dc:creator>
		<pubDate>Tue, 27 Feb 2007 07:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/#comment-657</guid>
		<description>[...] whois privacy service or who privacy-enhanced their domain registration details themselves, could be in for a battle to prove ownership of their domains in case RegisterFly goes out of [...]</description>
		<content:encoded><![CDATA[<p>[...] whois privacy service or who privacy-enhanced their domain registration details themselves, could be in for a battle to prove ownership of their domains in case RegisterFly goes out of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/comment-page-1/#comment-621</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 25 Feb 2007 04:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bluefur.com/2007/02/23/registerfly-troubles-and-whois-privacy/#comment-621</guid>
		<description>Well, their site&#039;s back up, maybe the issues have been resolved?

As for Whois Protection, I think it&#039;s a good idea, because then people don&#039;t know your address... But, I think they should include some details about you for the Whois Protection. Maybe something like:

&quot;Whois Protection Companies Name
Domain Owners Name
Whois Protection Companies Address
Whois Protected Forwarding to Domain Owners Email
Domain Owners Phone Number&quot;

Something like that maybe... Or maybe other small details about the Domain Owner, like first 2 digits of house number or postal/zip code, or something. Enough information so that you&#039;d be able to verify it was you. Customers should also keep (and print out) their invoices for domains and hosting. With my old host, I almost lost one of my domains because I had registered it through them and they put their (I actually think only 1 person worked their, but w/e) information for the Whois of that domain. Which I thought was more to protect my information... But, the company became &quot;static&quot; and I got no answers to any support tickets, so I decided to switch. But, they didn&#039;t let me manage my domain, so I had to contact the company who they went through to register the domains, and my Invoice for that domain was what got me my domain into my control. So, long story short, keep your Invoices. :P</description>
		<content:encoded><![CDATA[<p>Well, their site&#8217;s back up, maybe the issues have been resolved?</p>
<p>As for Whois Protection, I think it&#8217;s a good idea, because then people don&#8217;t know your address&#8230; But, I think they should include some details about you for the Whois Protection. Maybe something like:</p>
<p>&#8220;Whois Protection Companies Name<br />
Domain Owners Name<br />
Whois Protection Companies Address<br />
Whois Protected Forwarding to Domain Owners Email<br />
Domain Owners Phone Number&#8221;</p>
<p>Something like that maybe&#8230; Or maybe other small details about the Domain Owner, like first 2 digits of house number or postal/zip code, or something. Enough information so that you&#8217;d be able to verify it was you. Customers should also keep (and print out) their invoices for domains and hosting. With my old host, I almost lost one of my domains because I had registered it through them and they put their (I actually think only 1 person worked their, but w/e) information for the Whois of that domain. Which I thought was more to protect my information&#8230; But, the company became &#8220;static&#8221; and I got no answers to any support tickets, so I decided to switch. But, they didn&#8217;t let me manage my domain, so I had to contact the company who they went through to register the domains, and my Invoice for that domain was what got me my domain into my control. So, long story short, keep your Invoices. :P</p>
]]></content:encoded>
	</item>
</channel>
</rss>
