Home opinion-and-analysis Core Dump Web Hosting New TLDs a boon for domain registrars

A report published by Melbourne IT's digital brand services unit provides ammunition for those who suspect the expansion in the number of top level domains (TLDs) benefits the domain name industry rather than the Internet community as a whole.

According to Melbourne IT, around 80,000 trademarks were registered in the .xxx space to protect brands before it went live. Since brand protection was the criterion, it seems unlikely that any of those registrations were a natural fit for .xxx. Rather, organisations were simply following a policy of registering their names in every available TLD, just as they may have previously registered the same names in .com, .net, .com.au and so on.

So that's 80,000 registrations that weren't actually necessary, locking up a substantial number of names that could possibly have been legitimately used by other parties. An argument could be made that such 'defensive' registrations should be automatically cancelled if they are not actively used for purposes consistent with the purpose of the TLD.

At the time the .xxx TLD was being established, registry operator ICM Registry said it would only sell domains to those sites that are "officially in the adult-entertainment industry." But that same article reported that ICM CEO Stuart Lawley expected to make US$200 million a year from defensive registrations.

Only 16 disputes were filed with WIPO during the first full year of operation of .xxx, though there may have been others filed with NAF, which also provides resolution services.

Cybersquatting is most common in the .com space. Not only is 'companyname.com' the first place you'd look for an international business's web site, anyone can register a .com domain and there are practically no restrictions on the names that can be registered. Even though .com.au's original requirement that a domain name must be closely derived from the applicant's name has been watered down with provision for a "close and substantial connection" (which allows, to give just one example, a company called Boomerang.com.au Pty Ltd to register wine.com.au for the purpose of operating a directory of wine businesses), it is still significantly more restrictive than the .com name policy.

A further complication is that trademarks are granted for activities in particular classes. So one company might trademark a word for use in conjunction with "Hand tools and implements (hand-operated); cutlery; side arms; razors" while another might trademark exactly the same word for use in conjunction with "Scientific and technological services and research and design relating thereto; industrial analysis and research services; design and development of computer hardware and software."

Yet the 'baseline policies' for .xxx include a prohibition on "strings that are obvious variants of well-known trademarks not belonging to the registrant" - which would appear to allow the holder of a "well-known trademark" (which usually means a large multinational company) to bring a case against the holder of a lesser-known but similar trademark, even if the former is not involved in the adult entertainment industry.

While there is a certain stigma attached to the adult entertainment industry that could explain a bias against it, other new TLDs could easily end up with similar rules. Why should a company that does not operate in, say, the hairdressing industry have any form of prior claim to or veto over a name that is used by someone in the industry.

Please read on for an example, and advice on brand protection.

WEBINAR 26/27th May

Thinking of deploying Business Intelligence (BI)? So are your competitors.

And the most important, fundamental, tool for delivering your BI information to your users? Dashboards.




VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!


Stephen Withers

joomla visitors

Stephen Withers is one of Australia¹s most experienced IT journalists, having begun his career in the days of 8-bit 'microcomputers'. He covers the gamut from gadgets to enterprise systems. In previous lives he has been an academic, a systems programmer, an IT support manager, and an online services manager. Stephen holds an honours degree in Management Sciences, a PhD in Industrial and Business Studies, and is a senior member of the Australian Computer Society.






Join the iTWire Community and be part of the latest news, invites to exclusive events, whitepapers and educational materials and oppertunities.
Why do I want to receive this daily update?
  • The latest features from iTWire
  • Free whitepaper downloads
  • Industry opportunities