<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DaveZan.com</title>
	<atom:link href="http://davezan.com/feed" rel="self" type="application/rss+xml" />
	<link>http://davezan.com</link>
	<description></description>
	<lastBuildDate>Tue, 16 Apr 2013 14:30:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Has Network Solutions Been Hacked Or Broken Into?</title>
		<link>http://davezan.com/has-network-solutions-been-hacked-or-broken-into.html</link>
		<comments>http://davezan.com/has-network-solutions-been-hacked-or-broken-into.html#comments</comments>
		<pubDate>Tue, 16 Apr 2013 14:30:08 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Registrars]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[Network Solutions]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1249</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/has-network-solutions-been-hacked-or-broken-into.html">Has Network Solutions Been Hacked Or Broken Into?</a></p><p> Lately I&#8217;ve seen many people searching my blog on Network Solutions. Specifically, if the domain registrar has been hacked or broken into. I wasn&#8217;t aware of any hacking or computer attacks then. So, I did a little checking. It turned out Network Solutions had another recent incident. They first posted about it in their Facebook page last April 11, 2013: &#160; &#160; The domain registrar also wrote about that on their &#8220;Solutions Are Power&#8221; blog. To be expected, many people weren&#8217;t happy about it at all. Can&#8217;t blame them, of course. Soon after that, Network Solutions made another update: &#160; &#160; To be fair, at least the domain registrar somehow notified everyone involved. It&#8217;s the least they could (and should) do, after all. What they said gave a clue, namely WordPress. So I looked around online. It turned out that there had been a string of computer attacks, especially targeting websites that use WordPress and Joomla. ArsTechnica has more: &#160; Security analysts have detected an ongoing attack that uses a huge number of computers from across the Internet to commandeer servers that run the WordPress blogging application. The unknown people behind the highly distributed attack are using more than 90,000 [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/has-network-solutions-been-hacked-or-broken-into.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An International Domain Theft Story</title>
		<link>http://davezan.com/an-international-domain-theft-story.html</link>
		<comments>http://davezan.com/an-international-domain-theft-story.html#comments</comments>
		<pubDate>Sun, 14 Apr 2013 14:45:47 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Law]]></category>
		<category><![CDATA[Domain hijacking]]></category>
		<category><![CDATA[domain law]]></category>
		<category><![CDATA[domain lawyers]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1241</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/an-international-domain-theft-story.html">An International Domain Theft Story</a></p><p>In just a moment, I’m about to share with you a domain theft / hijacking story. It’s not like any I’ve encountered before, although others might have. By international, I mean it involves different parties in different countries. Three, to be exact. The owner originated in Country A, the domain registrar is in Country B, and the thief (or thieves as you’re about to find out) in Country C. Just by those three details alone, you can probably imagine how difficult this situation is. Especially for the owner from Country A. On the face of it, it seemed tough. Dire, even. When I first learned about the story, I was skeptical. Skeptical in the sense that it can be fixed, if ever. I dealt with a few domain theft cases before. None of them were easy to resolve. Not one. At all. What more if it involved parties who lived far apart from one another? Here’s his story on February 2012: &#160; My name is Goran Zinic. Some of you know me as the owner of Indigitalworks.com. On February 22nd, I became a victim of huge Internet fraud, which I would like to share with you. Domain name IndigitalWorks.com and [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/an-international-domain-theft-story.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Happens If A Domain Registrar Shuts Down</title>
		<link>http://davezan.com/what-happens-if-a-domain-registrar-shuts-down.html</link>
		<comments>http://davezan.com/what-happens-if-a-domain-registrar-shuts-down.html#comments</comments>
		<pubDate>Sat, 23 Mar 2013 03:01:03 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Commentary]]></category>
		<category><![CDATA[bankrupt]]></category>
		<category><![CDATA[dodora]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[Registerfly]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1220</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/what-happens-if-a-domain-registrar-shuts-down.html">What Happens If A Domain Registrar Shuts Down</a></p><p>Imagine a day you visit your domain registrar&#8217;s website. It&#8217;s time to renew your domain name. After you type in your registrar&#8217;s website name on your browser and you click ENTER, what do you get? Nothing. No logo, no log-in page, nothing. Or okay, let&#8217;s say their website does show up. Everything&#8217;s (seemingly) fine. You click log-in, enter your username and password, click Submit, and&#8230; &#8230;nothing happens. You get concerned. &#8220;I can&#8217;t log into my account to renew,&#8221; you say to yourself. No problem, you can use your registrar&#8217;s password recovery options. You choose the easiest one. Only, none of them seem to work, either. And that&#8217;s in spite of making sure you&#8217;re doing everything right. &#8220;Okay&#8221;, you sigh. &#8220;I&#8217;d better call/email them.&#8221; You call their phone number. And what do you get? &#160; &#8220;The number you are dialing cannot be reached.&#8221; &#160; Or something like that. Still, not a good sign. You then email asking how to renew your domain name because you can&#8217;t log in. And you need to renew it fast. Days pass, and there&#8217;s no answer. Now you&#8217;re getting worried. How can you renew your domain name if you can&#8217;t log in? Then you search online for any answers. [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/what-happens-if-a-domain-registrar-shuts-down.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Transfer An Expired Domain Name: Is It Possible?</title>
		<link>http://davezan.com/transfer-expired-domain-name.html</link>
		<comments>http://davezan.com/transfer-expired-domain-name.html#comments</comments>
		<pubDate>Fri, 15 Mar 2013 00:37:31 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[expired domains]]></category>
		<category><![CDATA[transfers]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1179</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/transfer-expired-domain-name.html">Transfer An Expired Domain Name: Is It Possible?</a></p><p>Transfer an expired domain name? Some people asked that interesting question soon after I wrote on ICANN&#8217;s upcoming Expired Registration Recovery Policy. So now you may be thinking, &#8220;Wait, transfer an expired domain name to another registrar? Is that allowed?&#8221; On the surface, one might think no. After all, any online service attached to an expired domain name stops working after some time. &#160; Believe it or not, it actually is possible. &#160; It&#8217;s okay if you feel like rubbing your eyes around in disbelief. I did, too, when I first learned about it. But, you read it right that it&#8217;s possible to transfer an expired domain name to another registrar. Not just possible, but doable to a point. How do I know, you ask? Well, I&#8217;ve also done it myself&#8230; &#8230;twice. Of course, that was about three to four years ago if I remember correctly. It&#8217;s been a while since I last pulled off that stunt. Normally you transfer your domain name to another registrar before it expires rather than after. So, how&#8217;s that possible? Before I explain how, I actually and strongly recommend transferring before the domain&#8217;s expiration. Preferably, do it at least one month before. You actually can start the process even a [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/transfer-expired-domain-name.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Domain Expiry Policy To Launch By August 2013</title>
		<link>http://davezan.com/new-domain-expiry-policy-august-2013-2.html</link>
		<comments>http://davezan.com/new-domain-expiry-policy-august-2013-2.html#comments</comments>
		<pubDate>Fri, 08 Mar 2013 05:47:05 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[ICANN]]></category>
		<category><![CDATA[errp]]></category>
		<category><![CDATA[expiration registration recovery policy]]></category>
		<category><![CDATA[expired domains]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1176</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/new-domain-expiry-policy-august-2013-2.html">New Domain Expiry Policy To Launch By August 2013</a></p><p>A new domain expiry policy is coming up courtesy of ICANN. Until otherwise, the upcoming Expired Registration Recovery Policy (ERRP) takes effect on August 31, 2013. In spite of best practices, many people still inadvertently let their domain names expire &#8211; to the point that they permanently lose them. The upcoming ERRP puts in writing how domain registrars will handle them moving forward. You can read the policy in its entirety here. I&#8217;ll try to accurately summarize and highlight some important points, though. Section two of ERRP deals with the domain expiry phase itself. The first part says that registrars must send at least three renewal notices: the first at least one month before expiration, the second at least one week prior, and the third at least five days after that. The above shouldn&#8217;t be a problem because many registrars do them, anyway. Some send so many notices prior, to the point of&#8230;well&#8230;pissing off some customers even. While the second part of section two states that registrars may delete domain names anytime after expiry, many of them still give as much &#8220;grace period&#8221; (up to 45 days) as they can afford. It also says that whether or not a domain [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/new-domain-expiry-policy-august-2013-2.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NameCheap Sets January 22 As Important Day</title>
		<link>http://davezan.com/namecheap-sets-january-22-as-important-day.html</link>
		<comments>http://davezan.com/namecheap-sets-january-22-as-important-day.html#comments</comments>
		<pubDate>Fri, 18 Jan 2013 14:43:43 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Promos]]></category>
		<category><![CDATA[Registrars]]></category>
		<category><![CDATA[Namecheap]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1138</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/namecheap-sets-january-22-as-important-day.html">NameCheap Sets January 22 As Important Day</a></p><p>Just found out that domain registrar NameCheap sets January 22, 2013 as an important day. Better mark that in your calendars. Rather than go on a long-winded explanation, it&#8217;s better to quote exactly what they said. So, here goes: &#160; On January 22, 2013 Namecheap is having an official Move Your Domains Day. Starting just after midnight EST we are offering $3.99 transfers for com, net, org, info, and biz domains! Some limits will apply and a $0.18 ICANN fee will be added to each com and net domains. &#160; Reason for that is this: &#160; As you may know, Namecheap is the leading domain name registrar focused on Internet freedoms. Last year, we had a successful campaign to further this goal and donated over $60,000 to the Electronic Frontier Foundation (EFF). This year, we’re doing it again. For each domain transferred to Namecheap on Move Your Domain Day, we will donate between $0.50 &#038; $1.50, per domain, to EFF. &#160; In case you just came in, someone in Reddit suggested boycotting domain registrar Go Daddy for their then-support for the Stop Online Piracy Act (SOPA) bill. The bill would&#8217;ve created lots of problems for website owners. That time, NameCheap [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/namecheap-sets-january-22-as-important-day.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Go Daddy Demands $199 Due To Spam Complaint</title>
		<link>http://davezan.com/go-daddy-demands-199-due-to-spam-complaint.html</link>
		<comments>http://davezan.com/go-daddy-demands-199-due-to-spam-complaint.html#comments</comments>
		<pubDate>Fri, 11 Jan 2013 03:10:49 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Registrars]]></category>
		<category><![CDATA[Go Daddy]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1123</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/go-daddy-demands-199-due-to-spam-complaint.html">Go Daddy Demands $199 Due To Spam Complaint</a></p><p>Pardon for the rather sensationalist headline. I do hope that gets your attention, though. Just bear with me for a moment. Especially if you&#8217;re not aware of this just yet, you&#8217;re about to find out why. As the headline goes, domain registrar Go Daddy is demanding one of its clients $199 due to a spam complaint. That happens when someone complains to Go Daddy of an alleged spam email coming from a domain name registered with them. I found out about this incident in the Warrior Forum. However, the situation described there is rather unique (or at least one I haven&#8217;t heard of until now). The original poster (OP) of that thread (which is linked at the bottom as a source) says that he never spams anyone, and I&#8217;m inclined to believe him. When Go Daddy forwarded to him the spam complaint, it turns out to be caused by an affiliate of that OP / client of the domain registrar. From what I gathered, the OP is in the medical device industry and periodically accepts affiliates. My guess is one of the affiliates emailed someone about the OP&#8217;s offer, that someone thought it&#8217;s spam, then reported it to Go Daddy. [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/go-daddy-demands-199-due-to-spam-complaint.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Will Domain Names Be Harder To Register Soon?</title>
		<link>http://davezan.com/will-domain-names-be-harder-to-register-soon.html</link>
		<comments>http://davezan.com/will-domain-names-be-harder-to-register-soon.html#comments</comments>
		<pubDate>Sat, 29 Sep 2012 03:57:11 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Commentary]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1112</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/will-domain-names-be-harder-to-register-soon.html">Will Domain Names Be Harder To Register Soon?</a></p><p>I normally don&#8217;t do this. However, I think this recent posting merits attention. If what&#8217;s written in that posting is correct, there&#8217;s a strong possibility that registering a domain name &#8211; or maintaining one &#8211; is going to become more difficult. That&#8217;s because law enforcement has been haggling ICANN and registrars to do something about it for the longest time. I&#8217;m going to copy and paste the article in its entirety here. I hope CircleID won&#8217;t mind, and I&#8217;ll understand their sentiments should they contact me about it. So, read on. Then maybe mark on your calendar the date mentioned at the bottom of that posting: Here goes: &#8220;Question: why has air travel become so painful? Because the threat posed by bad actors requires making everyone jump through hoops before letting them board a plane. To the point that, despite obvious requirements to ensure air safety, some are now openly questioning if the cure is not worse than the disease. Registering a domain name could be about to go the same way. Simply put, the cops that police the Internet are working on some major hoops for domain owners. The disease they are taking aim at is cybercrime. Is their [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/will-domain-names-be-harder-to-register-soon.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Three-Letter Domain Name Stolen, Then Retrieved</title>
		<link>http://davezan.com/three-letter-domain-name-stolen-then-retrieved.html</link>
		<comments>http://davezan.com/three-letter-domain-name-stolen-then-retrieved.html#comments</comments>
		<pubDate>Tue, 14 Aug 2012 11:44:35 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Commentary]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Domain hijacking]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1104</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/three-letter-domain-name-stolen-then-retrieved.html">Three-Letter Domain Name Stolen, Then Retrieved</a></p><p>I was just made aware of another case of a domain name having been stolen. This one involved a three-letter domain name, ezq.com. In domaining circles, three-letter domain names are particular targets because of their rarity. All three-character domain names &#8211; letters, numbers and combinations of both &#8211; have been registered ever since. In this instance, ezq.com belonged to a computer retailer named EZQuest Inc. and managed by a person named Ebrahim Zmehrir. The news report said that Mr. Zmehrir checked his email and got messages saying the domain name was transferring from Go Daddy to a China-based registrar. Once a domain name moves to another registrar, recovery becomes difficult if not impossible. All the more in cases of a stolen domain name moved to an overseas registrar. If a domain name is stolen, normally the first step is to contact the registrar about it right away. Unfortunately it seems Go Daddy just couldn&#8217;t get it back or compel the registrar to return the domain name. The result? &#160; The ensuing three months have plunged Zmehrir into a legal battle and cost his small company an estimated $500,000 in lost sales. &#8230; &#8220;People keep calling and asking, ‘Are you in [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/three-letter-domain-name-stolen-then-retrieved.html/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Go Daddy Shares Insights On Domain Front Running</title>
		<link>http://davezan.com/go-daddy-shares-insights-on-alleged-domain-front-running.html</link>
		<comments>http://davezan.com/go-daddy-shares-insights-on-alleged-domain-front-running.html#comments</comments>
		<pubDate>Fri, 10 Aug 2012 14:34:35 +0000</pubDate>
		<dc:creator>David Z</dc:creator>
				<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Registrars]]></category>
		<category><![CDATA[Domain name front running]]></category>
		<category><![CDATA[Go Daddy]]></category>

		<guid isPermaLink="false">http://davezan.com/?p=1095</guid>
		<description><![CDATA[<p>Check the actual source at <a href="http://davezan.com/go-daddy-shares-insights-on-alleged-domain-front-running.html">Go Daddy Shares Insights On Domain Front Running</a></p><p>Recently I read someone alleging that domain registrar Go Daddy is engaging in what&#8217;s since labeled as domain front running. If you just came in, domain front running is referred to the practice of looking up someone&#8217;s domain search and registering that available domain name before s/he could. Domain front running was a big problem years ago. Many customers search and find available domain names but didn&#8217;t register them on the spot, only to find them taken a day or two after. Many customers believed the registrars they used to search those domain names were behind that event, to the point some registrars reported increased complaints over time even though (for the most part) they had nothing to do with that. Complaints grew enough that registrars finally complained and asked ICANN to do something about it, even giving some suggestions how. ICANN since addressed that domain front running issue. While I don&#8217;t know (and I personally doubt) if domain front running is completely eliminated, I&#8217;ve seen far less complaints these past few years than when they were first reported. Until now, that is. Recently that someone blogged about his experience, to the point &#8211; unsurprisingly &#8211; of accusing Go Daddy [...]</p>]]></description>
		<wfw:commentRss>http://davezan.com/go-daddy-shares-insights-on-alleged-domain-front-running.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: davezan.com @ 2013-06-18 05:32:31 by W3 Total Cache -->