Latest news of the domain name industry

Recent Posts

Should brands get a new gTLD round to themselves? Twitter thinks so

Kevin Murphy, October 20, 2015, Domain Policy

Twitter wants to get its hands on some new gTLDs but doesn’t want to wait.
Having missed the first round of new gTLD applications back in 2012, the company is now keen on getting .twitter and other strings both branded and generic.
“We’re interest in round two,” Twitter trademark counsel Stephen Coates said as ICANN’s business constituencies met the board of directors today.
“We have several interesting opportunities to develop around that space,” he said. “We are interested in both brands and generics.”
The problem for Twitter, and every other would-be gTLD applicant, is that ICANN isn’t even talking in broad terms about when the next round will be.
The absolute minimum that must happen is that ICANN must complete a review of round one, focusing on “Competition, Consumer Trust and Consumer Choice”. This CCT review is mandated by ICANN’s Affirmation of Commitments with the US government.
Almost three years after the first round opened, the volunteer team that will carry out the CCT review has not even been assembled yet.
There are a number of other factors that may or may not wind up on the critical path — such as reviews of rights protection mechanisms and security and stability at the DNS root.
Coates said he would like a “bifurcated” review process leading to two separate second application rounds.
“I would advocate for bifurcating the review process, which I think is very important, especially around RPMs,” he said. “But also bifurcating the round process, treating dot-brands differently than generic names.”
I think this outcome is unlikely.
Application rules that give preference to one type of application over another invite exploitation. It happened in the 2003 sponsored TLD round and it’s happening with “community” and “Specification 13” applications in the current round too.

Time for .bloomberg after Twitter hoax?

Could the fake Bloomberg story about Twitter being acquired act as an impetus for the company to activate its mostly dormant dot-brand gTLD?
Twitter shares yesterday reportedly spiked as much as 8% on the “news” that it was the target of a $31 buyout bid.
The story was published on bloomberg.market, a cybersquatted domain hosting a mirror of the real Bloomberg web site.
While it was reportedly quite sloppily written, it nevertheless managed to convince at least one US cable news network to run with it, one reporter even tweeting the bogus link to his followers.
The story was quickly outed as a fake and within a few hours Rightside, the .market registry as well as owner of its registrar, eNom, suspended the domain for breaching its terms of service.
Rightside wrote in a blog post:

it pains us so greatly that, in the early stages when so many people are forming their first impressions of the new TLD program, these numerous positive examples are sometimes overshadowed by the malicious practices and behaviors of a very small group of people.

Bloomberg’s not at fault here, of course. No company should be expected to defensively register its trademark in every one of the 1,000+ TLDs out there right now.
But could the hoax persuade it to do something of substance with its .bloomberg gTLD, perhaps taking a leaf out of the BNP Paribas playbook?
Bloomberg has been populating its dot-brand with hundreds of domains since May — both the names of its products and keywords related to industries it’s known for covering — but currently they all seem to redirect to existing web sites in .com or .net.
It’s long been suggested by proponents of new gTLDs that dot-brands can act as a signal of legitimacy on the web, and that’s the attitude banks such as Barclays and BNP Paribas seem to be taking right now.
Could .bloomberg be next?

Turkey blocks Google DNS in Twitter crackdown

Kevin Murphy, March 23, 2014, Domain Policy

The Turkish government has reportedly blocked access to Google’s public DNS service from with its borders, as part of its recently instituted censorship of Twitter.
According to local reports, the IP addresses 8.8.8.8 and 8.8.4.4 — Google’s public DNS servers — were banned after they became widely used to circumnavigate blocks on Twitter’s domain names.
Turkish prime minister Recep Tayyip Erdogan last week vowed to “wipe out” Twitter, after the company refused to take down tweets criticizing his government over corruption allegations ahead of an election next week.
Twitter is encouraging Turkish users to use SMS to send tweets instead. Many Turks are also turning to VPNs to evade this bizarre piece of Draconian censorship.

Twitter starts supporting (some) new gTLDs

Kevin Murphy, March 7, 2014, Domain Tech

Twitter has started recognizing new gTLDs on its web page and on Tweetdeck.
As of some point in the last 48 hours, you can type something like “nic.berlin” or “fire.plumbing” in a tweet and Twitter will automatically turn it into a clickable link.
The switcheroo seems to have happened in the last two days, as this conversation may illustrate.
But there seems to be some delay — about a month, by my reckoning — in the support.
Domains such as nic.sexy, which is in a TLD delegated November 14, become clickable, but domains in more recent delegations such as .okinawa, which hit the root on Wednesday, are not.
Going back through the DI PRO Calendar, it seems that any TLD delegated on February 5 or earlier gets clickable links in Twitter and those delegated over the last four weeks do not.
I’m not sure why TLDs delegated in the last month are not supported, but I imagine it could be an annoyance during registries’ pre-launch marketing.
It’s difficult to overestimate how important application support is for the new gTLD program.
If new gTLDs don’t look like web addresses, there’s going to be a big barrier to adoption. A .link domain that isn’t clickable isn’t much use and nobody wants to have to copy-paste URLs.
Support for new gTLDs for Twitter’s 232 million active users is a big step along the road to universal acceptance of all TLDs, which ICANN has identified as a problem.

Twitter files UDRP over twitter.org

Kevin Murphy, January 14, 2013, Domain Policy

Twitter has filed a cybersquatting complaint over the domain name twitter.org, which is currently being used for one of those bogus survey scam sites.
The domain has been registered since October 2005 — six months before Twitter was created — but appears to have changed hands a number of times since then.
It’s been under Whois privacy since mid-2011, but the last available unprotected record shows the domain registered to what appears to be Panama-based law firm.
Hiding ownership via offshore shell companies is a common tactic for people cybersquatting high-profile brands.
The UDRP complaint, which looks like a slam-dunk to me, has been filed with WIPO.

Twitter typosquatters fined £100,000

Kevin Murphy, February 16, 2012, Domain Policy

Two typosquatters have been fined £100,000 ($156,000) by the UK premium rate phone services regulator.
PhonepayPlus said today that the owners of the typos wikapedia.com and twtter.com, both Dutch companies, were issued the fines for violating its Code of Practice.
R&D Media Europe and Unavalley use the now depressingly commonplace practice of tricking visitors with the promise of iPad prizes into signing up for bogus SMS services at ridiculous fees.
They’ve both been ordered to refund disgruntled customers’ fees.
PhonepayPlus has no powers to take away domain names, of course, so both typos are still active, albeit not no longer mimicking the Wikipedia or Twitter look-and-feel.
The regulator did however issue clear guidance that typosquatting is against its rules, stating:

This guidance reminds PRS [premium rate service] providers that they are responsible for all their digital promotions and, if they use marketing firms that mislead consumers through typosquatting, they will be in breach of the Code of Practice.

A Facebook attorney said last year that typos of high-traffic sites, such as facebok.com, could expect to get 250 million visits a year.

ICANN advertises new gTLDs on Twitter

Kevin Murphy, January 30, 2012, Domain Policy

ICANN has really ramped up the social marketing of its new generic top-level domain program for the last few weeks, and today it started plugging new gTLDs with some Twitter advertising.
It’s bought some “Promoted Tweets”, which means some Twitter users will see a designated ICANN tweet even if they don’t already follow ICANN.
Here’s an example captured by @andrewhennigan.

The Promoted Tweets ad service is bid-based and priced on a cost-per-engagement basis, so advertisers only pay when they get a reply, retweet, follow, etc. Reportedly, there’s a $15,000 minimum commitment.
Judging by Twitter noise today, I’m guessing that today ICANN is promoting its new gTLDs Twitter chat, which is happening at 1600 UTC tomorrow with the hashtag #newgtlds.

Five amusing Twitter accounts to follow

Kevin Murphy, January 29, 2012, Gossip

One of the good things about Twitter is that there’s no Whois (yet), which makes it fertile ground for pseudonymous humor.
Here are the five bogus domain humor tweeters I find amusing.
No, before you ask, none of these are me. I’ve only written one thing under a fake identity since I launched DI.
@BobRecstrum
Bob tweets in-character as a “heightened” version of ICANN CEO Rod Beckstrom.
He’s basically a globe-trotting narcissist hippy with delusions of grandeur and an obsessive penchant for taking panoramic iPhone photos of himself shaking hands with world leaders.
His avatar, inexplicably, is Sam Rockwell as Zaphod Beeblebrox.
Bob Recstrum
@thereforeICANN
This account, which usually offers a satirical view of ICANN proceedings, typically peaks during its thrice-yearly public meetings.
Whoever is responsible for this account has clearly been around ICANN for a while – s/he goes to the meetings, reads the web site, and knows what’s coming before it happens.

@dns_borat
This one’s for the geeks. Imagine everyone’s favorite Kazakhstani roving reporter, but he’s a DNS administrator.
That’s pretty much it really.

@DotSucks
This account was only created in the last few days. I’d hazard a guess that it has links to the adult entertainment industry, due to the obvious anti-.xxx sentiment on display.
The premise, of course, is that new gTLDs are basically a massive shakedown. Shows promise.

(I’ll note that the first time I heard of .sucks back in 2000 when it was floated by then-chair of ICANN Esther Dyson, ironically now one of the new gTLD program’s highest-profile critics.)
@domainhumor
This one is slightly different for two reasons: 1) I know who it is. 2) He/she has not tweeted much funny stuff lately.
I follow it in the hope that this might change one day.

Twitter co-founder to headline DOMAINfest

Kevin Murphy, November 9, 2011, Domain Services

Twitter co-founder Biz Stone is to keynote the 2012 DOMAINfest Global conference, organizer Oversee.net has just announced.
It sounds rather like his speech will focus on the “inspirational story” angle, rather like Go Daddy founder Bob Parsons’ keynote at the 2011 show.
According to the agenda, Stone will “share his thoughts on Twitter’s future and the evolving world of social media”.
Judging by the other speakers and panelists lined up, it’s an SEO-heavy agenda, but there will be a workshop entitled “Everything You Need to Know about New TLDs”.
For the new gTLDs panel, so far only Neustar’s Ken Hansen is listed as a confirmed speaker. I don’t expect that state of affairs to last long.
The show will be held at the Fairmont Miramar in Santa Monica, California, from January 31 to February 2 next year. Prices start at $1,195 if registering before December 31.

.xxx reveals new gTLD support problems

Kevin Murphy, August 5, 2011, Domain Tech

It’s late 2012. You’ve spent your $185,000, fought your way through objections, won your contention set, and proved to ICANN that you’re technically and financially capable of running a new generic top-level domain.
The registry contracts have been signed. But will your gTLD actually work?
The experiences of .xxx manager ICM Registry lately suggest that a certain amount of outreach will be needed before new gTLDs receive universal support in applications.
I’ve encountered three examples over the last few days of .xxx domain names not functioning as expected in certain apps. I expect there will be many more.
Skype. Type http://casting.com into a chat window and Skype will automatically make the link clickable. Do the same for the .xxx equivalent, and it does not.
Android, the Google mobile platform. I haven’t tested this, but according to Francesco Cetaro on Twitter, unless you manually type the http:// the domain doesn’t resolve.
TweetDeck, now owned by Twitter. It doesn’t auto-link or auto-shorten .xxx domains either, not even if you include the http:// prefix.
This problem is well known from previous new gTLD rounds. ICANN even warns applicants about it in the Applicant Guidebook, stating:

All applicants should be aware that approval of an application and entry into a registry agreement with ICANN do not guarantee that a new gTLD will immediately function throughout the Internet. Past experience indicates that network operators may not immediately fully support new top-level domains, even when these domains have been delegated in the DNS root zone, since third-party software modification may be required and may not happen immediately.
Similarly, software applications sometimes attempt to validate domain names and may not recognize new or unknown top-level domains.

As a 10-year .info registrant, I can confirm that some web sites will still sometimes reject email addresses at .info domains.
Sometimes this is due to outdated validation scripts assuming no TLD is longer than three characters. Sometimes, it’s because the webmaster sees so much spam from .info he bans the whole TLD.
This is far less of an issue that it was five or six years ago, due in part to Afilias’s outreach, but just this week I found myself unable to sign up at a certain phpBB forum using my .info address.
I understand ICM has also been reaching out to affected app developers recently to make them aware that .xxx now exists in the root and has resolvable domains.
ICANN also has released code in C#, Java, Perl, and Python (though not, annoyingly, PHP) that it says can be easily dropped into source in order to validate TLDs against the live root.
The last beta was released in 2007. I’m not sure whether it’s still under development.
(UPDATE: CentralNic CTO Gavin Brown has knocked up a PHP implementation here.)