<?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: Twitter&#8217;s DNS Compromised</title>
	<atom:link href="http://www.domainnamenews.com/news/twitters-dns-compromised/6846/feed" rel="self" type="application/rss+xml" />
	<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846</link>
	<description>News and Views from the Domain Name Industry</description>
	<lastBuildDate>Sun, 05 Feb 2012 02:08:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Twitter&#39;s DNS Compromised &#124; Domain Name News &#124; IT News</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71588</link>
		<dc:creator>Twitter&#39;s DNS Compromised &#124; Domain Name News &#124; IT News</dc:creator>
		<pubDate>Thu, 31 Dec 2009 04:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71588</guid>
		<description>[...] original post here: Twitter&#039;s DNS Compromised &#124; Domain Name News          [...]</description>
		<content:encoded><![CDATA[<p>[...] original post here: Twitter&#39;s DNS Compromised | Domain Name News          [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anabolics shop eu</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71537</link>
		<dc:creator>anabolics shop eu</dc:creator>
		<pubDate>Tue, 29 Dec 2009 08:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71537</guid>
		<description>This is confirmed by the statement from Biz Stone that the API had not been affected by the attack, so most likely that DNS entry was not change.</description>
		<content:encoded><![CDATA[<p>This is confirmed by the statement from Biz Stone that the API had not been affected by the attack, so most likely that DNS entry was not change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter’s DNS Compromised [ Domain Name News ]</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71415</link>
		<dc:creator>Twitter’s DNS Compromised [ Domain Name News ]</dc:creator>
		<pubDate>Sun, 20 Dec 2009 07:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71415</guid>
		<description>[...] Twitter’s DNS Compromised December 19th 2009 4:04am As per a tweet from Twitter8217s Biz Stone last night followed by a blog post it appears that Twitter8217s DNS servers have been compromised yesterday The cracker redirected the DNS so it displayed a message from 8220The Iranian Cyber Army8221 As far as we can tell with the NameServer History tool at DomainTools it appears From: www.domainnamenews.com [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter’s DNS Compromised December 19th 2009 4:04am As per a tweet from Twitter8217s Biz Stone last night followed by a blog post it appears that Twitter8217s DNS servers have been compromised yesterday The cracker redirected the DNS so it displayed a message from 8220The Iranian Cyber Army8221 As far as we can tell with the NameServer History tool at DomainTools it appears From: <a href="http://www.domainnamenews.com" rel="nofollow">http://www.domainnamenews.com</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter&#39;s DNS Compromised &#124; Domain Name News &#124; twitterhero.com</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71395</link>
		<dc:creator>Twitter&#39;s DNS Compromised &#124; Domain Name News &#124; twitterhero.com</dc:creator>
		<pubDate>Sat, 19 Dec 2009 03:05:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71395</guid>
		<description>[...] Go here to see the original: Twitter&#039;s DNS Compromised &#124; Domain Name News [...]</description>
		<content:encoded><![CDATA[<p>[...] Go here to see the original: Twitter&#39;s DNS Compromised | Domain Name News [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NewSunNetworks &#8212; Blog &#8212; Twitter&#39;s DNS Compromised &#124; Domain Name News</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71391</link>
		<dc:creator>NewSunNetworks &#8212; Blog &#8212; Twitter&#39;s DNS Compromised &#124; Domain Name News</dc:creator>
		<pubDate>Sat, 19 Dec 2009 01:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71391</guid>
		<description>[...] the rest here: Twitter&#8217;s DNS Compromised &#124; Domain Name News &#160;SHARETHIS.addEntry({ title: &quot;Twitter&#8217;s DNS Compromised &#124; Domain Name News&quot;, url: [...]</description>
		<content:encoded><![CDATA[<p>[...] the rest here: Twitter&#8217;s DNS Compromised | Domain Name News &nbsp;SHARETHIS.addEntry({ title: &quot;Twitter&#8217;s DNS Compromised | Domain Name News&quot;, url: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71380</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 18 Dec 2009 19:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71380</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by domainnamenews: #domains: Twitter&#039;s DNS Compromised http://www.domainnamenews.com/news/twitters-dns-compromised/6846...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by domainnamenews: #domains: Twitter&#8217;s DNS Compromised <a href="http://www.domainnamenews.com/news/twitters-dns-compromised/6846.." rel="nofollow">http://www.domainnamenews.com/news/twitters-dns-compromised/6846..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Twitter’s DNS Compromised &#124; Domain Name News -- Topsy.com</title>
		<link>http://www.domainnamenews.com/news/twitters-dns-compromised/6846/comment-page-1#comment-71377</link>
		<dc:creator>Tweets that mention Twitter’s DNS Compromised &#124; Domain Name News -- Topsy.com</dc:creator>
		<pubDate>Fri, 18 Dec 2009 19:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.domainnamenews.com/?p=6846#comment-71377</guid>
		<description>[...] This post was mentioned on Twitter by DomainNameNews and DomainNews, Randy Wayne. Randy Wayne said: Twitter’s DNS Compromised: Screenshot Of Twitter DNS Hack by tenz1225 on Flickr As per a tweet from Twitter’s B... http://bit.ly/5X74Xn [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by DomainNameNews and DomainNews, Randy Wayne. Randy Wayne said: Twitter’s DNS Compromised: Screenshot Of Twitter DNS Hack by tenz1225 on Flickr As per a tweet from Twitter’s B&#8230; <a href="http://bit.ly/5X74Xn" rel="nofollow">http://bit.ly/5X74Xn</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

