<?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: Network Solutions Security Hole Allows Domain Hijack</title>
	<atom:link href="http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/</link>
	<description></description>
	<lastBuildDate>Sun, 20 May 2012 18:20:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: skyshipper</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10866</link>
		<dc:creator>skyshipper</dc:creator>
		<pubDate>Wed, 05 May 2010 07:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10866</guid>
		<description>great post,indeed an eye opener, almost like a sequence from a thriller although a dark one,but registrants are supposed to keep whois updated and accurate, guess original registrant has to share blame as well, but great post</description>
		<content:encoded><![CDATA[<p>great post,indeed an eye opener, almost like a sequence from a thriller although a dark one,but registrants are supposed to keep whois updated and accurate, guess original registrant has to share blame as well, but great post</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chandan</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10618</link>
		<dc:creator>chandan</dc:creator>
		<pubDate>Sat, 10 Apr 2010 14:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10618</guid>
		<description>i have seen several domains which have dropped domains as email address. its best to use our ISP email in account access</description>
		<content:encoded><![CDATA[<p>i have seen several domains which have dropped domains as email address. its best to use our ISP email in account access</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Attila</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10545</link>
		<dc:creator>Attila</dc:creator>
		<pubDate>Wed, 31 Mar 2010 16:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10545</guid>
		<description>Wow, that is quite clever. Although, the only thing anyone can do is the previous owner, and he can only scream fraud as the other person mis-represented himself to be someone who he is not. 

However once you cross borders (country lines), its nearly impossible to go after the individual when it concerns fraudulently impersonating an identity.

Can possibly go to ICANN and NetSol to plead your case, but I doubt they will care unless the domain is a really high level name.</description>
		<content:encoded><![CDATA[<p>Wow, that is quite clever. Although, the only thing anyone can do is the previous owner, and he can only scream fraud as the other person mis-represented himself to be someone who he is not. </p>
<p>However once you cross borders (country lines), its nearly impossible to go after the individual when it concerns fraudulently impersonating an identity.</p>
<p>Can possibly go to ICANN and NetSol to plead your case, but I doubt they will care unless the domain is a really high level name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Zoch</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10538</link>
		<dc:creator>Jamie Zoch</dc:creator>
		<pubDate>Tue, 30 Mar 2010 22:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10538</guid>
		<description>@ Ms Domainer,
Thank you! Most whois emails addresses displayed are not the same email address on file for an account, which is a good thing. If you do use the same email address as you do for your registrar account, you should change it. NSI is one registrar that easily allows anybody (yes anybody) access to a specific email address that IS used for an account for a domain name. I didn&#039;t go into detail about this in my post, as that is the biggest security loop hole. I am not aware of obtaining an email address via Moniker, GoDaddy (the two I use) that I know of.</description>
		<content:encoded><![CDATA[<p>@ Ms Domainer,<br />
Thank you! Most whois emails addresses displayed are not the same email address on file for an account, which is a good thing. If you do use the same email address as you do for your registrar account, you should change it. NSI is one registrar that easily allows anybody (yes anybody) access to a specific email address that IS used for an account for a domain name. I didn&#8217;t go into detail about this in my post, as that is the biggest security loop hole. I am not aware of obtaining an email address via Moniker, GoDaddy (the two I use) that I know of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ms Domainer</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10537</link>
		<dc:creator>Ms Domainer</dc:creator>
		<pubDate>Tue, 30 Mar 2010 22:03:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10537</guid>
		<description>*

Jamie,

Great job!

I have always thought that email addresses ought to be hidden in the Whois record, perhaps a changing link similar to that of some privacy services.

That way, people could still email you, but the email itself would be hidden from nefarious eyes.

It just seems to me that registrars ought to take more care in protecting its customers&#039; property without gouging them for it.

On the other hand, the owner should have double checked his/her email address, and when he or she did not receive emails from the registrar, it should have been a red flag.

It&#039;s a shame for the past owner and something that all registrars should look into, not just NSI.

*</description>
		<content:encoded><![CDATA[<p>*</p>
<p>Jamie,</p>
<p>Great job!</p>
<p>I have always thought that email addresses ought to be hidden in the Whois record, perhaps a changing link similar to that of some privacy services.</p>
<p>That way, people could still email you, but the email itself would be hidden from nefarious eyes.</p>
<p>It just seems to me that registrars ought to take more care in protecting its customers&#8217; property without gouging them for it.</p>
<p>On the other hand, the owner should have double checked his/her email address, and when he or she did not receive emails from the registrar, it should have been a red flag.</p>
<p>It&#8217;s a shame for the past owner and something that all registrars should look into, not just NSI.</p>
<p>*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Zoch</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10534</link>
		<dc:creator>Jamie Zoch</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10534</guid>
		<description>@Shashi,
Since the domain name was registered at NSI, it is IMO. Secondly, there is a loop hole that I think, is and can be a problem providing a domains account admin contact email address and I am only aware of it at NSI. If you would like me to post it, I gladly will but I&#039;m sure many will not be safe if I did. I agree it in not NSI&#039;s fault the admin email was outdated, but when a password reset is done and whois details are changed that day as well, some kind of reg flag should go up. IP tracking, Payment from etc potentially all could have raised a red flag.</description>
		<content:encoded><![CDATA[<p>@Shashi,<br />
Since the domain name was registered at NSI, it is IMO. Secondly, there is a loop hole that I think, is and can be a problem providing a domains account admin contact email address and I am only aware of it at NSI. If you would like me to post it, I gladly will but I&#8217;m sure many will not be safe if I did. I agree it in not NSI&#8217;s fault the admin email was outdated, but when a password reset is done and whois details are changed that day as well, some kind of reg flag should go up. IP tracking, Payment from etc potentially all could have raised a red flag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Zoch</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10533</link>
		<dc:creator>Jamie Zoch</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10533</guid>
		<description>@Kevin,
I am not sure how or what &quot;all registrars&quot; process is but it clearly could be a problem with some. NSI has a loop hole that I did not include in my story for a reason and is likely what provides somebody the ability to see the email address of the admin (which can and often is different than the one displayed in whois).</description>
		<content:encoded><![CDATA[<p>@Kevin,<br />
I am not sure how or what &#8220;all registrars&#8221; process is but it clearly could be a problem with some. NSI has a loop hole that I did not include in my story for a reason and is likely what provides somebody the ability to see the email address of the admin (which can and often is different than the one displayed in whois).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shashi Bellamkonda</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10532</link>
		<dc:creator>Shashi Bellamkonda</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10532</guid>
		<description>Hi Jamie,

It is not accurate to categorize this as a Network Solutions security hole. I work for Network Solutions and we advise all domain registrants to always keep their account info updated. If your email domain name has expired you may have bigger issues than just your domain name registration. You may want to include this link where we have posted simple tips to protect  domain name registration no matter who your domain name registrar is. http://blog.networksolutions.com/2008/8-tips-to-protect-your-domain-registration/ and could be useful to your readers.

Thanks,

Shashi</description>
		<content:encoded><![CDATA[<p>Hi Jamie,</p>
<p>It is not accurate to categorize this as a Network Solutions security hole. I work for Network Solutions and we advise all domain registrants to always keep their account info updated. If your email domain name has expired you may have bigger issues than just your domain name registration. You may want to include this link where we have posted simple tips to protect  domain name registration no matter who your domain name registrar is. <a href="http://blog.networksolutions.com/2008/8-tips-to-protect-your-domain-registration/" rel="nofollow">http://blog.networksolutions.com/2008/8-tips-to-protect-your-domain-registration/</a> and could be useful to your readers.</p>
<p>Thanks,</p>
<p>Shashi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Zoch</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10531</link>
		<dc:creator>Jamie Zoch</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10531</guid>
		<description>@Ross,
Theft or &quot;stolen&quot; etc are strong words and ones I didn&#039;t feel comfortable using... so yes, it may be considered theft but I am also not a lawyer and didn&#039;t read the TOS that closely.</description>
		<content:encoded><![CDATA[<p>@Ross,<br />
Theft or &#8220;stolen&#8221; etc are strong words and ones I didn&#8217;t feel comfortable using&#8230; so yes, it may be considered theft but I am also not a lawyer and didn&#8217;t read the TOS that closely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domains</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10530</link>
		<dc:creator>Domains</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:11:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10530</guid>
		<description>Brett Lewis covered this type of theft in CircleID a couple of years ago, but not in as much detail:

http://www.circleid.com/posts/help_domain_name_hijacked/

Good investigation and example.</description>
		<content:encoded><![CDATA[<p>Brett Lewis covered this type of theft in CircleID a couple of years ago, but not in as much detail:</p>
<p><a href="http://www.circleid.com/posts/help_domain_name_hijacked/" rel="nofollow">http://www.circleid.com/posts/help_domain_name_hijacked/</a></p>
<p>Good investigation and example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TeenDomainer</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10529</link>
		<dc:creator>TeenDomainer</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10529</guid>
		<description>Great find I&#039;m amazed someone pulled that off.</description>
		<content:encoded><![CDATA[<p>Great find I&#8217;m amazed someone pulled that off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10528</link>
		<dc:creator>Ross</dc:creator>
		<pubDate>Tue, 30 Mar 2010 20:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10528</guid>
		<description>Is this considered theft since the person is not the original owner of the domain and someone accessed the other persons aacount? I believe the person that did this is a member of the domaining community.</description>
		<content:encoded><![CDATA[<p>Is this considered theft since the person is not the original owner of the domain and someone accessed the other persons aacount? I believe the person that did this is a member of the domaining community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10527</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Tue, 30 Mar 2010 20:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10527</guid>
		<description>Good investigative work there.

But is it not fair to say this is a security problem common to all registrars (or indeed any web site that allows password resets) and not specific to just NSI?</description>
		<content:encoded><![CDATA[<p>Good investigative work there.</p>
<p>But is it not fair to say this is a security problem common to all registrars (or indeed any web site that allows password resets) and not specific to just NSI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sing</title>
		<link>http://www.dotweekly.com/network-solutions-security-hole-allows-domain-hijack/#comment-10526</link>
		<dc:creator>sing</dc:creator>
		<pubDate>Tue, 30 Mar 2010 20:23:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dotweekly.com/?p=3900#comment-10526</guid>
		<description>this was a great find indeed.

Love ur blog, and u basically win me as ur regular visitor to your blog with ur investigated post.

cheers</description>
		<content:encoded><![CDATA[<p>this was a great find indeed.</p>
<p>Love ur blog, and u basically win me as ur regular visitor to your blog with ur investigated post.</p>
<p>cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>

