The .co registry .CO Internet has announced the winners of its inaugural Bulby Awards, given out to the best .co sites.
Key registrar partner Go Daddy won an award (for x.co), as did the companies’ joint Super Bowl spokesmodel Joan Rivers (for joan.co).
Go Daddy’s Bulby was for the Best Use Of A Single Letter Domain. It beat Twitter (t.co) and Overstock (o.co). Rivers beat the singer Charlotte Church for Best Personal Site.
Sociable.co beat domain blogger Elliot Silver (bahamas.co) to the Best Content award.
The winners were tallied up from votes submitted online, .CO said. The results can be found here.
Afilias does something similar for .info domains every year, but its awards have cash prizes.
If you’ve ever doubted what a rarefied world we work in, check out this new CNN interview with ICM Registry, which confusingly conflates .xxx with ICANN’s new top-level domains program.
Anchor Pauline Chiou uses the approval of new gTLD program as a segue into a brief interview with ICM president Stuart Lawley about the forthcoming .xxx sunrise period.
“If they want to apply for this one-time block do they have to pay this $185,000?” she asks
She goes on to press Lawley into launching a defense of ICANN’s program that I doubt he was expecting.
You’ll notice that Chiou also refers to ICANN as the “Internet Corporation for Assigned Names” and flatteringly describes it as “the group that oversees the development of the internet”.
For a casual viewer, it would be fairly easy to come away from this interview assuming Lawley works for ICANN, and that .xxx domains could cost $185,000.
Will http://google ever work?
Will any of the hundreds of .brand gTLDs expected to be approved by ICANN in its first round of new top-level domains resolve without dots?
Will users be able to simply type in the name of the brand they’re looking for into their browser’s address bar and have it resolve to the company’s official site?
Probably not, according to the experts.
ICANN’s Applicant Guidebook answers this question, but you need to know where to look, and to know a little about DNS records, to figure it out what it actually says.
Section 18.104.22.168 of the Guidebook (page 75 of the May 30 PDF) provides a list of the permissible contents of a new gTLD zone.
Specifically not allowed are A and AAAA records, which browsers need in order to find web sites using IPv4 and IPv6 respectively.
“To facilitate a dotless domain, you would need to place an A or a AAAA record in the zone, and these are not on the list of permitted record types,” said Kim Davies, root zone manager at IANA. “The net result is a default prohibition on dotless domains.”
Applicants may be able to obtain A/AAAA records if they specifically ask for them, but this is very likely to trigger an Extended Evaluation and a Registry Services Review, according to Davies and the Guidebook.
There’s an additional $50,000 fee for a Registry Services Review, with no guarantee of success. It will also add potentially months to the application’s processing time.
(Incidentally, ICANN has also banned DNS “wildcards”. You cannot have an infinite SiteFinder-style catch-all at the second level, you need to allocate domain names individually.)
Applicants that successfully obtain A/AAAA records, enabling dotless domains, would face a far greater problem than ICANN’s rules – endpoint software probably won’t support them.
“As it stands, most common software does not support the concept,” Davies said. “There is a common assumption that fully qualified domain names will have at least one dot in them.”
You can type IP addresses, host names, domain names or search terms into browser address bars, and dots are one of the ways the software figures out you’re looking for a domain.
You can test this today. There are already a handful of top-level domains, probably fewer than 20 and all ccTLDs, that have implemented an A record at the TLD level.
They don’t revolve on any Windows 7 browser I’ve tested (Firefox/IE/Chrome), but I’d be interested in hearing your experiences, if you’d be so good as to leave a comment below.
Given the lack of software support, it may be a poor use of time and resources to fight ICANN for a dotless gTLD that most internet users won’t even be able to resolve.
According to a recent CircleID article by Paul Vixie, chairman of the Internet Systems Consortium, many browsers treat domains without dots as local resources.
Only if the browser’s “DNS search list” cannot find a local resource matching the dotless TLD will it then go out to the internet to look for it.
In some organizations, a local resource may have been configured which matches a new gTLD. There may be a local server called “mail” for example, which could clash with a .mail gTLD.
A recent article in The Register quoted security people fretting about what would happen if a malicious hacker somehow persuaded ICANN to approve a string such as .localhost or .lan.
These worries appear to be largely reliant on an erroneous belief that getting your hands on a gTLD is going to be as simple as registering a domain name.
In reality, there’s going to be months of technical evaluation – conducted in a fish-bowl, subject to public comment, applicant background checks and, in the case of a request for A records, the aforementioned Registry Services Review – before a gTLD is approved.
If everything works according to plan, security problems will be highlighted by this process and any gTLDs that would break the internet will be caught and rejected.
So it seems very unlikely that we’re going to see domains without dots hitting the web any time soon.
Domain names are designed to help people find you. Dotless domains today will not do that, even if ICANN does approve them.
Do I have to write another 19 of these stories?
.CO Internet has announced the sale of the domain name g.co to Google. It will be used – shock! – as a URL shortener for Google’s services.
While the selling price has not been disclosed, I believe the starting bid for single-character .co domains is around $1.5 million. I expect Google will have paid more.
Google said on its official blog that only Google will be able to create g.co short links and they’ll only redirect to Google sites, unlike goo.gl, which is its customer-facing shortening service.
This is excellent news for .CO, of course. It gets yet another super-high-profile anchor tenant that will spread .co links (and, hopefully for the company, awareness) around the web like a virus.
Amazon acquired a.co, z.co and k.co, Overstock is of course now known as O.co, Go Daddy got x.co and Twitter is using t.co as its official URL shortener.
By my reckoning, that leaves another 19 one-letter .co names to sell. The registry’s windfall could quite easily amount to a year’s revenue for just 26 registrations.
That’s not including the numbers, of course.
Speaking of numbers, .CO also announced today that Silicon Valley incubator 500 Startups is to use 500.co, instead of 500startups.com, as its official domain.
Entrepreneurs, not URL shorteners, are .CO’s target market, vital for its longevity, so it was a very smart PR move to combine these two customer wins into one announcement.
The University of Puerto Rico has accused the manager of the .pr top-level domain of hoodwinking ICANN in order to “illegally” take over the registry.
It recently filed a lawsuit seeking to regain control of .pr, saying that the current registry operator has made an estimated $2 million from domain registrations since it somehow took over the ccTLD.
The lawsuit and other documents tell a remarkable story, one in which a University department quietly spun itself out as a private for-profit company and took .pr with it.
If the claims are true, ICANN may have made a huge screw-up by inadvertantly allowing the ccTLD to be transferred from the University into private hands.
According to an archived copy of the IANA delegation record for .pr, the ccTLD was from 1988 until about 2007 delegated to:
University of Puerto Rico
Facundo Bueso Building
Rio Piedras 00931
That’s the Sponsoring Organization. The administrative and technical contacts also stated that UPR was in charge of the domain. The contact email address was @uprr.pr, the University’s domain.
Today, the IANA record is quite different:
Gauss Research Laboratory Inc.
Calle Vesta 801
San Juan 00923
The University is no longer listed. The contact email addresses are now @nic.pr. These new details have been in effect apparently since some time in 2007.
To my eye, this looks like the stewardship of .pr was transferred from one organization, the University of Puerto Rico, to another, Gauss Research Laboratory Inc.
But IANA never produced a redelegation report – as it must when a registry changes hands – and the ICANN board never voted to redelegate.
According to a July 2007 letter (pdf) circulating this week from David Conrad, who was then IANA general manager at ICANN, the changes merely reflected a “structural reorganization” of the registry:
Since the underlying organization performing registry services for .PR did not change (it was Gauss Laboratory before and after the change), this is not considered a full redelegation, and therefore does not result in a public report with board approval.
But the University claims that long-time manager Oscar Moreno set up Gauss as a non-profit organization to handle .pr when he retired from UPR, then in 2007 changed it to the for-profit corporation that is now the designated registry manager.
A 2009 letter from UPR to ICANN general counsel John Jeffrey (pdf), which emerged on mailing lists last week, said Moreno was trying to sell his company, and the ccTLD, to a third party.
IANA, according to the letter, was fooled into thinking the University backed the transfer of control due to a letter from a faculty member who did not have the authority to authorize the changes.
The University sued Moreno in late May (pdf), seeking an injunction ordering him to transfer .pr back to UPR and to return the $2 million it believes .pr domain sales have raised since 2007.
IANA redelegations are rarely straightforward.
A recent report from the Country Code Names Supporting Organization found that ccTLD redelegations have been basically a bloody mess – unpredictable, opaque and poorly documented.
ICANN does not discuss IANA requests, but I’m currently aware of a handful of ongoing redelegation battles, such as those over Niue’s .nu and Rwanda’s .rw.
It is suspected that Irish operator IEDR is currently trying to have .ie taken away from its nominal sponsor, University College Ireland, which has put the fear into at least one registrar.