Comments on: Using OpenDNS for Phishing Protection http://mjtsai.com/blog/2008/08/07/using-opendns-for-phishing-protection/ Wed, 07 Jan 2009 23:35:59 +0000 http://wordpress.org/?v=2.5.1 By: Roustem Karimov http://mjtsai.com/blog/2008/08/07/using-opendns-for-phishing-protection/#comment-383037 Roustem Karimov Mon, 11 Aug 2008 19:48:36 +0000 http://mjtsai.com/blog/?p=1768#comment-383037 OpenDNS does provide a certain level of protection. However, before it can be recommended it as a reliable solution, try to find some of the recent phishing emails and see if OpenDNS/PhishTank can detect the forgery. I did it myself and 8 times out of 10, the link was not registered in PhishTank database. This database is currently maintained by volunteers and sadly it cannot guarantee 100% protection against phishing. OpenDNS does provide a certain level of protection.

However, before it can be recommended it as a reliable solution, try to find some of the recent phishing emails and see if OpenDNS/PhishTank can detect the forgery. I did it myself and 8 times out of 10, the link was not registered in PhishTank database. This database is currently maintained by volunteers and sadly it cannot guarantee 100% protection against phishing.

]]> By: Fred Blasdel http://mjtsai.com/blog/2008/08/07/using-opendns-for-phishing-protection/#comment-379929 Fred Blasdel Thu, 07 Aug 2008 15:24:52 +0000 http://mjtsai.com/blog/?p=1768#comment-379929 Please don't give any more attention to the goblins over at 'OpenDNS' It's not Open in any sense, and it's not even DNS! The anti-phishing bullshit breaks DNS, and so does their policy of hijacking all unregistered domains for showing web ads. If you want faster, more reliable public DNS, use: 4.2.2.1 4.2.2.2 4.2.2.3 Please don't give any more attention to the goblins over at 'OpenDNS'

It's not Open in any sense, and it's not even DNS! The anti-phishing bullshit breaks DNS, and so does their policy of hijacking all unregistered domains for showing web ads.

If you want faster, more reliable public DNS, use:
4.2.2.1
4.2.2.2
4.2.2.3

]]>