Company to offer .sucks domains at .com prices

A new company says it is going to sell .sucks domain names, which usually retail for around $250, for as little as $12 a year.
This.sucks Inc, which says it is not affiliated with the registry, is even planning to give away 10,000 names for free.
That’s a hell of a cost to cover — the .sucks registry fee is $199 for most names or $1,999 for names, including brands, that have been marked as premium.
A 10,000-name giveaway would cost close to $2 million per year, in other words.
But This.sucks isn’t a registrar. Instead, it wants to tie its customers in to its forum and blogging platform, which will be monetized in some way.
Spokesperson Phil Armstrong told us “our plan is to create new revenue streams from different sources, including possibly advertising.” He said:

Our goal is to build a business around giving consumers affordable and easy access to these expressive web addresses, and we’ll work with different registrars to get the best price. We think we can create a large, sustainable community that over time will generate income well above the initial costs of the registrations.

There are good reasons to believe that the company is in fact the “Consumer Advocate Subsidy” provider that .sucks registry Vox Populi promised would be launching in September.
Vox Pop said in March that the subsidizing entity — which would be an unaffiliated company — would offer .sucks domains with attached forum sites for around $10 a year.
The proposed name of the service was “Everything.sucks” — a domain now owned by This.sucks Inc that redirects to this.sucks.
But Vox Pop CEO John Berard said that This.sucks was “just another registrant” and that it was “not a registry service”.
Armstrong said: “We are not related to anything Vox Populi is doing. Not sure what they are up to, but hopefully they’ll be excited about what we are doing.”
The company’s mailing address appears to be a UPS store at a small strip mall in New York state.
The this.sucks service is currently in invitation-only beta testing “for individuals with a passion”.
There’s a sister site with a virtually identical design and mission statement at this.rocks.
In a fact sheet, This.sucks says:

At both This.Rocks and This.Sucks consumers will be able to pick the name of companies, products, people and causes they want to be the focus of the commentary and conversation. With the web address of their choosing, they will be able to moderate a blog or forum to talk about the issues, initiatives and interests that stir their passions.
The goal is to encourage individual consumers to give voice to their points-­of-­view and make it easy for like­‐minded people to join the conversation, much like Reddit for general topics, Slash/Dot for technology, CafePharma in the ethical drug industry, and Glassdoor for job seekers and employers.

.food applies for dot-brand status, but you can help stop it

Scripps Networks, the company that runs the Food Network television network, wants to make .food a dot-brand gTLD that only it can use.
The company has applied to ICANN to have Specification 13 exemptions incorporated into its Registry Agreement.
Spec 13 is an add-on to the RA that dot-brands use to exempt themselves from having to sell to the public via the registrar channel, offer sunrise periods, and so on.
Scripps subsidiary Lifestyle Domains won the .food contention set after an auction with Donuts and Dot Food LLC a couple months ago.
It’s one of the applications that was identified by the Governmental Advisory Committee as a “closed generic”. Such applications were subsequently banned by ICANN.
Scripps and dozens of other applicants were given the option to change their applications to remove the single-registrant policy, to withdraw, or to carry their applications over to the next round.
But Scripps is pressing ahead regardless, claiming that if anyone else is allowed to own .food domains, all kinds of horrible things will happen. It recently told ICANN:

Internet users will benefit more from Scripps operating .FOOD because it will provide more trusted experiences. Left open to the wild west of typosquatters and cybersquatters or fraudulent users, internet users will be harmed rather than helped. With a plethora of unregulated websites in a fully open registry, the public could be misled or confused as to the origin of the content and information and rely, to their detriment, on such content.

It more recently told ICANN that it has no intention of modifying its application to comply with the GAC advice. ICANN now considers the matter “resolved”.
What’s not resolved is whether .food qualifies for Spec 13 status.
To use Spec 13, the gTLD needs to match a trademark you own, but it cannot be also be a generic string, defined as:

a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.

ICANN lawyers will make the ultimate decision about whether .food qualifies for Spec 13, but the request is open for public comment until October 29.
ICANN told DI: “ICANN has not yet made a determination as to if the application qualifies for Specification 13 and welcomes any comments from the community.”
What do you think? Should something as clearly generic as “food” be a space where only one company can register names?

URS arrives in three legacy gTLDs

The legacy gTLDs .cat, .pro and .travel will all be subject to the Uniform Rapid Suspension policy from now on.
Earlier this week, ICANN approved the new Registry Agreements, which are based on the new gTLD RA and include URS, for all three.
URS is an anti-cybersquatting policy similar to UDRP. It’s faster and cheaper than UDRP but has a higher burden of proof and only allows domains to be suspended rather than transferred.
The inclusion of the policy in pre-2012 gTLDs caused a small scandal when it was revealed a few months ago.
Critics, particularly the Internet Commerce Association, said that URS (unlike UDRP) is not a Consensus Policy and therefore should not be forced on registries.
ICANN responded that adding URS to the new contracts came about in bilateral negotiations with the registries.
The board said in its new resolutions this week:

the Board’s approval of the Renewal Registry Agreement is not a move to make the URS mandatory for any legacy TLDs, and it would be inappropriate to do so. In the case of .CAT, inclusion of the URS was developed as part of the proposal in bilateral negotiations between the Registry Operator and ICANN.

The concern for ICA and others is that URS may one day be forced into the .com RA, putting domainer portfolios at increased risk.

Viking victor in .cruise gTLD auction

Viking River Cruises has emerged as the winner of the .cruise new gTLD contention set.
It seems to have beaten Cruise Lines International Association, which has withdrawn the only competing application, in an auction.
Both applicants originally proposed a single-registrant model, in which only the registry could own domains, but changed their plans after ICANN adopted Governmental Advisory Committee advice against so-called “closed generic” gTLDs.
There was controversy in July when CLIA claimed Viking had waited too long to change its proposed registration policies.
The group accused Viking of deliberately delaying the contention set.
ICANN, however, rejected its argument, saying applicants can submit change requests at any time.
Viking’s updated application seems to envisage something along the lines of .travel, where registration is limited to credentialed industry members, defined as:

Applicant and its Affiliates, agents, network providers and others involved in the delivery of cruise-related services, including without limitation: companies that hold a license from a governmental or regulatory body to offer cruise services, companies that provide services or equipment to cruise providers, as well as consultants, resellers, engineers, etc., working with the cruise industry.

Viking is already the registry for its dot-brand, .viking.

Pritz quitz DNA

Domain Name Association boss Kurt Pritz has resigned after two years on the job.
Neustar’s Adrian Kinderis, chair of the domain industry trade group, made the announcement in an email to members yesterday.
No immediate replacement for Pritz has been named, but Kinderis said the DNA’s board wasn’t worried:

Fellow members may have concerns about the current and future management of the DNA and its many activities. Please be advised that the board and I have no serious concerns. The DNA partners with Virtual and Allegravita, two full-service external consultancies that manage all areas of operational excellence and communications. These two organizations have the full trust and support of the board, and the various DNA member committees that I’m proud to see are generating substantial and practical work product on a weekly basis.

Pritz joined the DNA in November 2013, having previously spent years in senior roles, including chief strategy officer, at ICANN.
Under his watch, the DNA has done things like adopting a webinar series for new gTLD registries and launching a site highlighting examples of new gTLD domains advertised “in the wild”, as well as carrying various advocacy work.

Africa hands coffin nails to DotConnectAfrica evaluators

The African Union and a United Nations commission have formally told ICANN that they don’t support DotConnectAfrica’s bid for .africa.
When it comes to showing governmental support, a necessity under ICANN’s rules for a geographic gTLD applications, the UN Economic Commission for Africa was DCA’s only prayer.
Company CEO Sophia Bekele had managed to get somebody at UNECA to write a letter supporting .africa back in 2008, and DCA has continued to pretend that the letter was relevant even after the entire continent came out in support of rival applicant ZA Central Registry.
During its Independent Review Process appeal, DCA begged the IRP panel to declare that the 2008 letter showed it had the support of the 60% of African governments that it requires to be approved by ICANN.
The panel naturally declined to take this view.
Now UNECA has said in a letter to the African Union Commission (pdf) dated July 20, which has since been forwarded to ICANN:

ECA as United Nations entity is neither a government nor a public authority and therefore is not qualified to issue a letter of support for a prospective applicant in support of their application. In addition, ECA does not have a mandate represent the views or convey the support or otherwise of African governments in matters relating to application for delegation of the gTLD.
…
It is ECA’s position that the August 2008 letter to Ms Bekele cannot be properly considered as a “letter of support or endorsement” with the context of ICANN’s requirements and cannot be used as such.

The AUC itself has also now confirmed for the umpteenth time, in a September 29 letter (pdf), that it doesn’t support the DCA bid either. It said:

Any reliance by DCA in its application… proclaiming support or endorsement by the AUC, must be dismissed. The AUC does not support the DCA application and, if any such support was initially provided, it has subsequently been withdrawn with the full knowledge of DCA even prior to the commencement of ICANN’s new gTLD application process.

The AUC went on to say that if DCA is claiming support from any individual African government, such claims should be treated “with the utmost caution and sensitivity”.
That’s because a few years ago African Union member states all signed up to a declaration handing authority over .africa to the AUC.
The AUC ran an open process to find a registry operator. DCA consciously decided to not participate, proclaiming the process corrupt, and ZACR won.
The new letters are relevant because DCA is currently being evaluated for the second time by ICANN’s independent Geographic Names Panel, which has to decide whether DCA has the support of 60% of African governments.
ZACR passed its GNP review largely due to a letter of support from the AUC.
If DCA does not have the same level of support, its application will fail for the second time.
The 2008 UNECA letter was the only thing DCA had left showing any kind of support from any governmental authority.
Now that’s gone, does this mean the DCA application is dead?
No. DCA has a track record of operating irrationally and throwing good money after bad. There’s every chance that when it fails the Geographic Names Review it will simply file another Request for Reconsideration and then another IRP, delaying the delegation of .africa for another year or so.

Uniregistry will stick with risky .hiv model for now

Uniregistry has agreed to take over the new gTLD .hiv from original registry dotHIV, and said it has no plans to immediately change the business model.
“We are going to maintain the status quo, at least at the start,” said Uniregistry general counsel Bret Fausett. “We will give it a year or so on our platform and then evaluate it.”
dotHIV launched last year with what I then described as “one of the strangest and riskiest business models of any new gTLD to date.”
It’s a not-for-profit TLD with an optional “Click-Counter” service that makes microdonations, pulled from reg fees, to HIV/AIDS charities whenever somebody visits a .hiv web site.
The idea hasn’t really caught on.
When dotHIV put its ICANN contract up for auction in April it had only 345 fee-paying registrations and total revenue was $83,000.
The auction, which made it plain that the buyer would not be allowed to make a profit, failed to meet the $200,000 reserve.
Uniregistry said in a press release that while it is a for-profit company, it will continue to run .hiv as a “social enterprise”.
Fausett said the gTLD’s numbers could go up once it’s on Uniregistry’s platform.
“We think this will get a natural bump when it moves to our registrar channel,” he said. “We have over 175 registrars on our platform, which is 4x the current .HIV distribution channel.”

ICANN lists the ways the new gTLD program sucked

ICANN has published an analysis of the many ways in which the first round of the new gTLD program wasted everyone’s time and money.
The 200-page “New gTLD Program Implementation Review” is essentially a long list of ways the program could have been better, along with dozens of recommendations for possible future changes.
It’s for the most part a fairly dry read, and it is probably not as comprehensive as it could be, but it will be required reading for anyone working on policy concerning, or thinking of applying during, the second application round.
It concludes, for example, that maybe there should be a right to appeal inconsistent objection rulings.
It ponders aloud whether the Community Priority Evaluation should be scrapped or revised.
It wonders whether dot-brands, or other categories of gTLD, should get their own version of the standard Registry Agreement.
There’s also some discussion about the possibility of making the evaluation stage more efficient by grouping applications by applicant or back-end service provider, which would streamline the process but complicate the prioritization queues.
I count 48 “lessons learned” in the document, but as a concise summary covering over three years of the program, it’s necessarily somewhat light on detail.
On my first read, a few omissions jumped out at me.
There’s no discussion at all of the cybersquatting component of the background screening process, for example. Nor is there any mention of Geographic Name Review shortcomings highlighted by the recent .africa Independent Review Process case.
Also, in my view the document goes way too easy on the Governmental Advisory Committee.
That’s just off the top of my head. I’m sure almost everyone who reads it will notice something lacking.
That’s why it’s now open for public comment.
The document is expected to be used as part of the review leading into the second application round, which somehow seems more distant with each passing day.

M+M lays off dozens in focus on S&M, promises profit next year

Minds + Machines has outlined its plan to refocus its business on sales and marketing, which has already resulted in a couple dozen job losses, as the latest stage of its profit runway.
The new gTLD company also outlined plans to return about half of its cash reserves — mostly obtained by losing new gTLD auctions — to its shareholders.
For the first half of the year, the London-listed company reported an EBITDA loss of $1.2 million, compared to income of $5.7 million a year earlier, on revenue that was up to $3.6 million from $113,000 in the comparable 2014 period.
The company said it is “committed to achieving its stated goal of crossing over into profitability in 2016” and blamed high operating costs for the loss, but said it has been restructuring to help it return to profit.
M+M said its headcount has been reduced from 58 to 44, but that it has added ten jobs in sales and marketing, which seems to indicate at least 24 people recently lost their jobs.
The bottom line was also affected by the fact that most of the company’s cashflow to date has been generated by auction losses, and there were more of those last year than this.
The company hit three of its six “key performance indicator” targets — domains under management market share, premium sales growth and standard sales growth — but fell short of the other three.
Average revenue per name for premiums was $184 versus a $200-$225 target, and average revenue per standard name was down from $28 to $10, largely due to a deep discount promotion for .work domains. Higher prices for soon-to-launch .law could increase the average, M+M said.
The company also announced that it will spent £15 million ($23.1 million) of its cash reserves on a share buyback.
That’s almost half of the $48.3 million is has in the bank. This time last year, M+M’s share price peaked at 12p; it’s currently at 8.55p.
The price saw a spike in May, shortly before then-chairman Fred Krueger was asked to resign by the board. Krueger has since sold off the majority of his substantial shareholding, despite explicitly saying that he would not.

Apple using apple.news as (yawn) redirect service

Apple has become the latest famous brand to deploy a new gTLD domain in the wild.
The domain apple.news has been observed this week being used as a URL redirection service by its Apple News app.
It seems that when somebody shares a link to a news site via social media, using Apple News, the app automatically shares an apple.news redirect link instead.
The domains apple.news and www.apple.news do not resolve to web sites (for me at least) but Google has already indexed over a thousand apple.news URLs. Clicking on these links transparently punts the surfer to the original news source.
UPDATE: Thanks to Gavin Brown for pointing out in the comments that apple.news does resolve if you specify “https://” rather than “http://” in the URL. The secured domain bounces visitors to apple.com/news.
It puts me in mind of .co’s original flagship anchor tenant, Twitter, which obtained t.co five years ago and continues to use it as its core URL redirection service.
It’s impossible to tell what impact t.co had on the success of .co — the domain was in use from .co’s launch — but it surely had some impact.
.news, a Rightside TLD, had just over 24,400 domains in its zone file yesterday. We’ll have to see whether Apple’s move has an impact on sales.
Taryn Naidu, Rightside’s CEO, said in a press release:

This is just the start, but Apple.NEWS is the most significant use of a new top-level domain (TLD) yet, and I am very excited at the promise and potential that this development signals. Whether they’re used as a complementary domain, content-sharing links (bit.ly, but with branding) or a simple re-direct, new domain extensions have a real and important place in every company’s overarching brand strategy today.

There’s no denying that having popular software automatically generating links for your gTLD is a great way to raise awareness.
But is this as significant as Apple actually launching a web site at apple.news, or switching from .com to .apple, and encouraging people with marketing and branding to actually type those domains into their browsers? I’m skeptical.