How many TLDs are there?

I love this visual, via ICANN, a diagram of the world’s top-level domains (TLDs) — all 280 of them.

all_domains_icann

The overwhelming majority of TLDs are country codes, most of which are included in the poster I published about a year ago.

Looking ahead, I would expect the “g” domains to multiply in number. These generic TLDs include domains such as .biz and .info. ICANN recently opened a call for applications to open gTLDs for governments and corporations.

New gTLDs could include “.coke” and “.paris.” It remains to be seen if companies are willing to put up the cash to get these domains, but I’m fairly certain a good many will.

But for now at least the total number of TLDs stands at 280.

Is .NYC the next 212? Or is it the next .LA?

So it’s looking like .NYC may indeed come to fruition.

It certainly has its proponents.

Paris and Berlin are also pursuing their own domains. But the reason I see .NYC gaining traction is that the proposed registrar dotNYC is promising to return a percentage of revenues to the city — and what city is going to turn down extra money these days?

According to the NYPost, “Anthony Van Couvering, CEO of a company called dotNYC, predicted roughly $3 million would flow into city coffers each year by the third year of the domain’s existence.”

This number assumes roughly a million registered domains, renewed annually. For a city of eight million, that may not sound like much, except when you consider that the United States, with 280 million people, has only registered a few million .US domains.

Council Speaker Christine Quinn, who supports the domain, said, “A local business won’t have to outbid a guy in Kansas to get TonysPizza.com. They’ll be able to get TonysPizza.nyc,” Quinn said.

It’s a nice thought, assuming that small businesses want their own .NYC domains. I’m sure many do. But how will the city keep the out-of-town squatters from taking TonysPizza before Tony gets to it?

Of all the city domains, .NYC certainly stands the best chance of succeeding. Perhaps it will become as coveted as 212 once was.

But just to be safe, city council members would be wise to study .LA — offered up in 2006 as a Los Angeles domain (by way of Laos). When’s the last time you visited a .LA Web site?

.EU: Three years and three million registrations

It’s been nearly three years since .EU went live.

Stephane reports that the domain reached 3 million registrations today. Not too bad, considering that .US is still well under two million.

So who’s using this domain? Amazon is using it as a European placeholder; you can test it here.

BMW uses it only as a redirect domain. The same goes for IKEA and Siemens.

So while the jury is still out as to whether .EU will ever live up to the landing page potential of a ccTLD or a .COM, it has certainly proven to be popular. And I still maintain that it makes a great landing page for a European home page.

IDNs get on the fast track

So with the “father of Internet” and chief Internet evangelist at Google, Vinton Cerf, chairing the latest IDNA working group and ICANN issuing a fast track PDF document, it appears that we’re really truly absolutely going to see IDNs come to light in 2009.

I think.

I first covered the “coming” of IDNs in 2000. Little did I know then that it would be such a long process.

Granted, IDNs already exist in the eyes of a number of registrars around the world. You can find an IDN registrar today on this list courtesy of Verisign.

But in the eyes of ICANN, IDNs aren’t yet official.

If you’re interested in the nitty gritty of what these ICANN-approved IDNs are going to look like, check out the fast track document. The document makes it clear that IDNs can only be derived from one script. In other words, we should see no mixing of, say, Latin and Cyrillic characters to create a bogus http://www.pаypal.com/ address (try the link out and see for yourself).

Countries that share a common official language will also need to work together to develop a consistent code table of accepted characters. I can see this being a particularly tricky process, depending on the countries involved.

But the good news here is that the number of obstacles appear to be decreasing in number. There are still some issues to be resolved — like how much money ICANN is going to expect for all this effort.

Will acquiring an IDN cost a registrar the same as a gTLD: $185,000?

Or will the fee be minimal in exchange for some type of revenue share based on registrations? All I do know is that there is demand for a fast-track process and the standards folks are now hashing out the final IDNA document.

Next year could be the year.

Really.

ICANN’s IDN site