Twitter has registered the domain name t.co, to use as a secure URL shortener.
Just minutes ago, t.co started resolving to a page containing this text:
Twitter uses the t.co domain as part of a service to protect users from harmful activity, to provide value for the developer ecosystem, and as a quality signal for surfacing relevant, interesting tweets.
The page links to a FAQ describing its current URL shortener, twt.tl.
Under this program, companies can partner with .CO to get a free premium .co domain if they commit to promote it.
TechCrunch was previously the highest-profile site to join the program, when it registered disrupt.co.
I would say getting Twitter on board definitely beats that deal.
UPDATE: Twitter published a blog post on the launch. I guess they beat me by about three minutes.
“When this is rolled out more broadly to users this summer, all links shared on Twitter.com or third-party apps will be wrapped with a t.co URL,” the firm says.
Probably too soon to say for sure, but it looks like Bit.ly is kinda screwed.
I imagine it’s a pretty hard job, largely thankless, working at ICANN. No matter what you do, there’s always somebody on the internet bitching at you for one reason or another.
The job may be about to get even more irksome for some staffers, if ICANN decides to implement new security recommendations made by risk management firm JAS Communications.
In a report published yesterday, JAS suggests that senior IANA staff – basically anyone with critical responsibilities over the DNS root zone – should be made to agree to personal credit checks, drug screening and even psych evaluations.
To anyone now trying to shake mental images of Rod Beckstrom peeing into a cup for the sake of the internet, I can only apologise.
This is what the report says:
JAS recommends a formal program to vet potential new hires, and to periodically re‐vet employees over time. Such a vetting program would include screening for illegal drugs, evaluation of consumer credit, and psychiatric evaluation, which are all established risk factors for unreliable and/or malicious insider activity and are routinely a part of employee screening in government and critical infrastructure providers.
I’ve gone for the cheap headline here, obviously, but there’s plenty in this report to take seriously, if you can penetrate the management consultant yadda yadda.
There are eight other recommendations not related to stoners running the root, covering contingencies such as IANA accidentally unplugging the internet and Los Angeles sinking into the Pacific.
Probably most interesting of all is the bit explaining how ICANN’s custom Root Zone Management System software, intended to reduce the possibility of errors creeping into the root after hundreds of new TLDs are added, apparently isn’t being built with security in mind.
“No formal requirements exist regarding the security and resiliency of these systems, making it impossible to know whether the system has been built to specification,” the report says.
It also notes that ICANN lacks a proper risk management strategy, and suggests that it improve communications both internally and with VeriSign.
It discloses that “nearly all critical resources are physically located in the greater Los Angeles area”, which puts the IANA function at risk of earthquake damage, if nothing else.
JAS recommends spreading the risk geographically, which should give those opposed to ICANN bloat something new to moan about.
There’s a public comment forum over here.
UPDATE (2010-06-13): As Michael Palage points out over at CircleID, ICANN has pulled the PDF from its web site for reasons unknown.
On the off-chance that there’s a good security reason for this, I shall resist the temptation to cause mischief by uploading it here. This post, however, remains unedited.
The massive slump in Chinese domain name registrations appears to have hit the overall domain name market significantly in the first quarter 2010, slowing its growth.
According to the latest VeriSign Domain Name Industry Brief, only one million net new domains were registered across all TLDs in the period, a paltry 0.6% increase.
There were about 193 million domains active at the end of March, up from 192 million at the start of the year.
A million might seem like a lot, until you consider that the market grew by 11 million domains in the fourth quarter and by three million in the first quarter of 2009.
The slump is certainly due to the rapid decline in .cn domains.
China’s ccTLD had about 13.4 million names at the end of last year, and only 8.8 million at the end of March. April’s numbers show the decline continued, with 8.5 million names registered.
The China drag has been caused by a combination of pricing and the Draconian new identification requirements the communist government placed on the registry, CNNIC.
Chinese registrants now have to present photo ID before they can register a domain.
VeriSign’s own .com/.net business did a decent trade in the quarter, up 7% compared to the same quarter last and 2.7% on December to 99.3 million names in total.
With registrations growing by 2.7 million per month, this means VeriSign already has more than 100 million names in its com/net database.
Energy drink maker Red Bull has somehow managed to lose a UDRP complaint over the domain name taurusrubens.com, despite having already won a lawsuit against its current registrant.
“Taurus Rubens” was the name of an air show slash performance art piece sponsored by Red Bull, performed at Salzburg airport in August 2003. There’s a clip here on YouTube.
The day before the show, an Austrian man named Reinhard Birnhuber registered taurusrubens.com and rubenstaurus.com and parked them with his ISP.
Two years later, when Red Bull got wise to the registrations, it offered Birnhuber €500 for them. He countered with a demand for a whopping €1 million.
That was in March 2005. One month later, Red Bull secured an Austrian trademark on the term “Taurus Rubens”. It then filed a UDRP complaint with WIPO.
Judging from that WIPO decision, it’s pretty clear that Birnhuber’s registrations were not entirely innocent.
Not only did he ask a ludicrous price for the domains, he also admitted to knowing about the air show when he registered them, he already owned redbullbag.com, and he gave a bunch of reasons about his plans for developing the domains that WIPO didn’t buy.
Nevertheless, because Red Bull had acquired its trademark rights years after the registrations, apparently just so it had standing under the UDRP rules, WIPO dismissed the complaint.
So Red Bull sued in an Austrian commercial court instead, and won.
Birnhuber appealed, and lost.
The court ruled that he had registered the domains in bad faith and that he should turn them over to Red Bull.
But he has apparently so far refused to do so. So Red Bull this year filed a second UDRP complaint with WIPO, asking for the domains to be transferred to it.
And, bizarrely, Red Bull lost.
WIPO this week denied the company’s complaint on the grounds that the the Austrian court’s ruling is irrelevant under UDRP rules, and that the 2005 WIPO decision should stand.
Here’s a Google translation of the relevant bits:
The panel can see in the above circumstances, no new facts or actions that would warrant a new assessment of the case. In this respect, the complainant fails to recognize that not only “new actions” to the resumption of proceedings are necessary, but this also has to be relevant.
The correct legal result is more than the enforcement of that ruling in Austria, especially as the present legal request (transfer of the domain name) covers with the sentencing order of the Austrian court. Since both parties are domiciled in Austria, is likely a priori, no specific enforcement problems arise. WIPO panels can so far do not replace the state authorities.
So, does Birnhuber get his €1 million? I doubt it. But right now he still owns taurusrubens.com.
The National Telecommunications and Information Administration, part of the US Department of Commerce, has formally announced its intent to allow the domain name system’s root servers to be digitally signed with DNSSEC.
Largely, I expect, a formality, a public comment period has been opened (pdf) that will run for two weeks, concluding on the first day of ICANN’s Brussels meeting.
NTIA and NIST have reviewed the testing and evaluation report and conclude that DNSSEC is ready for the final stages of deployment at the authoritative root zone.
DNSSEC is a standard for signing DNS traffic using cryptographic keys, making it much more difficult to spoof domain names.
ICANN is expected to get the next stage of DNSSEC deployment underway next week, when it generates the first set of keys during a six-hour “ceremony” at a secure facility in Culpeper, Virginia.
The signed, validatable root zone is expected to go live July 15.