F-Secure Calls for '.safe' TLD
Rajesh writes "According to F-Secure, ICANN (Internet Corporation for Assigned Names and Numbers), the organization responsible for the global coordination of the Internet's system of unique identifiers, should introduce a .safe domain name to be used by registered banks and other financial organizations."
But wouldn't something a little more, well, financially sound be better. .safe just makes me think of child protection sites, law enforcement security boards and such.
I know .fin is taken, but how about someone put a little more thought into this one. I agree we possibly COULD use a .safe, but for other purposes.
I just don't trust anything that comes out and says "trust me, I'm safe." This isn't a good idea, it teaches people to let their guard down as opposed to being aware of the risks of blanketly trusting a website. What if someone gets some exploit code on one of these sites? I think it'll just take a few notable hacked up website before the whole trust of .safe is lost.
People are infallible and immune from social engineering attacks and there is no way a shady organization would ever get a .safe domain.
My twitter
Count down to the first case where a .safe domain is corrupted because of nepotism, fraud, forgery, what-have-you.
.safe TLD mean, in that case?
A TLD does not solve this problem. An alert user does, aided by tools like regular check-ups, challenge-response systems or cryptography.
We've all heard how some corporations lose several thousands of records of personal data. What does that
People are still pretty dumb and easily tricked, the kind of people that get duped into putting their info in a phishing site are the same people that could be tricked by a fake URL...i.e. safe.financialsite.com or yourbank.com/safe or any other obvious ways to add safe into a URL.
In a world of acronyms, the words are the real victims.
so we need a .safe and a .scam domain?
Likely won't make a lick of difference though.
-nB
whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
I don't think so...
There will always be idiots, who will fill in their credit card information at visa.safe.ru!
09 f9 11 02 9d 74 e3 5b d8 41 56 c5 63
There is a much greater need to tell when a site is NOT safe. There is a reason that URLs with IP addresses and domain names such as "www.paypal.secure.dodgydomain.info/..." are still effective. Introduction of a new TLD is not a replacement for user education.
click to login to http://mybank.safe/ </a>
On the face of it, the idea is not completely awful. As usage of the internet grows, the organization of the domain names will grow in complexity and scope.
.gov for the US government sites. This makes sense. All government-owned web sites are then managed in one place. We have .edu for education institutions.
.shop for on-line shops that actually sell through their web site. eg. Amazon, TigerDirect
We have
Financial institutions are a major power in our society, like government, so maybe they should have a specific domain. This would make looking for a financial place predictable. "I need to find my bank's web site. Ah, I will try bankname.bank" knowing that you will at least get a real bank, and not a phishing scam built on a typo in a name.
There are other major market segments which could justify a TLD like libraries (.lib?) and medical (.med?).
We should not let a fear of abusers stop us from trying to organize things in a predictably way. With more TLD options, we could possibly avoid domain names having to be ever longer because their name was already taken.
Bearded Dragon
But it also sounds like an inviting and tempting invitation for hackers to prove that nothing is ".safe"
What next? Will someone build a ship and claim it's unsinkable? Oh wait...
A: Create a new TLD!
Q: (what was the question again?)