<?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"
	>
<channel>
	<title>Comments on: Phishing Test</title>
	<atom:link href="http://www.mckeay.net/2005/11/30/phishing-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mckeay.net/2005/11/30/phishing-test/</link>
	<description>The views of one man on security, privacy and anything else that catches his attention</description>
	<pubDate>Wed, 20 Aug 2008 08:28:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Jason</title>
		<link>http://www.mckeay.net/2005/11/30/phishing-test/#comment-328</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Sat, 18 Feb 2006 10:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2005/11/30/phishing-test/#comment-328</guid>
		<description>I got 9/10 - only one wrong was CapitalOne (with the domain thingy) which turned out to be legitimate - hey better to be safe than sorry!!
</description>
		<content:encoded><![CDATA[<p>I got 9/10 - only one wrong was CapitalOne (with the domain thingy) which turned out to be legitimate - hey better to be safe than sorry!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leftyman</title>
		<link>http://www.mckeay.net/2005/11/30/phishing-test/#comment-327</link>
		<dc:creator>Leftyman</dc:creator>
		<pubDate>Sun, 04 Dec 2005 10:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2005/11/30/phishing-test/#comment-327</guid>
		<description>I got most of them wrong... I pretty muched guessed the lot.

If it was the real thing and not an image I'm sure I'd get them all right cus I use the CallingID.com toolbar which somehow always recognizes the fruad.
</description>
		<content:encoded><![CDATA[<p>I got most of them wrong&#8230; I pretty muched guessed the lot.</p>
<p>If it was the real thing and not an image I&#8217;m sure I&#8217;d get them all right cus I use the CallingID.com toolbar which somehow always recognizes the fruad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kostas P.</title>
		<link>http://www.mckeay.net/2005/11/30/phishing-test/#comment-326</link>
		<dc:creator>Kostas P.</dc:creator>
		<pubDate>Fri, 02 Dec 2005 12:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2005/11/30/phishing-test/#comment-326</guid>
		<description>Exactly the same mistakes for me too. But I hadn't noticed that you could see the URL at the bottom so I had to read through them and use my instinct.
</description>
		<content:encoded><![CDATA[<p>Exactly the same mistakes for me too. But I hadn&#8217;t noticed that you could see the URL at the bottom so I had to read through them and use my instinct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.mckeay.net/2005/11/30/phishing-test/#comment-325</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 01 Dec 2005 04:20:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2005/11/30/phishing-test/#comment-325</guid>
		<description>Looks like we're all making the same mistake, erring on the side of caution.  Not that I'd expect anything less from the people who read this site.
</description>
		<content:encoded><![CDATA[<p>Looks like we&#8217;re all making the same mistake, erring on the side of caution.  Not that I&#8217;d expect anything less from the people who read this site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: student</title>
		<link>http://www.mckeay.net/2005/11/30/phishing-test/#comment-324</link>
		<dc:creator>student</dc:creator>
		<pubDate>Thu, 01 Dec 2005 04:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2005/11/30/phishing-test/#comment-324</guid>
		<description>I got the exact same as Barry (above). I just looked at the web address in the status bar at the bottom. If the address looked correct, I would glance over the email to see what it was about. As a general rule, I don't click on links in emails when the link goes to a page where I am required to enter personal  information.
</description>
		<content:encoded><![CDATA[<p>I got the exact same as Barry (above). I just looked at the web address in the status bar at the bottom. If the address looked correct, I would glance over the email to see what it was about. As a general rule, I don&#8217;t click on links in emails when the link goes to a page where I am required to enter personal  information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://www.mckeay.net/2005/11/30/phishing-test/#comment-323</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Wed, 30 Nov 2005 23:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2005/11/30/phishing-test/#comment-323</guid>
		<description>1. Chase
Legitimate ... CORRECT

2. PayPal
Phishing Fraud ... CORRECT

3. Bank of America
Phishing Fraud ... INCORRECT
(The correct answer was Legitimate)

4. Washington Mutual
Phishing Fraud ... CORRECT

5. MSN
Phishing Fraud ... CORRECT

6. Earthlink
Legitimate ... CORRECT

7. Amazon
Phishing Fraud ... CORRECT

8. eBay
Phishing Fraud ... CORRECT

9. Capital One
Phishing Fraud ... INCORRECT
(The correct answer was Legitimate)

10. Network Solutions
Legitimate ... CORRECT

You got 8 out of 10 correct, or 80 %

...Speaking of Chase, I tried reporting phishing to them but none of the forms on their website were for phishing reports, and they all required personal information like a telephone number. Then I tried the administrative contact email address in their whois information, but "domadmin at chase dot com" wasn't valid and the email bounced back to me. I reported Chase to http://wdprs.internic.net/ for an incorrect administrative contact email, and I'll be following up if I don't see any progress.

As for Bank of America, they don't autorespond to phishing complaints, and they didn't respond to my complaint about it through their form.
</description>
		<content:encoded><![CDATA[<p>1. Chase<br />
Legitimate &#8230; CORRECT</p>
<p>2. PayPal<br />
Phishing Fraud &#8230; CORRECT</p>
<p>3. Bank of America<br />
Phishing Fraud &#8230; INCORRECT<br />
(The correct answer was Legitimate)</p>
<p>4. Washington Mutual<br />
Phishing Fraud &#8230; CORRECT</p>
<p>5. MSN<br />
Phishing Fraud &#8230; CORRECT</p>
<p>6. Earthlink<br />
Legitimate &#8230; CORRECT</p>
<p>7. Amazon<br />
Phishing Fraud &#8230; CORRECT</p>
<p>8. eBay<br />
Phishing Fraud &#8230; CORRECT</p>
<p>9. Capital One<br />
Phishing Fraud &#8230; INCORRECT<br />
(The correct answer was Legitimate)</p>
<p>10. Network Solutions<br />
Legitimate &#8230; CORRECT</p>
<p>You got 8 out of 10 correct, or 80 %</p>
<p>&#8230;Speaking of Chase, I tried reporting phishing to them but none of the forms on their website were for phishing reports, and they all required personal information like a telephone number. Then I tried the administrative contact email address in their whois information, but &#8220;domadmin at chase dot com&#8221; wasn&#8217;t valid and the email bounced back to me. I reported Chase to <a href="http://wdprs.internic.net/" rel="nofollow">http://wdprs.internic.net/</a> for an incorrect administrative contact email, and I&#8217;ll be following up if I don&#8217;t see any progress.</p>
<p>As for Bank of America, they don&#8217;t autorespond to phishing complaints, and they didn&#8217;t respond to my complaint about it through their form.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.376 seconds -->
