Is your online banking etc really connecting to your bank, and not someone else? Consider DNSSEC: maybe I can help a little (not just for technologists)

• Does your bank or credit union etc wisely use DNSSEC?  I wish mine
  did.  DNSSEC tries to make sure, for example, that a web site you
  visit is really your bank, not an attacker between you and your
  bank:  http://www.wikipedia.org/wiki/DNSSEC
  
  I can possibly find out if you want me to check a given URL, 
  if "no" means you will likely encourage them to use it, as they're
  probably just waiting for a crisis.  
  
  And, does your own computer check for DNSSEC (to let you know
  if there is a problem)?  Mine does now.  
  At most, it costs only the time to make it work.  Maybe all 
  you have to do is point your DNS to 8.8.8.8? I'm not sure 
  for most systems, but we could find out.  
  
  (Then there's DNSCurve for admins to consider.)
  

• But I'm reconsidering whether to bother w/ DNSSEC in the future, after reading discussion about it on news.ycombinator.com .