Skip to content

.xxx top level domain to start later this year

ICANN released Wednesday that it was approved a new top level domain specific to web sites with adult content. The new TLD is .xxx.

Note: Above is the only place I’m going to use the actual TLD just so this page doesn’t pop up to high on searches for that phrase.

This, in a reversal from a 2000 decision, will allow filtering of child-unfriendly sites much easier.

But, it requires that the sites actually use the extension rather than the more common .com and .net. To get the new TLD requires that the sites adhere to a set of “industry best practices” which includes not carrying material that exploits minors. Other conditions to being allowed to use the TLD are still under discussion.

One reason the sites may want to use the new TLD comes from the Protect Act passed by Congress in 2003. Under this act, adult sites that have misleading addresses could be held liable if children are being exposed to adult content through their misrepresentation.

Of course, the biggest problem is that it is optional for the sites. There will always be adult oriented sites, and many of them are trying to skirt around regulation instead of embracing it. The more “legitimate” sites will probably use this new TLD. These are the ones that already do some sort of age checking; credit card numbers, that sort of thing. But it really seems that the nasty sites that children (and adults) must be protected from are not likely to accept voluntary limits on what they can and cannot do. Especially since having a .com instead of the new TLD removes those restrictions.

I’m also curious what type of enforcement the ICANN really has over this. What happens if a site is found to be in violation of the new TLD requirements? So they can’t use the new TLD anymore and have to go back to .com or any of the hundreds of country specific TLDs. What about a site under the new TLD that simply redirects to another TLD?

Published inInternet

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *