Latest news of the domain name industry

Recent Posts

TMCH turning off some brand-blocking services

Kevin Murphy, April 13, 2022, Domain Services

The Trademark Clearinghouse is closing down two of its brand protection services after apparently failing to attract and retain registry partners.

The company announced recently that TREx, its Trademark Registry Exchange, will shut down after its customers’ existing subscriptions expire, saying:

The communication that we receive from our agents, resellers, clients and other registries that we have reached out to around improving the product shows that there is currently little appetite for such a service.

TMCH said it may revive the service after the new round of new gTLDs happens.

TREx was a service similar to Donuts’ Domain Protected Marks List and others, whereby trademark owners can block their brands across a multitude of TLDs for a substantial discount on the cost of defensive registrations.

But the TMCH offering was not restricted to one registry’s portfolio. Rather, it consolidated TLDs from multiple smaller operators, including at least one ccTLD — .de — into one service.

It seems to have peaked at 43 TLDs, but lost three when XYZ.com pulled out a couple years ago.

Its biggest partner was MMX, which sold its 22 gTLDs to GoDaddy Registry last year. I’d be very surprised if this consolidation was not a big factor in the decision to wind down TREx.

I’d also be surprised if we don’t see a DPML-like service from GoDaddy before long. It already operates AdultBlock on its four porn-themed gTLDs.

The news follows the announcement late last year that TMCH will also close down its BrandPulse service, which notified clients when domains similar to their brands were registered in any TLD, when its existing subscriptions expire.

Both services leveraged TMCH’s contractual relationship with ICANN, under which it provides functions supporting mandatory rights protection mechanisms under the new gTLD program rules, but neither are ICANN-mandated services.

ICANN accidentally summons Lesser Old One in DNSSEC snafu

Kevin Murphy, April 1, 2022, Gossip

Southern California has come under the control of timeless demonic entities, plunging the Greater Los Angeles Area into a thousand years of darkness and torment, after a DNSSEC misconfiguration led to ICANN accidentally summoning a Lesser Old One into the mortal realm.

“I can confirm that there was an RRSIG glitch during the ceremony to sign the root zone ZSK for 2022Q2 and introduce HSM6W at our secure facility in El Segundo, California, today,” an ICANN spokesperson said.

“A downstream KSK misconfiguration was inadvertently introduced into the IMRS, resulting in a cascading Trust Anchor collapse across the entire constellation,” he said.

“This unfortunately led to the opening of a transdimensional portal to the Lost City of R’lyeh and the manifestation of an entity our initial analysis indicates may be Baoht Z’uqqa-Mogg, High Commander of the Armies of the Damned and celestial envoy for the mighty Cthulhu,” he added.

“And for some reason Facebook is down in Denver; we’re looking into that too,” the spokesperson said.

ICANN’s Seven Secret DNSSEC Key Holders were observed fleeing from the data center where the signing ceremony had been taking place, casting aside their cowls and robes and clawing at their eyes and skin, according to local reports.

They were pursued by a wailing, forty-foot-tall scorpion-faced lizard monster, emerging from a blinding disc of purple hellfire and bent on subjugating the human race to millennia of torment, local TV station Fox Action 5 Shooty Shooty Bang Bang News reported from the scene, shortly before its news chopper was plucked from the sky by a blistered tentacle and tossed into Z’uqqa-Mogg’s slavering, beak-like mandibles.

The entity was then seen slamming its cloven hoof into the ground and performing an obscene incantation, opening a rift through which poured a horde of bloodthirsty, crab-headed minions that proceeded to swarm through the streets of LA, devouring all in their path.

“This is the one thing we hoped would not happen,” the ICANN spokesperson admitted.

In response to the crisis, which has so far resulted in the deaths of millions and the enslavement into madness of half the US west coast, ICANN’s Security and Stability Advisory Committee has formed an ad-hoc working group to devise possible strategies to banish the Old One to its cthonic netherworld.

It’s planning to deliver an initial draft of its report no later than September 2023, after which its work will be opened to the Whatever’s-Left-Of-The-Public Comment process.

What to make of this strange trend in new domain regs?

Kevin Murphy, March 18, 2022, Domain Registries

Are people getting the shortest domain possible when they register in a new gTLD?

Every month uber-registry Donuts publishes data about its portfolio, such as which gTLDs are most popular, in which region, what its most popular premium names are, and what keywords are most commonly registered at the second-level.

For the past few months, I’ve noticed what may be considered an unusual trend — many of the most popular SLD keywords are already gTLDs in their own right, suggesting registrants may not be getting their optimal domain.

The top 10 second-level keywords in February were: today, meta, letter, first, digital, verse, online, club, life, and home.

Put a dot in front of them, and five are also gTLDs — .today, .digital, .online, .club, and .life — some of which Donuts actually manages. One of them, .home, has multiple outstanding applications but has been essentially banned by ICANN due to high levels of name collision.

It’s even more noticeable in January’s numbers, with seven gTLD matches — online, life, digital, free, green, shop, world — in the top 10 SLD keywords.

In December there are six — today, group, online, digital, world and life. In November, four — online, digital, life, group. In October, six — digital, online, life, tech, shop, group.

It shouldn’t be hugely surprising that there’s a crossover between gTLD strings and popular SLD strings — one of the ways Donuts and others picked their gTLDs was by scouring the .com zone file for the most-common SLD endings.

The idea was that if Peter owned, or was thinking of registering, peterspickledpeppersonline.com, he might reasonably want to upgrade to the shorter peterspickledpeppers.online.

Donuts consistently says that the domains it sells are 20% shorter than domains registered in .com over the comparable period.

But its data suggests that this they’re not always getting their optimal domain. People are registering in new gTLDs, but they’re often not using the gTLD that would make their overall domain shorter.

I wonder why this is.

Cost could certainly be a factor. There’s not a massive amount of difference between a .online and a .live, and both are typically more expensive than .com, but it might be an issue for registrants on tight budgets.

It seems more likely that a lack of awareness among registrants may be the main issue — they don’t know the full breadth of options available to them (hell, even I don’t, and this is my job).

Registrars’ name spinners aren’t always helpful raising this awareness.

I typed the string “peterspickledpeppersonline” into the storefronts of seven popular registrars, all of which carry new gTLDs, and found that two of them didn’t offer peterspickledpeppers.online among their suggestions at all.

On some, the domain was way down the list, after far less-relevant suggestions, even though it is shorter and carries a higher price.

Namecheap boss goes nuclear on Russian customers

Namecheap has banned all Russians from its services in a comprehensive, surprising, and unprecedented expression of solidarity with Ukraine, the invaded country where most of its support staff are based.

CEO Richard Kirkendall said yesterday that Namecheap, which has over 14 million domains under management, “will no longer be providing services to users registered in Russia”, in an email to Russian customers.

Namecheap says it has over 1,000 employees in Ukraine.

It uses a company there called Zone3000 for its English-language customer support, from three locations across the country, mostly in Kharkiv, one of the cities that has been particularly affected by the Russian invasion over the last five days.

Kirkendall has given Russian customers until March 6, one week from the time of the email, to move to another registrar.

The email was posted online, and I’ve confirmed with Namecheap that it’s accurate. Kirkendall said:

Unfortunately, due to the Russian regime’s war crimes and human rights violations in Ukraine, we will no longer be providing services to users registered in Russia. While we sympathize that this war may not affect your own views or opinion on the matter, the fact is, your authoritarian government is committing human rights abuses and engaging in war crimes so this is a policy decision we have made and will stand by.

If you hold any top-level domains with us, we ask that you transfer them to another provider by March 6, 2022.

I’m told the words “any top-level domains” just means ‘any domains in any TLDs’.

Kirkendall went on to say that anyone using Russian and Belarusian ccTLDs — .ru, .xn--p1ai (.рф), .by, .xn--90ais (.бел), and .su — will no longer be able to use Namecheap’s email or hosting services.

After some negative replies, accusing Namecheap of going too far, Kirkendall wrote:

We haven’t blocked the domains, we are asking people to move. There are plenty of other choices out there when it comes to infrastructure services so this isn’t “deplatforming”. I sympathize with people that are not pro regime but ultimately even those tax dollars they may generate go to the regime. We have people on the ground in Ukraine being bombarded now non stop. I cannot with good conscience continue to support the Russian regime in any way, shape or form. People that are getting angry need to point that at the cause, their own government. If more grace time is necessary for some to move, we will provide it. Free speech is one thing but this decision is more about a government that is committing war crimes against innocent people that we want nothing to do with.

It’s by some way the strongest stance anyone in the domain industry has yet taken on the war in Ukraine.

Namecheap intends to issue a formal statement outlining its position later today.

UDRP cases soar at WIPO in 2021

Kevin Murphy, February 15, 2022, Domain Policy

The World Intellectual Property Organization has released statistics for cybersquatting cases in 2021, showing one of the biggest growth spurts in UDRP’s 22-year history.

Trademark owners filed 5,128 UDRP complaints last year, WIPO said, a 22% increase on 2020.

There have been almost 56,000 cases since 1999, covering over 100,000 domains names, it said.

The number of annual cases has been growing every year since 2013, its numbers show.

WIPO took a punt that the increase last year might be related to the ongoing coronavirus pandemic, but didn’t really attempt to back up that claim, saying in a release:

The accelerating growth in cybersquatting cases filed with the WIPO Center can be largely attributed to trademark owners reinforcing their online presence to offer authentic content and trusted sales outlets, with a greater number of people spending more time online, especially during the COVID-19 pandemic.

The number of domains hit by UDRP that include strings such as “covid” or “corona” or “vaccine” are pretty small, amounting to just a few dozen domains across all providers, searches show.

The growth does not necessarily mean the total number of UDRP cases has increased by a commensurate amount — some of it might be accounted for by WIPO winning market share from the five other ICANN-approved UDRP providers.

It also does not indicate an increase in cybersquatting. WIPO did not release stats on the number of cases that resulted in a domain name being transferred to the complaining trademark owner.

“It’s not our fault!” — ICANN blames community for widespread delays

Kevin Murphy, February 14, 2022, Domain Policy

ICANN may be years behind schedule when it comes to getting things done on multiple fronts, but it’s the community’s fault for making up rubbish policies, bickering endlessly, and attempting to hack the policy-making process.

That’s me paraphrasing a letter sent last week by chair Maarten Botterman to the Registries Stakeholder Group, in which he complained about the community providing “ambiguous, incomplete, or unclear policy recommendations”.

RySG chair Samantha Demetriou had written to Botterman (pdf) in December to lament the Org and board’s lack of timely progress on many initiatives, some of which have been in limbo for many years.

Policies and projects related to Whois, new gTLDs and the Independent Review Process have been held up for a long time, in the latter case since 2013, she wrote, leading to community volunteers feeling “disempowered or discouraged”.

As I recently reported, ICANN has not implemented a GNSO policy since 2016.

The lack of board action on community work also risks ICANN’s legitimacy and credibility, Demetriou wrote.

But Botterman’s response (pdf), sent Thursday, deflects blame back at the community, denying that the delays are “simply because of failure at the level of the organization and Board.”

He wrote:

we need to continue to find our way forward together to address the challenges that affect the efficiency of our current decision-making processes, including, for example, ambiguous, incomplete, or unclear policy recommendations, the relitigation of policy issues during implementation, and the use of the review process to create recommendations that should properly be addressed by policy development

In other words, the community is providing badly thought-out policy recommendations, continuing to argue about policy after the implementation stage is underway, and using community reviews, rather than the Policy Development Process, to create policy.

The RySG, along with their registrar counterparts, put their concerns to the board at ICANN 72 in October, warning of “volunteer burnout” and a “chilling effect” on community morale due to board and Org inaction.

At that meeting, director Avri Doria presented staff-compiled stats showing that across five recent bylaws-mandated community reviews (not PDPs), the board had received 241 recommendations.

She said that 69% had been approved, 7% had been rejected, 18% were placed in a pending status, and 6% were “still being worked on”.

CEO Göran Marby provided a laundry list of excuses for the delays, including: reconciling differing community viewpoints, the large number of recommendations being considered, the potential for some recommendations to break ICANN bylaws, sensitivity to the bottom-up nature of the multi-stakeholder process, lack of staff, and the extra time it takes to be transparent about decision-making.

Just this week, ICANN has posted eight job listings, mostly in policy support.

In his letter last week, Botterman pointed to a “Prioritization Framework”, which is currently being piloted, along with further community conversations at ICANN 73 next month and a “thought paper” on “evolving consensus policies”.

Because why fix something when you can instead create another layer of bureaucracy and indulge in more navel-gazing?

PIR to offer industry FREE domain abuse clearinghouse

Kevin Murphy, February 11, 2022, Domain Registries

The DNS Abuse Institute will soon launch a free service designed to make it easier to report abuse and for registries and registrars to act upon it.

The Institute, which is funded by .org manager Public Interest Registry, is working on a system provisionally called CART, for Centralized Abuse Reporting Tool, an ambitious project that would act as a clearinghouse for abuse reports across the industry.

The plan is to offer the service for free to reporters and registrars alike, with a beta being offered to registrars late next month and a public launch hopefully before ICANN 74 in June.

DNSAI director Graeme Bunton said that CART is meant to solve the “mess” of current abuse reporting systems.

For abuse reporters, the idea is to give them a one-stop shop for their reports, across all gTLDs and registrars. CART would take their complaints, normalize them, furnish them with additional information from sources such as Whois records and domain block-lists, and shunt them off to the registrar of record.

“Registrars get boatloads of abuse reports every day,” Bunton said. “Hundreds to thousands. They’re often duplicative, often unevidenced — almost always. There’s no standardization. So they’re having to spend a lot of time reading and parsing these abuse reports.”

“They’re spending a huge amount of time triaging tickets that don’t make the internet any better,” he said. “It felt like trying to solve this problem across every individual registry and registrar was not going to work, and that a centralizing function that sits in the middle and absorbs a lot of the complexity would make a real difference, and we’ve been working towards that.”

CART reporters would be authenticated, and their reports would be filed through forms that normalized the data to make them easier for registrars to understand. There will be “evidence requirements” to submit a report.

“It’s a common lament that the abuse@ email that registrars have to publish are filled with garbage,” Bunton said. “This is intended to clean that up, as well as make it easier for reporters.”

Registrars will be able to white-label these forms on their own sites, replacing or adding to existing reporting mechanisms, which will hopefully drive adoption of the tool, Bunton said.

Registrars will be able to use an API to pull the abuse feed into their existing ticketing workflows, or simply receive the reports via email.

The plan is to send these enhanced reports to registrars’ publicly listed abuse@ addresses, whether they opt into the CART system or not, Bunton said.

One feature idea — possibly in a version 2 release — is to have a reputation-scoring function in which registrars can flag reporters as reliable, facilitating on-the-fly “trusted notifier” relationships.

While the DNSAI is focusing to the industry definition of “DNS abuse” — phishing, pharming, malware, botnets and a subset of spam — the plan is to not limit reporters to just those categories.

Copyright infringement claims, for example, would be acceptable forms of abuse report, if the registrar enables that option when they embed the CART forms on their own sites.

CART will most likely be renamed to something with “better mass-market appeal” before it launches, Bunton said, but there will be no charge to reporters or registrars.

“This is all free, with no plans to do cost-recovery or anything like that,” he said.

While Bunton didn’t want to comment, I think it’s unlikely that these projects would be going ahead, at least not for free, had PIR been turned into a for-profit company under its proposed acquisition by Ethos Capital, which was blocked by ICANN a couple of years ago.

A second project DNSAI is working on is called Intelligence.

This will be somewhat similar to ICANN’s own Domain Abuse Activity Reporting (DAAR) system, but with greater granularity, such as giving the ability to see abuse trends by registry or registrar.

The current plan is to have a preview of Intelligence available in June, with a launch in July.

Post-lockdown blues hit Tucows’ growth

Kevin Murphy, February 11, 2022, Domain Registrars

Tucows’ domain business was pretty much flat in the fourth quarter and full-year 2021, as the company hit the trough following the spike of the pandemic lockdown bump.

The registrar said last night that its Domain Services business saw new registrations down or flat in both wholesale and retail channels, even when compared to pre-pandemic levels.

The company said (pdf) it ended the year with 25.2 million domains under management, down from 25.4 million a year earlier. The total number of new, renewed or transferred-in domains was 17.4 million, down from 18.2 million.

For the fourth quarter, the total new, renewed or transferred-in domains was 4 million, compared to 4.3 million a year earlier.

In prepared remarks (pdf), CEO Elliot Noss said that wholesale-segment registrations were down 6% to 3.7 million in Q4 and new registrations were down 27% from 2020’s pandemic-related “outsized volumes”.

In retail, total new, renewed and transferred registrations for the quarter were just over 310,000, down 16%, he said. New registrations were down 21% year over year.

The domains business reported revenue of $61.4 million in the fourth quarter, down from $61.8 million in the year-earlier period.

Domain revenue from wholesale was down to $47.1 million from $47.5 million. Retail was down to $8.7 million from $9.2 million. EBITDA across both channels was $11.6 million, down from $12.1 million.

The renewal rates for wholesale and retail were a more-than-respectable 80% and 85% respectively.

Some of the declines can be attributed to the pandemic-related bump Tucows and other registrars experienced in 2020.

Margins had been impacted a bit by the acquisition of UNR’s back-end registry business, the integration of which Noss said has now been fully completed.

For the full company, including non-domain businesses such as mobile and fiber, revenue for the year was down 2.2% at $304.3 million and net income was down 41.7% at $3.4 million.

The company also announced it has renewed its $40 million share buyback program.

Verisign and PIR join new DNS abuse group

Kevin Murphy, February 9, 2022, Domain Policy

The domain name industry has just got its fourth (by my count) DNS abuse initiative, with plans for work on “trusted notifier” programs and Public Interest Registry and Verisign as members.

topDNS, which announced itself this week, is a project out of eco, the German internet industry association. It said its goals are:

the exchange of best practices, the standardisation of abuse reports, the development of a trusted notifier framework, and awareness campaigns towards policy makers, decision-makers and expert groups

eco’s Thomas Rickert told DI that members inside and outside the industry had asked for such an initiative to combat “the narrative that industry is not doing enough against an ever-increasing problem”.

He said there’s a “worrying trend” of the domain industry being increasingly seen as an easy bottleneck to get unwelcome content taken down, rather than going after the content or hosting provider.

“There is not an agreed-upon definition of what constitutes DNS abuse,” he said.

“There are groups interested in defining DNS abuse very broadly, because it’s more convenient for them I guess to go to a registrar or registry and ask for a domain takedown rather than trying to get content taken down with a hosting company,” he said.

topDNS has no plans to change the definition of “DNS abuse” that has already been broadly agreed upon by the legit end of the industry.

The DNS Abuse Framework, which was signed by 11 major registries and registrars (now, it’s up to 48 companies) in 2019 defines it as “malware, botnets, phishing, pharming, and spam (when it serves as a delivery mechanism for the other forms of DNS Abuse)”.

This is pretty much in line with their ICANN contractual obligations; ICANN itself shudders away from being seen as a content regulator.

The big asterisk next to “spam” perhaps delineates “domains” from “content”, but the Framework also recommends that registries and registrars should act against content when it comprises child sexual abuse material, illegal opioid sales, human trafficking, and “specific and credible” incitements to violence.

Rickert said the plan with topDNS is to help “operationalize” these definitions, providing the domain industry with things like best practice documents.

Of particular interest, and perhaps a point of friction with other parties in the ecosystem in future, is the plan to work on “the development of a trusted notifier framework”.

Trusted notifier systems are in place at a handful of gTLD and ccTLD registries already. They allow organizations — typically law enforcement or Big Content — a streamlined, structured path to get domains taken down when the content they lead to appears to be illegal.

The notifiers get a more reliable outcome, while the registries get some assurances that the notifiers won’t take the piss with overly broad or spammy takedown requests.

topDNS will work on templates for such arrangements, not on the arrangements themselves, Rickert said. Don’t expect the project to start endorsing certain notifiers.

Critics such as the Electronic Frontier Foundation find such programs bordering on censorship and therefore dangerous to free speech.

While the topDNS initiative only has six named members right now, it does have Verisign (.com and .net) and PIR (.org), which together look after about half of all extant domains across all TLDs. It also has CentralNic, a major registrar group and provider of back-end services for some of the largest new gTLDs.

“Verisign is pleased to support the new topDNS initiative, which will help bring together stakeholders with an interest in combating and mitigating DNS security threats,” a company spokesperson said.

Unlike CentralNic and PIR, Verisign is not currently one of the 48 signatories of the DNS Abuse Framework, but the spokesperson said topDNS is “largely consistent” with that effort.

Verisign has also expressed support for early-stage trusted notifier framework discussions being undertaken by ICANN’s registry and registrar stakeholder groups.

PIR also has its own separate project, the DNS Abuse Institute, which is working on similar stuff, along with some tools to support the paperwork.

DNSAI director Graeme Bunton said: “I see these efforts as complementary, not competing, and we are happy to support and participate in each of them.” He’s going to be on topDNS’s inaugural Advisory Council, he and Rickert said.

Rickert and Bunton both pointed out that topDNS is not going to be limited to DNS abuse issues alone — that’s simply the most pressing current matter.

Rickert said issues such as DNS over HTTP and blockchain naming systems could be of future interest.

Satirists register Joe Rogan domain to promote Covid vaccines

Kevin Murphy, January 31, 2022, Gossip

An Australian comedy troupe has registered podcaster Joe Rogan’s name as a domain as part of an anti-anti-vaccine prank.

The Chaser, which has published satire across print, radio, TV and the web for the last 20 years, picked up joerogan.com.au a few days ago and redirected it to the Aussie government’s vaccine-booking web site.

The domain was publicized in the latest edition of The Chaser’s podcast, which was rebranded “The Joe Rogan Experience” and spent most of its 20-minute runtime skewering the US comedian and martial arts commentator.

Rogan has attracted negative attention in the last week or so for his skeptical comments about Covid-19 vaccines on his podcast, which is the most-listened podcast on Spotify, the platform with which he has an exclusive $100 million distribution deal.

Musicians Neil Young and Joni Mitchell have pulled their work from Spotify in protest at Rogan’s words, which they said were dangerous.

Rogan has since tried to clarify his comments and editorial policy, and Spotify has said it will start to provide links to reliable Covid-19 information alongside podcasts that address the topic.