2 ms·
One huge issue with this is phishing. DNS certainly isn't bulletproof, but combined with SSL it's pretty secure. If I'm at https://www.bofa.com https://www.bof
by tlrobinson 19y ago
One huge issue with this is phishing. DNS certainly isn't bulletproof, but combined with SSL it's pretty secure.
If I'm at https://www.bofa.com https://www.bofa.com and my browser doesn't warn me, I can be pretty damn sure I'm actually at Bank of America's website.
If I were taken to https://171.159.65.173 https://171.159.65.173 by Google I would really have no idea whether or not it was BofA's site.
- a-priori 19y agoThis is a UI issue that can be solved with good search. When loading a page, the browser can do a "reverse lookup" on the URL through a search engine and display common terms associated with it instead of (or in addition to) the URL. If you're expecting Bank of America, and it shows "sex, porn, xxx" in your status bar, you may not want to click it.
- tlrobinson 19y agoThe problem isn't porn sites masquerading as banks, it's fake banks masquerading as banks. A reverse lookup through a search engine is more akin to a blacklist of bad sites, whereas DNS and SSL is essentially a whitelist of good sites. The problem with blacklists is it's inevitable that bad sites will slip through the cracks. DNS solves the UI problem: the inability of humans to easily remember IP addresses. As I mentioned in another comment, DNS isn't the problem, it's the allocation of domain names. If squatters and spammers couldn't register domains so easily and cheaply it wouldn't be a problem.