Latest news of the domain name industry

Recent Posts

Governments erect bulk-reg barrier to new gTLD next round

Kevin Murphy, June 12, 2025, Domain Policy

No new gTLDs should be added to the internet until ICANN develops policies addressing the abuse of bulk domain name registrations, according to the Governmental Advisory Committee.

The GAC this afternoon drafted formal Advice for the ICANN board stating that policy work on bulk regs should get underway before ICANN 84, which takes place in Muscat, Oman in late October.

While the wording still may change before it is sent to ICANN, the current draft advice reads:

The GAC advises the board: To urge the GNSO Council to undertake all necessary preparation prior to ICANN84 towards enabling targeted and narrowly scoped Policy Development Processes (PDPs) on DNS Abuse issues, prioritizing the following: to address bulk registration of malicious domain names; and the responsibility of registrars to investigate domains associated with registrar accounts that are the subject of actionable reports of DNS Abuse.

The advice on bulk regs is fairly self-explanatory: the GAC has become aware that spammers typically shop around for the cheapest TLDs then register huge amounts of domains on the assumption that some will start getting blocked quite quickly.

The second part of the advice probably needs some explanation: under the current ICANN contracts, registrars have to deal with abuse reports concerning domains they sponsor, but they’re under no obligation to investigate other domains belonging to the registrants of those domains.

So, if a scumbag registers 100 domains for a spam campaign and only one of them is reported as abusive, the registrar can comply with its contract by simply suspending that one domain. The GAC thinks it should be obliged to proactively investigate the other 99 names too.

The advice seems to have been inspired by two sources: NetBeacon’s recent Proposal for PDPs on DNS Abuse (pdf) and data from Interisle Consulting.

Both pieces of advice obviously could have an impact on registrars’ top and bottom lines. They could lose revenue if they currently make a lot of money from bulk regs, and their costs could be increased with new obligations to investigate abuse.

An added wrinkle comes in the GAC’s rationale for its advice, which suggests that dealing with bulk regs and abuse probes should be a gating factor for the next round of new gTLDs going ahead. It reads:

Before new strings are added to the DNS as a result of the next round, further work on DNS Abuse is needed to stem the increasing cost to the public of phishing, malware, botnets, and other forms of DNS Abuse.

The core text of the advice was compiled in furtive huddles on the edges of sessions at ICANN 83, and I believe Switzerland held the pen, but it seems the US government was the driving force behind the push to make abuse a barrier to the next round.

As I reported on Monday, the US GAC rep said that “in light of the global phishing problem… and similar concerns the United States is of the view that we should not expand the DNS too broadly”.

Little interest in cheapo gTLD program

Kevin Murphy, June 11, 2025, Domain Policy

ICANN’s program to offer heavily discounted new gTLD application fees to certain organizations has so far seen little uptake, and some governments are not happy about it.

The Applicant Support Program offers up to 45 qualified applicants a discount of up to 85% on their application fees. That’s worth almost $200,000 each. ICANN will also hook applicants up with pro-bono application consultants and help out with auctions if necessary.

While 40 applications are in the process of being drafted, according to ICANN’s latest monthly stats, only four finalized applications have been submitted and there’s no way of telling whether the other 40 will convert to full applications.

The low number has members of ICANN’s Governmental Advisory Committee concerned, partly because of a deal it struck with ICANN last year that would encourage a change of strategy if it turned out some regions were more represented than others.

The arrangement saw ICANN promise to refocus its outreach efforts on under-served regions after tallying up the home nations of the first 20 submitted applications. With the 12-month program application window now well past the half-way mark, the GAC is worried that by the time the 20th bid is logged, it will be too late to course-correct.

It now seems likely that the GAC’s formal Advice from the ongoing ICANN 83 meeting in Prague will see language included saying ICANN should conduct its review of the applications now, while there’s still time to adjust the strategy.

Currently, the stats show a strange and surprising mix of geographies.

North America has the most applications in draft at 15. This is weird because entities based in the US and Canada don’t qualify for the discount, ICANN doesn’t count Mexico as North American, and the only other economies in the region are US island territories like Puerto Rico and Guam.

Meanwhile, the whole of Latin America and the Caribbean region, with all its half a billion citizens, has just two applications in draft. That’s the just one more than Europe, which has just a handful of qualifying nations.

Africa and Asia-Pacific both have seven applications in draft, and Asia-Pac also has three fully submitted bids.

Based on the current stats, you’d have to assume ICANN would need beef up its outreach in Latin America if it wanted to rebalance the numbers. Europe probably doesn’t need as much love because so few countries there qualify.

As well as encouraging ICANN to analyse its number immediately, the GAC is also considering text that would connect applicants in drafting with their local governments, to see if they need any assistance getting over the final hurdle.

US government opposes most new gTLDs

Kevin Murphy, June 9, 2025, Domain Policy

The US government has come out against most of the new gTLDs likely to be applied for in next year’s application round, saying they will contribute to the “global phishing problem”.

The eyebrow-raising revelation came during an intervention from Susan Chalmers, the country’s senior representative on the Governmental Advisory Committee, at the ICANN 83 meeting in Prague this afternoon.

Chalmers said the US is not opposed to the next round in general, but “has some reservations” that the expansion could make DNS abuse worse and that ICANN should “consider how to limit the expansion appropriately”.

Here are her remarks in full:

The United States has some reservations about the next round of new gTLDs. Specifically we have concerns that expanding the DNS too broadly can lead to more spam and DNS abuse for everyone on the internet. Our concerns are not for a next round in general to be clear. We see value in certain categories of applications such as for geo-TLDs and for internationalized domain names. In some cases it makes sense to add new strings to the DNS, but in light of the global phishing problem (which we will learn more about tomorrow) and similar concerns the United States is of the view that we should not expand the DNS too broadly. As the GAC did in 2013 we must consider how to limit the expansion appropriately to take into account public interest impacts.

The US, which has at least five civil servants attending the GAC meetings in Prague, was the only government to openly oppose new gTLDs during this afternoon’s session.

The position puts the US at odds with likely the majority of next-round new gTLD applicants, which could be a cause for concern.

While there will no doubt be some worthy geographic TLDs and IDNs applied for, if 2026 is anything like the 2012 round most applications will be commercial in nature, with as broad an appeal as possible.

Sadly, no doubt some applicants will be the kind of chancers who want to make their millions selling disposable domains for a buck apiece to spammers.

While Chalmers’ remarks may be somewhat surprising, the US position under Trump isn’t a million miles away from the Obama administration’s position in the run-up to the 2012 round.

Back then, the US tried successfully to strong-arm ICANN into giving the GAC more powers over which gTLDs could and could not enter the root. Those powers have been grandfathered in to the rules for next year’s round.

But the political landscape was different back then. ICANN was still a US government contractor, which irked other governments. Some nations wanted ICANN’s powers to be expatriated and given to a body like the International Telecommunications Union. The US was keen to keep the Org under its jurisdiction, and thought a beefed-up GAC was the way to do it.

It seems unlikely that the US could derail the next round entirely. Technically, it would have to win over the full GAC to produce a consensus against the expansion, but one of the hallmarks of the Trump administration so far has been its refusal to play nicely or respect multilateralism, so who knows what might happen.

The US could also use ICANN’s own rules to object to individual new gTLD applications it deems risky or unworthy.

A GAC consensus advice objection against an applications has historically been enough to kill it dead, but any nation can also choose to go it alone by issuing a so-called GAC Early Warning.

An Early Warning is a unilateral notice to an applicant that a government doesn’t like their application and may try to get it rejected or changed in some way. Applicants are free to ignore such warnings, but are encouraged to engage with the government in question to resolve their concerns.

Could Chalmers’ remarks today be the first early warning?

UK’s Nigel Hickson has died

Kevin Murphy, April 1, 2025, Domain Policy

Long-serving ICANN community member and UK government representative Nigel Hickson has died, according to friends and colleagues.

He’s said to have died at the weekend following a battle with cancer.

While the loss will be felt most keenly by his family, Hickson’s absence will also be felt by the ICANN community and wider domain name industry.

Hickson was most recently head of internet governance policy at the UK’s Department for Science, Innovation and Technology, but he might be better known to the domains community as the country’s representative on ICANN’s Governmental Advisory Committee.

He was until a few weeks ago one of the GAC’s vice-chairs and as such often a prominent and vocal presence during governmental discussions of ICANN’s policies at public meetings.

But he also engaged with the domain investor community, showing up to deliver the UK government’s perspectives at conferences such as the London Domains Summit.

Prior to joining the government, Hickson spent eight years working for ICANN as a vice president with a government engagement portfolio.

I only met Nigel on a handful of occasions, but he always came across as a thoroughly pleasant chap with a surprising sense of humor.

Hickson is said to be survived by his wife and daughter, who have our condolences.

Could ICANN approve an R-word gTLD?

Kevin Murphy, January 22, 2025, Domain Policy

ICANN could be faced with the headache of approving or rejecting a new gTLD containing a term broadly considered a slur for the first time.

Unstoppable Domains has revealed that it is working with a client on an application for .retardio, which is linked to a memecoin cryptocurrency of the same name.

Unstoppable says the domain “symbolizes pride and a blend of brilliance with eccentricity”.

But the application could come up against significant challenges if it goes ahead, due to the various reviews and objection procedures all applications face.

The word “retard”, originally a medical term for people with mental disabilities, over the years morphed into a fun playground insult but is now considered offensive enough that, unless you’re Elon Musk, it’s often referred to as the “R-word”.

(I’m only typing it out in full here for the benefit of people who are reading this in their second language, who otherwise might not know what I’m talking about.)

Since 2009, the Special Olympics has held an annual Spread the Word to End the Word awareness day, which seeks to reduce usage of the word, which it describes as a form of “bullying”.

The British comedian Rosie Jones, who has cerebral palsy, faced a barrage of criticism from her own community when she provacatively titled her 2023 documentary about online ableist bullying “Am I a R*tard?” (asterisk in original).

There can be little doubt that it’s an offensive term in most of the Anglophone world, but does that mean it cannot be included in a gTLD string?

The current draft of ICANN’s Applicant Guidebook says that applicants “should be mindful of limitations to free expression” and there are multiple avenues through which a .retardio application could be killed off.

The most obvious way would be via the Governmental Advisory Committee, which has broad powers to instruct ICANN to reject applications on public policy grounds.

The AGB says the GAC Advice objection is for applications that are “problematic” or “potentially violate national law or raise sensitivities”, but that’s a pretty wide net.

If a couple of governments decided to champion an objection to .retardio, it’s easy to imagine they’d be able to rustle up enough support to meet the “consensus” threshold for formal GAC Advice.

ICANN’s board of directors is able to reject such advice, but in the 2012 application round it pretty much did what it was told.

Another way .retardio could fail is through the Limited Public Interest Objection, which can be filed against strings that are “contrary to generally accepted legal norms of morality and public order that are recognized under principles of international law”, such as:

Incitement to or promotion of discrimination based upon race, color, gender, ethnicity, religion or national origin, or other similar types of discrimination that violate generally accepted legal norms recognized under principles of international law

Literally anybody can file a LPI Objection, and they presumably could use the UN Convention on the Rights of Persons with Disabilities to tick the “principles of international law” box.

If successful, such objections force the applicant to withdraw.

The International Olympic Committee has never been shy about participating in ICANN, so if the affiliated Special Olympics, or the IOC, or indeed any disability rights advocacy groups, wanted to make a point by objecting to .retardio, the LPI Objection would be the way to do it.

ICANN lawyers want to keep their clients secret

Kevin Murphy, December 5, 2024, Domain Policy

IP lawyers in the ICANN community have come out swinging against proposed rules that would require them to come clean about who they work for, rules that are supported by registrars and governments.

A proposed policy that would force lawyers to disclose the identities of their clients when they participate in policy-making would violate their clients’ human rights, according to the Intellectual Property Constituency.

The criticisms came in response to an ICANN public comment period on a draft Community Participant Code of Conduct Concerning Statements of Interest, which opened in October and closed this week.

The draft would close a loophole that allows ICANN policy makers to keep their potential conflicts of interest secret when “professional ethical obligations” prevent them from disclosing this information.

“When disclosure cannot be made, the participant must not participate in ICANN processes on that issue,” the draft states.

The changes are keenly supported by the Registrar Stakeholder Group as a whole and by GoDaddy and Tucows in particular. As far as the registrars are concerned, the main problem with the draft is the somewhat vague enforcement mechanisms.

GoDaddy, for example, said in its comments:

We recognize that there may be situations in which a party is unable to disclose their client(s), and in those rare cases, GoDaddy agrees with ICANN’s conclusion that the participant forfeits the ability to participate in associated processes.

It added, echoing the RrSG as a whole, that more clarity is needed on enforcement, where the buck seems to stop with the chair of the working group where the disclosure infraction is alleged to have taken place, with no escalation.

On the opposing side are the IPC, the Business Constituency, and the International Trademark Association, which all filed comments criticizing the proposed changes. The IPC said:

The often-argued response of having attorneys not participate if they fail to uphold their ethical duty to their clients effectively vitiates the human right of representation by counsel and is not for the public benefit. ICANN has agreed to uphold human rights and therefore counsel cannot be compelled to disclose client identity.

Two of the concerns from lawyers is that the policy could require their clients to divulge trade secrets, such as whether they intend to apply for a new gTLD in the forthcoming application round.

Perhaps anticipating the Governmental Advisory Committee’s expected support for the policy changes, which was no secret, the IPC also raises the specter of the policy being broad enough to apply to the governments themselves: should they all be compelled to reveal the names of all the lobbyists who knock on their doors?

This forcing of transparency of national interest would significantly inhibit GAC members from fulfilling their role. Imagine a GAC member from one country filing an SOI saying that their government was being lobbied by numerous parties to gain favor in the New gTLD Rounds?

The GAC’s response to the public comment period was in fact cautiously supportive of the rule changes, saying:

Prima facie, the proposal referring to Statements of Interests seems to be in the right direction, and to fulfil the expectations expressed by the GAC. At the same time, the GAC looks forward to the reactions from ICANN org to the views expressed during the public comment period

Like the registrars, the GAC is looking for more clarity on enforcement mechanisms.

The public comments will by summarized for publication mid-December and the ICANN board could take action on the proposals next year.

Unloved INTA slams ICANN over new gTLDs

Kevin Murphy, October 22, 2024, Domain Policy

The new gTLD program is an existential threat to ICANN if it continues to ignore the concerns of IP interests, according to the International Trademark Association.

Trademark owners are becoming disillusioned with the ICANN process and “instead have opted to pursue more balanced outcomes through regulators, legislatures, and courts”, INTA said in comments on draft new gTLD program rules yesterday.

INTA warned that there has been “a decline in interest in the work of ICANN as otherwise engaged members have determined that there is very little return on the thousands of hours of time that they have devoted to ICANN’s continuous improvement”. It said:

The ICANN Board, Org and review team members would do well to consider the consequences of continuing to ignore the input of non-contracted parties especially when it comes to addressing ongoing harms within the domain name system. At a time when governments are vying to assume more policy oversight over the DNS, ICANN is well positioned to double down on the multistakeholder model by giving serious consideration and adjusting proposed policies in a balanced manner.

ICANN’s refusal to take on board the IP lobby’s suggestions when it added new DNS abuse requirements to its registry and registrar contracts earlier this year seems to be at the root of the outburst.

INTA said that it is “opposed to new [gTLD application] rounds” until “substantial reforms are made to ICANN’s approach to domain abuse and contract compliance”.

The comments were by far the angriest filed in response to the ICANN public comment period, just closed, that sought input on several draft sections of the new gTLD program’s Applicant Guidebook.

Pre-rant, INTA substantively said that the AGB needs to give brand owners and potential dot-brand applicants more clarity on when subsequent application rounds will launch.

Currently, ICANN expects the Next Round’s first wave to kick off in the second quarter of 2026, but subsequent application windows are subject to a checklist of triggering events that on the face of it is a little confusing.

Threats of government intervention undermining the legitimacy of the ICANN multistakeholder model are of course far from new. I’ve been writing about them for 20 years or more.

But the latest INTA threat may ring a little hollow given that ICANN’s Governmental Advisory Committee also filed comments on exactly the same issues, so we know exactly what governments think: they’re totally cool with how the AGB is being drafted, and just seem happy to be involved.

Private auctions to be banned in next new gTLD round

Kevin Murphy, July 25, 2024, Domain Policy

ICANN plans to ban private auctions in the next new gTLD application round, chair Tripti Sinha has told governments.

The board of directors plans to accept the Governmental Advisory Committee’s recent advice to “prohibit the use of private auctions in resolving contention sets in the next round of New gTLDs”, Sinha told her GAC counterpart in a letter published this week.

This is a significant departure from the 2012 round, where many contention sets were resolved privately, with tens of millions of dollars changing hands. Simply applying for a gTLD, in order to lose an auction rather than actually running a registry, will quite possibly no longer be a business model.

What replaces private auctions is yet to be determined. ICANN plans to publish a paper and hold two community webinars in August to discuss alternatives, and reach a decision at its meeting in early September.

Sinha warned that if it cannot reach a conclusion by the September meeting, it might delay the publication of the Applicant Guidebook and thus the opening of the next application window.

It’s quite an aggressive deadline, given the complexity of the problem. ICANN is essentially trying to figure out a way to prevent unscrupulous actors from attempting to game the system for financial gain.

Ideas such as allowing good-faith joint ventures to be formed between competing applicants have been floated in recent months, but have faced scrutiny as they might permit side-deals to be inked that have the same effect as private auctions.

What seems certain is that “last resort” auctions — where ICANN gets all the money for its already $200 million war chest — will still be an option in the next round, which is current penciled in for the first half of 2026.

ICANN’s board plans to pass resolutions on the matter next Monday, so we should have a little more clarity by the start of August at the latest.

ICANN content policing power grab may be dead

Kevin Murphy, April 3, 2024, Domain Policy

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”.

GoDaddy’s next .xxx contract may not be a done deal

Kevin Murphy, March 18, 2024, Domain Policy

ICANN has published what could be the next version of GoDaddy’s .xxx registry contract, and is framing it as very much open to challenge.

The proposed Registry Agreement would scrap the “sponsored” designation from .xxx, substantially reduce GoDaddy’s ICANN fees, and implement the strictest child-protection measures of any gTLD, as well as make ICANN Compliance’s job a lot easier by standardizing terms on the new gTLD program’s Base RA.

But, as eager as ICANN usually is to shift legacy, pre-2012 gTLDs to the Base RA, this time it’s published the contract for public comment as if it’s something GoDaddy is unilaterally proposing.

It’s “ICM’s proposal”, according to ICANN’s public comment announcement, referring to GoDaddy subsidiary ICM Registry, and “ICM has requested to use the Base Registry Agreement form, as well as to remove the sponsorship designation of the .XXX TLD”.

This is not the language ICANN usually uses when it publishes RA renewals for public comment. Normally, the proposed contracts are presented as the result of bilateral negotiations. In this case, ICANN and ICM have been in renewal discussions for at least three years, but the contract is being presented as something GoDaddy alone has asked for.

The new RA would remove almost all references to sponsorship and to IFFOR, the pretty much toothless “sponsor” organization ICM created to get its .xxx application over the line under the rules of the Sponsored TLD application round that kicked off back in 2003.

Instead, it loads a bunch of Public Interest Commitments, aimed at replicating some of the safeguards IFFOR oversight was supposed to provide, into the Base RA.

GoDaddy would have to ban and proactively seek out and report child sexual abuse material. It would also prohibit practices that suggest the presence of CSAM, such as the inclusion of certain unspecified keywords in .xxx domains or in the corresponding web site’s content or meta-content.

(ICANN notes that these PICs may become unenforceable, depending on the outcome of current discussions about its ability to enforce content-related terms of its contracts).

GoDaddy and IFFOR have both submitted letters arguing that sponsorship is no longer required. The existence of sister gTLDs .adult, .sex, and .porn as unsponsored gTLDs, also in the GoDaddy Registry stable, proves the extra oversight is not needed, they say. Registrants polled do not object to the changes, they say.

GoDaddy’s cost structure would also change under the new deal. Not only would it save $100,000 a year by cutting off IFFOR, but it would also inherit the Base RA’s 50,000-domain threshold for paying ICANN transaction fees.

This likely means it won’t pay the $0.25 transaction fee for a while — .xxx was at about 47,500 domains under management and shrinking at the last count. It hasn’t reported DUM over 50,000 since January 2023.

While the renewal terms may seem pragmatic and not especially unreasonable, they’ve already received at least one public objection.

Consultant Michael Palage, who was on the ICANN board for the first three years of .xxx’s agonizing eight-year path to approval, took to the mic at the ICANN 79 Public Forum earlier this month to urge the board to reject GoDaddy’s request.

Palage said there have been “material violations of the Registry Agreement” that he planned to inform ICANN Compliance about. He added that approving the new deal would set a bad precedent for all the other “community” registries ICANN has contracts with.

The situation has some things in common with the controversy over the proposed acquisition of Public Internet Registry and .org a few years ago, in that the proposal entails ignoring promises made by a registry two decades ago.

Whether .xxx will attract the same level of outrage is debatable — this deal doesn’t involve nearly as many domains and does not talk to the price registrants pay — but it could attract noise from those who believe ICANN should not throw out its principles for the sake of a quieter life.

One place we might look for comment is the Governmental Advisory Committee, which was the biggest reason .xxx took so long to get approved in the first place.

But the timing of the comment period opening is interesting, coming a week after ICANN 79 closed. It will end April 29, about six weeks before the full GAC next meets en masse, at ICANN 80.

It’s not impossible that the new contract could be approved and signed before the governments get a chance to publicly haul ICANN’s board over the coals.