Is Your Online Bank .SAFE ?
In the hope of preventing possible future fraud, security professionals are now suggesting that banks must do more to protect their web sites. The idea is for all banks to host their customer access webs on private dedicated domains reserved exclusively for banks. Suggestions have been made for a .safe and .sure locked-down TLD. In this case only registered financial institutions would be the only ones able to acquire the special TLD for use with these webs. It’s a good idea.
F-Secure’s chief research officer stated that such a move would help security companies further protect consumers.
The philosophy here is that unlike the extremely common dot-com TLD, a locked-down TLD like .safe or .sure would be immediately recognizable as a legitimate domain. It wouldn’t stop the phishing attacks that take place now, but the presence of a .safe domain would enable security software to recognize a safe or unsafe domain immediately.
Source: Securitypronews.com
Yet another domain just for the sake of security? Let’s get serious. This is not a sensible solution.
Banks should host their database within their premises, behind hardware and software firewalls (as major financial institutions do) and allow clients to access their accounts via a secured (SSL) connection.
Another TLD can only cause confusion. We don’t need it. – In my opinion.
I agree, and it looks now like banks don’t want a new TLD either and are pushing to block it. Thanks David.
Mark