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."
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
Who will accredit third world banks such as the FIRST BANK OF JOSEPH ENTBE OF NIGERIA?
Some drink at the fountain of knowledge. Others just gargle.
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.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Exactly, how many people would pay for an .unsafe tld?
.com.safe, .gov.safe, .net.safe....
.unsafe domain and we're done!
So once 95% of all websites decide that they want to be safe, how do organise the namespace? How about
Then all we do is turn off the
Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
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.
> So once 95% of all websites decide that they want to be safe, how do organise the namespace?
.safe, .extrasafe, .doubleplussafe, .360safe etc. The only limit is the amount payed to the registrar :-)
That should be easy:
Agreed. We should also create a .terror domain--it'd help make tracking down those evil evil terra-ists that much easier...
This guy's the limit!
You don't let '95%' of all domains use it.
So financial institutions get it, but "we're not a bank" Paypal wouldn't.
That's a shiv I would love to see paypal get.
The Kruger Dunning explains most post on
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...
Support the .scam domain! And the .spam domain too!
Sent from my ASR33 using ASCII