<?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/"
	xmlns:series="http://unfoldingneurons.com/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Phishing Alert : Please watch for emails like this</title>
	<atom:link href="http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/</link>
	<description>Small Business tips, interviews and conversations that provide advice and discussion about small business.</description>
	<lastBuildDate>Thu, 19 Nov 2009 18:43:50 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: OnlineSafetyTeam</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-3734</link>
		<dc:creator>OnlineSafetyTeam</dc:creator>
		<pubDate>Mon, 20 Jul 2009 19:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-3734</guid>
		<description>Funky domain names always give fraudulent emails away. When you hover over a link you can usually see in the bottom left hand corner of your browser where it&#039;s going to take you. A good way to double check.</description>
		<content:encoded><![CDATA[<p>Funky domain names always give fraudulent emails away. When you hover over a link you can usually see in the bottom left hand corner of your browser where it&#39;s going to take you. A good way to double check.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emptydreamer</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-3188</link>
		<dc:creator>emptydreamer</dc:creator>
		<pubDate>Tue, 24 Mar 2009 17:41:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-3188</guid>
		<description>i think that phishing is dumb.&lt;br&gt;go to my site if you have piczo!&lt;br&gt;&lt;a href=&quot;http://www.emptydreamer.piczo.com&quot; rel=&quot;nofollow&quot;&gt;www.emptydreamer.piczo.com&lt;/a&gt;&lt;br&gt;it has codes</description>
		<content:encoded><![CDATA[<p>i think that phishing is dumb.<br />go to my site if you have piczo!<br /><a href="http://www.emptydreamer.piczo.com" rel="nofollow">http://www.emptydreamer.piczo.com</a><br />it has codes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lipo</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2932</link>
		<dc:creator>Lipo</dc:creator>
		<pubDate>Wed, 07 Jan 2009 22:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2932</guid>
		<description>I finally got an email from a credit card company warning about security breach that wasn&#039;t phishing. After calling the number on my statement, it turned out there had been an attempted security breach. I have always routinely discarded every email as phish thinking that they were all bogus, but something about this one seemed real. I&#039;m glad I called and now I am going to check on the ones that come from companies that I actually do business with, just to be on the safe side.</description>
		<content:encoded><![CDATA[<p>I finally got an email from a credit card company warning about security breach that wasn&#39;t phishing. After calling the number on my statement, it turned out there had been an attempted security breach. I have always routinely discarded every email as phish thinking that they were all bogus, but something about this one seemed real. I&#39;m glad I called and now I am going to check on the ones that come from companies that I actually do business with, just to be on the safe side.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alejandro rodriguez</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2578</link>
		<dc:creator>alejandro rodriguez</dc:creator>
		<pubDate>Thu, 06 Nov 2008 02:00:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2578</guid>
		<description>como y donde cambio las claves y usuarios de mi dominio</description>
		<content:encoded><![CDATA[<p>como y donde cambio las claves y usuarios de mi dominio</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domain Registrar Phishing Scam Update &#124; Dave Zan's Domain Name Blog</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2569</link>
		<dc:creator>Domain Registrar Phishing Scam Update &#124; Dave Zan's Domain Name Blog</dc:creator>
		<pubDate>Tue, 04 Nov 2008 04:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2569</guid>
		<description>[...] their main site enom.com if you checked it out. Then Shashi Bellamkonda of Network Solutions also blogged about it, and it&#8217;s also posted on their main site [...]</description>
		<content:encoded><![CDATA[<p>[...] their main site enom.com if you checked it out. Then Shashi Bellamkonda of Network Solutions also blogged about it, and it&#8217;s also posted on their main site [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R. Treasure</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2571</link>
		<dc:creator>R. Treasure</dc:creator>
		<pubDate>Mon, 03 Nov 2008 17:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2571</guid>
		<description>Anyone can tell me what LDAP mean - when i type in my website i get that information. What should i do?</description>
		<content:encoded><![CDATA[<p>Anyone can tell me what LDAP mean &#8211; when i type in my website i get that information. What should i do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2564</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 03 Nov 2008 05:18:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2564</guid>
		<description>It&#039;s indeed another phishing email, Jane. Domain registrar eNom posted about it on their &lt;a href=&quot;http://enom.com&quot;&gt;enom.com&lt;/a&gt; site.</description>
		<content:encoded><![CDATA[<p>It&#39;s indeed another phishing email, Jane. Domain registrar eNom posted about it on their <a href="http://enom.com">enom.com</a> site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Two Domain Registrar Scam Emails &#124; Dave Zan's Domain Name Blog</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2563</link>
		<dc:creator>Two Domain Registrar Scam Emails &#124; Dave Zan's Domain Name Blog</dc:creator>
		<pubDate>Mon, 03 Nov 2008 05:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2563</guid>
		<description>[...] copies of those email which I&#8217;m posting here. Shashi Bellamkonda of Network Solutions also blogged about it. Dear Network Solutions [...]</description>
		<content:encoded><![CDATA[<p>[...] copies of those email which I&#8217;m posting here. Shashi Bellamkonda of Network Solutions also blogged about it. Dear Network Solutions [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jane</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2562</link>
		<dc:creator>jane</dc:creator>
		<pubDate>Sun, 02 Nov 2008 16:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2562</guid>
		<description>I also have received 2 emails like this below - is this another example?  also recieved the network solutions one as well.&lt;br&gt;&lt;br&gt;Dear user, &lt;br&gt;&lt;br&gt;On Sun, 2 Nov 2008 19:39:49 +0300 we received a third party complaint of invalid domain contact information in the Whois database for this domain. Whenever we receive a complaint, we are required by ICANN regulations to initiate an investigation as to whether the contact data displaying in the Whois database is valid data or not. If we find that there is invalid or missing data, we contact both the registrant and the account holder and inform them to update the information. &lt;br&gt;&lt;br&gt;The contact information for the domain which displayed in the Whois database was indeed invalid. On Sun, 2 Nov 2008 19:39:49 +0300 we sent a notice to you at the admin/tech contact email address and the account email address informing you of invalid data in breach of the domain registration agreement and advising you to update the information or risk cancellation of the domain. The contact information was not updated within the specified period of time and we canceled the domain. The domain has subsequently been purchased by another party. You will need to contact them for any further inquiries regarding the domain. &lt;br&gt;&lt;br&gt;PLEASE VERIFY YOUR CONTACT INFORMATION - &lt;a href=&quot;http://www.enom.com&quot;&gt;http://www.enom.com&lt;/a&gt; &lt;br&gt;&lt;br&gt;If you find any invalid contact information for this domain, please respond to this email with evidence of the specific contact information you have found to be invalid on the Whois record for the domain name. Examples would be a bounced email or returned postal mail. If you have a bounced email, please attach or forward with your reply or in the case of returned postal mail, scan the returned letter and attach to your email reply or please send it to: &lt;br&gt;&lt;br&gt;Attn: Domain Services 14455 N Hayden Rd Suite 219 Scottsdale, AZ 85260 &lt;br&gt;&lt;br&gt;&lt;br&gt;LINK TO CHANGE INFORMATION - &lt;a href=&quot;http://www.enom.com&quot;&gt;http://www.enom.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Thank you,&lt;br&gt;Domain Services</description>
		<content:encoded><![CDATA[<p>I also have received 2 emails like this below &#8211; is this another example?  also recieved the network solutions one as well.</p>
<p>Dear user, </p>
<p>On Sun, 2 Nov 2008 19:39:49 +0300 we received a third party complaint of invalid domain contact information in the Whois database for this domain. Whenever we receive a complaint, we are required by ICANN regulations to initiate an investigation as to whether the contact data displaying in the Whois database is valid data or not. If we find that there is invalid or missing data, we contact both the registrant and the account holder and inform them to update the information. </p>
<p>The contact information for the domain which displayed in the Whois database was indeed invalid. On Sun, 2 Nov 2008 19:39:49 +0300 we sent a notice to you at the admin/tech contact email address and the account email address informing you of invalid data in breach of the domain registration agreement and advising you to update the information or risk cancellation of the domain. The contact information was not updated within the specified period of time and we canceled the domain. The domain has subsequently been purchased by another party. You will need to contact them for any further inquiries regarding the domain. </p>
<p>PLEASE VERIFY YOUR CONTACT INFORMATION &#8211; <a href="http://www.enom.com">http://www.enom.com</a> </p>
<p>If you find any invalid contact information for this domain, please respond to this email with evidence of the specific contact information you have found to be invalid on the Whois record for the domain name. Examples would be a bounced email or returned postal mail. If you have a bounced email, please attach or forward with your reply or in the case of returned postal mail, scan the returned letter and attach to your email reply or please send it to: </p>
<p>Attn: Domain Services 14455 N Hayden Rd Suite 219 Scottsdale, AZ 85260 </p>
<p>LINK TO CHANGE INFORMATION &#8211; <a href="http://www.enom.com">http://www.enom.com</a></p>
<p>Thank you,<br />Domain Services</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darla</title>
		<link>http://blog.networksolutions.com/2008/phishing-alert-please-watch-for-this-email/comment-page-1/#comment-2558</link>
		<dc:creator>Darla</dc:creator>
		<pubDate>Sat, 01 Nov 2008 18:24:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.networksolutions.com/?p=342#comment-2558</guid>
		<description>@Juanse - I received that one too:&lt;br&gt;&lt;br&gt;from &lt;a href=&quot;mailto:info@enom.com&quot;&gt;info@enom.com&lt;/a&gt; links go to: &lt;a href=&quot;http://www.enom.com.sys43.ru/&quot;&gt;http://www.enom.com.sys43.ru/&lt;/a&gt;&lt;br&gt;Dear user, &lt;br&gt;&lt;br&gt;On Sat, 1 Nov 2008 13:55:35 +0200 we received a third party complaint of invalid domain contact information in the Whois database for this domain. Whenever we receive a complaint, we are required by ICANN regulations to initiate an investigation as to whether the contact data displaying in the Whois database is valid data or not. If we find that there is invalid or missing data, we contact both the registrant and the account holder and inform them to update the information. &lt;br&gt;&lt;br&gt;The contact information for the domain which displayed in the Whois database was indeed invalid. On Sat, 1 Nov 2008 13:55:35 +0200 we sent a notice to you at the admin/tech contact email address and the account email address informing you of invalid data in breach of the domain registration agreement and advising you to update the information or risk cancellation of the domain. The contact information was not updated within the specified period of time and we canceled the domain. The domain has subsequently been purchased by another party. You will need to contact them for any further inquiries regarding the domain. &lt;br&gt;&lt;br&gt;PLEASE VERIFY YOUR CONTACT INFORMATION - &lt;a href=&quot;http://www.enom.com&quot;&gt;http://www.enom.com&lt;/a&gt; &lt;br&gt;&lt;br&gt;If you find any invalid contact information for this domain, please respond to this email with evidence of the specific contact information you have found to be invalid on the Whois record for the domain name. Examples would be a bounced email or returned postal mail. If you have a bounced email, please attach or forward with your reply or in the case of returned postal mail, scan the returned letter and attach to your email reply or please send it to: &lt;br&gt;&lt;br&gt;Attn: Domain Services 14455 N Hayden Rd Suite 219 Scottsdale, AZ 85260 &lt;br&gt;&lt;br&gt;&lt;br&gt;LINK TO CHANGE INFORMATION - &lt;a href=&quot;http://www.enom.com&quot;&gt;http://www.enom.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Thank you,&lt;br&gt;Domain Services&lt;br&gt;&lt;br&gt;[IncidentID:12397]&lt;br&gt;&lt;a href=&quot;http://www.enom.com.sys43.ru/&quot;&gt;http://www.enom.com.sys43.ru/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>@Juanse &#8211; I received that one too:</p>
<p>from <a href="mailto:info@enom.com">info@enom.com</a> links go to: <a href="http://www.enom.com.sys43.ru/">http://www.enom.com.sys43.ru/</a><br />Dear user, </p>
<p>On Sat, 1 Nov 2008 13:55:35 +0200 we received a third party complaint of invalid domain contact information in the Whois database for this domain. Whenever we receive a complaint, we are required by ICANN regulations to initiate an investigation as to whether the contact data displaying in the Whois database is valid data or not. If we find that there is invalid or missing data, we contact both the registrant and the account holder and inform them to update the information. </p>
<p>The contact information for the domain which displayed in the Whois database was indeed invalid. On Sat, 1 Nov 2008 13:55:35 +0200 we sent a notice to you at the admin/tech contact email address and the account email address informing you of invalid data in breach of the domain registration agreement and advising you to update the information or risk cancellation of the domain. The contact information was not updated within the specified period of time and we canceled the domain. The domain has subsequently been purchased by another party. You will need to contact them for any further inquiries regarding the domain. </p>
<p>PLEASE VERIFY YOUR CONTACT INFORMATION &#8211; <a href="http://www.enom.com">http://www.enom.com</a> </p>
<p>If you find any invalid contact information for this domain, please respond to this email with evidence of the specific contact information you have found to be invalid on the Whois record for the domain name. Examples would be a bounced email or returned postal mail. If you have a bounced email, please attach or forward with your reply or in the case of returned postal mail, scan the returned letter and attach to your email reply or please send it to: </p>
<p>Attn: Domain Services 14455 N Hayden Rd Suite 219 Scottsdale, AZ 85260 </p>
<p>LINK TO CHANGE INFORMATION &#8211; <a href="http://www.enom.com">http://www.enom.com</a></p>
<p>Thank you,<br />Domain Services</p>
<p>[IncidentID:12397]<br /><a href="http://www.enom.com.sys43.ru/">http://www.enom.com.sys43.ru/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
