Many users already use Google instead of the url box, just have to see how many user look for MySpace and Facebook. Therefore, there are two resolutions:
1st Google: keyword-> url
2nd DNS: Url -> ip
Maybe Google could provide keyword-> ip resolution. This could not work for website using virtual hosting, but for critical sites like Bank and eBay it might be possible and it could prevent phishing.
i've seen that website give both positive and negative results for a patched server so whilst it may be true that people haven't patched yet, that website is hardly authorative. 
Many users already use Google instead of the url box, just have to see how many user look for MySpace and Facebook. Therefore, there are two resolutions:
1st Google: keyword-> url
2nd DNS: Url -> ip
Maybe Google could provide keyword-> ip resolution. This could not work for website using virtual hosting, but for critical sites like Bank and eBay it might be possible and it could prevent phishing.
Dan might appreciate it if you spelled/spelt his last name properly.
And after applying this patch, it's *still* insecure. So I don't see what all the fuss is about.
The first image doesn't obscure all instances of the vulnerable servers IP address.
i've seen that website give both positive and negative results for a patched server so whilst it may be true that people haven't patched yet, that website is hardly authorative.