<?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>Acro.net - Technology Rants &#38; Raves by Acroplex® &#187; Verisign</title>
	<atom:link href="http://acro.net/blog/tag/verisign/feed/" rel="self" type="application/rss+xml" />
	<link>http://acro.net/blog</link>
	<description></description>
	<lastBuildDate>Tue, 22 May 2012 17:23:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Drastic changes to the domain security methodology</title>
		<link>http://acro.net/blog/domains/drastic-changes-to-the-domain-security-methodology/</link>
		<comments>http://acro.net/blog/domains/drastic-changes-to-the-domain-security-methodology/#comments</comments>
		<pubDate>Sat, 24 Apr 2010 00:17:26 +0000</pubDate>
		<dc:creator>Acro</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Domains]]></category>
		<category><![CDATA[Copyright Theo Develegas]]></category>
		<category><![CDATA[domainers]]></category>
		<category><![CDATA[domaining]]></category>
		<category><![CDATA[George Kirikos]]></category>
		<category><![CDATA[ICANN]]></category>
		<category><![CDATA[Lock domains]]></category>
		<category><![CDATA[registrar]]></category>
		<category><![CDATA[Registries]]></category>
		<category><![CDATA[Registry]]></category>
		<category><![CDATA[Verisign]]></category>

		<guid isPermaLink="false">http://acro.net/blog/?p=592</guid>
		<description><![CDATA[Today&#8217;s domain security status is marked by several issues that affirm the system&#8217;s weaknesses &#8211; along with the observation that the underlying managing forces do not wish any such change to occur. Very simple methods of domain security are being neglected or even avoided. Registrars should lock domains by default and make it harder to [...]]]></description>
		<wfw:commentRss>http://acro.net/blog/domains/drastic-changes-to-the-domain-security-methodology/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Higher .com/.net fees? Big whoopie!</title>
		<link>http://acro.net/blog/domains/higher-com-net-fees-big-whoopie/</link>
		<comments>http://acro.net/blog/domains/higher-com-net-fees-big-whoopie/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 23:39:13 +0000</pubDate>
		<dc:creator>Acro</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Domains]]></category>
		<category><![CDATA[com/net fees]]></category>
		<category><![CDATA[CPA]]></category>
		<category><![CDATA[LLC]]></category>
		<category><![CDATA[Verisign]]></category>

		<guid isPermaLink="false">http://acro.net/blog/?p=263</guid>
		<description><![CDATA[Today, Verisign announced the increase of their fees for registering/renewing .com/.net domains. Per contract, they are allowed to increase the fees up to 7% annually. No such increase occured in 2009. My response: big whoopie. To those domainers among us with no long term memory; there was a time registrations cost $50 per year with [...]]]></description>
		<wfw:commentRss>http://acro.net/blog/domains/higher-com-net-fees-big-whoopie/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

