Alibaba, Name.com among new RDRS opt-ins

Eleven registrars representing millions of domain names signed up to support ICANN’s Registration Data Request Service last month. One registrar dropped out.

One of Chinese tech giant Alibaba’s registrars was among the additions. Alibaba Cloud Computing (Beijing), which has 2.6 million names under management, is a notable addition given that one of its sister registrars was recently hit with an ICANN Compliance action due to alleged abuse inaction.

Also opting in to the Whois band-aid service were Identity Digital’s Name.com (2.2 million names), three of its sister companies, and Newfold Digital’s Register.com (1.5 million names). Nominalia, P.A Vietnam, and Ubilibet also signed up.

Realtime Register dropped out of the voluntary service, the third registrar to opt out since RDRS launched in Novemeber.

ICANN says its coverage is now 57% of the total gTLD domains out there, up from 55% in February. It has 86 registrars on-board in total, including most of the largest.

RDRS is a two-year pilot that offers people who want access to private Whois records, largely intellectual property interests and law enforcement, a simpler way to connect with the registrars holding that data.

Comment Tagged: ICANN, privacy, rdrs, whois

.my domains to be sold globally next month

The .my namespace is to be opened up to international registrants next month under a deal between the Malaysian registry and Caymans-based Internet Naming Co, according to INCO’s CEO.

Shayan Rostam said that MYNIC will continue to be the registry for .my, but that INCO will take on operations outside Malaysia. The deal will allow non-Malaysians to register .my domains for the first time, he said. Currently, some registrars offer local presence services to get around the rules.

INCO already runs a portfolio of gTLDs, the initial batch acquired from UNR a few years ago, and adding .my should bring the ccTLD to a wider range of registrars. There’s going to be a new Registry-Registrar Agreement that is “less restrictive” than the old one, Rostam said.

.my has been around since 1987 and currently has about 313,000 domains under management, split roughly 50:50 between the second-level under .my and third level under .com.my. There are also lesser-used spaces such as .org.my and .net.my.

Rostam said the third-level spaces will still be reserved for Malaysians, but that no local nexus will be required under the second-level. It’s a similar idea to how Colombia’s .co was operated when it relaunched in 2010.

The TLD is of course potentially attractive because it’s an English word commonly used in domains, albeit usually at the start of the name rather than the end. According to my database, “my” is the most commonly-registered ccTLD-match two-letter domain among dot-brands.

Rostam said that he expects to start the relaunch with an Early Access Period, with prices starting at about $25,000, in late May, with full general availability in June.

Renewal pricing in GA is expected to be around the $30 mark — substantially cheaper than current retail prices — but registrars are expected to run first-year promotions in the sub-$10 area,

There will also be a list of premium-priced domains that could pump the pricing up to between $100 and $10,000 per year.

There’s no formal sunrise period — ccTLDs are not governed by ICANN rules and .my has of course been around for almost 40 years — but brand-protection registrars have been given special early access in case they have clients that want protection, Rostam said.

Under a separate deal, INCO has also taken over management of .forum and .feedback on behalf of two of Jay Westerdahl’s companies, Rostam confirmed.

Comment Tagged: .feedback, .my, forum, inco, internet naming co, mynic

The Swiss can register .swiss domains from next week

The Swiss government is relaxing the registration rules for its .swiss gTLD so that regular people will be able to register names there from next week.

Previously available only to registered legal entities in Switzerland, from April 24 any Swiss person at home or abroad will also be able to buy .swiss domains.

The TLD will still be heavily regulated, however. You’ll only be able to register domains that match your own name or the name that you are commonly known by. You won’t be able to register common family names without an accompanying given name.

Swiss people living elsewhere will be able to register, but will be forbidden from using their names for commercial purposes.

.swiss lives alongside the country’s official ccTLD, .ch, which is derived from the Latin name for the multilingual nation.

While .swiss is perhaps more internationally recognizable, to date it has attracted only about 26,000 registrations, compared to the 2.5 million in decades-old .ch.

Comment Tagged: .swiss

.ai up to 425,000 domains

The .ai registry has provided its latest, sporadic update to its registration numbers, showing that Anguilla’s ccTLD continues to be wildly popular compared to the country’s size.

It’s grown from 353,928 domains on December 20 to 425,060 domains on April 12, according to the registry’s web site.

That’s an increase of 71,132 since the last update, or about 620 a day. The zone is on track to have doubled in size over 12 months by the middle of the year.

.ai has a relatively high price point — about $70 a year but with a two-year minimum initial registration — suggesting that registrants either intend to use their domains or are fairly confident they can turn a profit by selling them to somebody who will.

Comment Tagged: ai

A million “free” .music domains up for grabs

The new .music gTLD registry says it will give away up to one million first-year domains over the next five weeks as part of its launch program, but there are of course plenty of catches.

DotMusic says the domains are available to what it calls “Music Community Member Organizations” — think record labels and the like — until May 24 or it reaches a million names, whichever comes first.

With not much more than a month to get on board and a fairly complex, multi-layered registration and verification process, it seems more likely that the promo will time out before it hits seven figures.

.music is a “community” gTLD only available to entities with a nexus to the music industry. The names are only available as exact matches of music performers or professionals or the organizations they belong to.

They’re also only resolvable after the registrants verify their identities via DotMusic’s sister company, ID.music, which costs $1.99 per domain during the promotion.

It’s not exactly “free”, but compared to the usual price of defensively registering during sunrise periods, it’s an absolute bargain. DotMusic’s regular, ICANN-mandated sunrise period ended a few months ago, with dozens of domains registered by the usual suspects — the likes of Apple and Amazon.

More details on the promotion can be found here. General availability begins June 25.

Comment Tagged: .music, dotmusic, new gTLDs

D3 to get $5 million in crypto to apply for .ape gTLD

New gTLD consultancy D3 Global has inked a deal to apply for the .ape gTLD on behalf of the ApeCoin community.

The company said in a blog post that it will receive three million $APE — cryptocurrency coins currently worth about $5 million, according to Coinbase — in order to apply to ICANN for, operate and market .ape domains.

As it has with other clients, it will first launch *ape names that can only be used on the relevant blockchain to address crypto wallets and such. D3 uses an asterisk to differentiate blockchain names from real domains.

The deal came about after D3 submitted a proposal to the ApeCoin DAO. That’s a Decentralized Autonomous Organization that allows any ApeCoin holder to have a vote in the development of the ApeCoin ecosystem. They voted overwhelmingly in favor of D3’s proposal.

The DAO will receive 50% of gross revenue from *ape and .ape sales under the deal, but D3 says it will retain exclusive rights to .ape. Presumably this is because there’s no way in hell ICANN’s lawyers are going to allow it sign a registry contract with a DAO.

The business plan proposal is quite detailed for a public document, containing stuff like revenue projections that ICANN will redact from published gTLD applications. D3 reckons it could be turning over about $8 million with 90,000 registered .ape names by its fourth year.

“It’s simple, Ape Names are built by Apes, for Apes,” D3 said. As well as quite the most ludicrous quote I’ve used in a considerable while, it also happens to be Technically The Truth when said of any TLD, when you think about it.

But it’s actually a reference to the fact that a few of the D3 C-suite are owners of Bored Ape Yacht Club and Mutant Ape Yacht Club NFTs — those expensive little crypto chimp avatars that people sometimes use in their social media bios.

D3 CEO Fred Hsu apparently owns this ape picture, which is “worth” almost $37,000. Fellow co-founder Paul Stahura has a whole collection.

In other news, there’s still no cure for cancer.

1 Comment Tagged: .ape, blockchain, crypto, d3

Alibaba hit with ICANN breach notice

One of the companies in the Alibaba Group, China’s biggest registrar and one of the largest technology companies in the world, has been handed a breach notice, containing a long list of complaints including abuse failures and non-payment of fees, by ICANN Compliance.

Alibaba.com Singapore E-Commerce, one of Alibaba’s four accredited registrars, failed to respond to abuse reports and failed to respond to ICANN’s requests for information about its failure to respond to abuse reports, the notice claims.

The breach notice will likely to be the last to be sent out for claims under the current version of the Registrar Accreditation Agreement. In two days, April 5, stricter domain takedown rules approved earlier this year will become effective on all registrars.

The abuse claims seem to cover four domains in .com and .vip that look like typos that could have been used in phishing attacks.

ICANN Compliance says that Alibaba also hasn’t published the names of its officers or its redemption fees, as the RAA also requires. It says the registrar also owes it an unspecified amount of past-due fees.

The chronologies reported in the notice claim Alibaba has been giving Compliance the run-around, failing to respond to calls and emails, since early November.

All four registrars in the Alibaba Group have the same published email and phone details, but it’s not clear whether the same ones are listed in ICANN’s internal directory.

Alibaba.com Singapore is one of four accredited registrars owned by Alibaba, the Chinese e-commerce giant. The parent is not short of a bob or two, reporting revenue equivalent to $126 billion last year. It can afford to pay its ICANN fees.

Of the three Alibaba registrars that have domains the “Singapore” one is the smallest, with about 660,000 domains under management. The other two have 3.2 million and 2.6 million domains to their accreditations.

The company has been told it has until April 17 to come back into compliance or risk getting terminated.

Comment Tagged: abuse, albaba, breach, compliance, ICANN

New Vegas conference “Davos for Web3 interoperability”

Specialist new gTLD consultancy D3 is to hold a two-day conference in Las Vegas at the end of the month it’s describing as the “Davos for Web3 interoperability”.

Imposingly named Dominion, it’s due to take place at the Cesar’s Palace hotel from April 29 to 30. The theme is the interoperability between the traditional domain name system and newer blockchain-based naming systems.

Organizers says it’s invite-only, and limited to about 125 attendees, but an invitation can be requested from the event’s web site.

Keynote speakers include Lily Liu (president of the Solana Foundation) and Fred Gregaard (CEO of the Cardano Foundation) on the blockchain side of things, and Matt Overman of Identity Digital on the domain name side, as well as D3 CEO Fred Hsu.

D3 specializes in arranging gTLD applications for blockchain firms and has five announced clients so far.

Comment Tagged: blockchain, d3, dominion

ICANN content policing power grab may be dead

A move by ICANN to grant itself more formal “content policing” powers may be dead, after the community was split on the issue and governments failed to back the move.

The Governmental Advisory Committee yesterday sent comments essentially opposing, for now at least, the idea of ICANN reforming its bylaws to give it more powers over internet content, making it very unlikely that ICANN would be able to get such amendments approved by its community overseers.

The comments came a few days after ICANN extended the deadline for responses to a December 2023 consultation on whether applicants in the next new gTLD round should be able to sign up to so-called Registry Voluntary Commitments that regulate content in their zones.

RVCs would be an appendix to ICANN Registry Agreements which would commit a registry to, for example, ban certain types of registrant or certain types of content from domains in their gTLDs.

They’re basically a rebadged version of the Public Interest Commitments found in RAs from the 2012 round, in which the likes of .sucks agreed to ban cyberbullying and .music agreed to ban piracy.

But they’ve got ICANN’s board and lawyers worried, because the Org’s bylaws specifically ban it from restricting or regulating internet content. They’re worried that the RVCs might not be enforceable and that ICANN may wind up in litigation as a result.

ICANN has therefore proposed a framework (pdf) in which RVCs would be enforced by ICANN only after an agreed-upon third-party auditor or monitor found that a registry was out of compliance.

The board sent out several pages of questions to all of its Supporting Organizations and Advisory Committees in December, asking among other things whether the bylaws needed to be amended to clarify ICANN’s role, but the responses were split along traditional lines.

Registries and registrars were aligned: there’s no need for a bylaws change, because ICANN should not allow RVCs that regulate content into its contracts at all.

“ICANN should maintain its existing bylaws which exclude content from its mission, and allowing any changes to this could be a slippery slope opening ICANN to becoming a broader ‘content police’,” the Registrars Stakeholder Group said in its response, giving this amusing example:

An example of a content restriction is provided in the proposed implementation framework for .backyardchickens (e.g. no rooster-related content). Restricting rooster-related content would require a significant amount of policing, and could even prohibit valuable content that would benefit such a TLD. For example, a backyard hen farmer might want to promote the pedigree lineage of the roosters that helped sire the hens, show pictures of the roosters that were the fathers, etc. All of this could in theory be prohibited,but would also require review and subjective analysis. This would be a very slippery slope for ICANN, and a substantial departure from its mission. Restricting rooster content would then put ICANN in the place of enforcing laws that prohibit backyard roosters, rather than relying upon the competent government authorities charged with overseeing residential animal husbandry.

The Non-Commercial Stakeholders Group was more strident in its tone, even raising the possibility of legal action if ICANN went down the content policing route, saying “the best way for the Board to address content-related PICs and RVCs is to make it clear that it will reject them categorically.” It added:

The prohibition on content regulation in ICANN’s mission is extremely important and very clear. Mission limitations were a critical part of the accountability reforms that were required before ICANN would be released from US government control in 2016… NCSG will mount a legal challenge to any attempt to dilute this part of the mission.

The opposing view was held by the Business Constituency, the Intellectual Property Constituency, and the At-Large Advisory Committee, which is tasked with representing the interests of ordinary internet users.

They all said that ICANN should be able to allow content-related RVCs in registry contracts, but the IPC and BC said that no bylaws amendment is needed because the bylaws already have a carve-out that enables the Org to enforce PICs in its agreements. The ALAC said a bylaws amendment is needed.

“There is a distinction between ICANN regulating, i.e imposing ‘rules and restrictions on’ services and content, versus the registry operator voluntarily proposing and submitting to such rules and restrictions,” the IPC wrote.

“There is also a distinction between ICANN directly enforcing such rules and restrictions on third parties, i.e. registrants, versus ICANN holding a registry operator to compliance with the specifics of a contractual commitment,” it added.

The last community group to submit a response, fashionably late, was the GAC, which filed its response yesterday having reviewed all the other responses submitted so far. The GAC arguably has the loudest voice at ICANN, but its comments were probably the least committed.

The GAC said that ICANN should only go ahead with a bylaws amendment if it has community backing, but that the community currently lacks consensus. It said, “at this stage there are not sufficient elements to justify commencing a fundamental bylaws amendment to explicitly enable the enforcement of content-related restrictions”.

However, the GAC still thinks that RVCs “will continue to serve as tools for addressing GAC concerns pertaining to new gTLD applications during the next round” and that it wants them to be enforceable by ICANN, with consequences for registries found in breach.

The GAC said that it “will continue to explore options to address this important question”.

This all means that ICANN is a long way from getting the community support it would need to push through a bylaws amendment related to content policing. That’s considered one of the “Fundamental Bylaws” and can only be changed with substantial community support.

Such amendments require the backing of the Empowered Community. That’s the entity created in 2016 to oversee ICANN after it severed ties with the US government. It comprises individuals from five groups — the GAC, the GNSO, the ccNSO, the ALAC and the Address Supporting Organization.

For a fundamental bylaws amendment to get over the line, at least three of these groups must approve it and no more than one must object.

With the GNSO, given its divisions, almost certainly unable to gather enough affirmative votes, the GAC seemingly on the fence, and the ASO and ccNSO recusing themselves so far, only the ALAC looks like a clear-cut yes vote on a possible future bylaws amendment.

Perhaps that’s why ICANN chair Tripti Sinha has written to the ASO and ccNSO in the last few days to ask them whether they’d like to think again about ducking out of the consultation, giving them an extra two weeks to submit comments after the original March 31 deadline.

The ccNSO handles policy for country-code domains and the ASO for IP addresses. Both have previously told ICANN that gTLD policy is none of their business, but Sinha has urged them both to chip in anyway, because “the ICANN Bylaws govern us all”.

Comment Tagged: alac, aso, ccnso, content policing, gac, gnso, ICANN, new gTLDs, next round, pics, rvcs

Cable company unplugs its dot-brand after acquisition

A Canadian telecommunications company is turning off its dot-brand gTLD after it was acquired and its brand was deprecated.

Shaw Cablesystems has told ICANN it no longer wants .shaw, so could the registry contract kindly be terminated.

The move follows the company’s $26 billion acquisition by rival Rogers Communications, which closed a year ago. Rogers has been winding down the Shaw branding for the last nine months.

But .shaw had never actually been used by Shaw, apart from the mandatory placeholder at nic.shaw, so it was likely circling the self-termination drain anyway even without the acquisition.

Rogers also has two dot-brands — .rogers and .fido — but while it has registered a few .rogers domains over the last six months none of them have any meaningful content or redirects as yet.

The .shaw gTLD was using Identity Digital as its back-end registry services provider, having originally signed up with Afilias.

Comment Tagged: .shaw, rogers