Recent Posts
- Alibaba, Name.com among new RDRS opt-ins
- .my domains to be sold globally next month
- The Swiss can register .swiss domains from next week
- .ai up to 425,000 domains
- A million “free” .music domains up for grabs
- D3 to get $5 million in crypto to apply for .ape gTLD
- Alibaba hit with ICANN breach notice
- New Vegas conference “Davos for Web3 interoperability”
- ICANN content policing power grab may be dead
- Cable company unplugs its dot-brand after acquisition
- Germany crosses 10,000 dot-brand domains milestone
- Founders out as Com Laude gets equity injection
- PIR’s Diaz to leave domain industry
- Some registrars have already quit ICANN’s Whois experiment
- ICANN opens $217 million Grant Program
- Internet could get one-letter gTLDs (but there’s a catch)
- .ai registry fights deadbeats with tweaked auction rules
- Amazon and Google among .internal TLD ban backers
- .ai registry advises buyers not to use GoDaddy
- .post liberalizes with new sunrise period
- Team Internet spends $41 million on content farm
- Epik backtracks on Kiwi Farms claim after legal threat
- .austin names launch on blockchain
- Freenom shuts down 12.6 million domains — report
- GoDaddy’s next .xxx contract may not be a done deal
- GlobalBlock blocking 2.5 million domains
- Microsoft moving its cloud apps from .com to .microsoft
- ICANN 79: anonymous trolls and undercover lawyers
- ICANN scores win in single-letter .com lawsuit
- Cosmetics brand terminates its gTLD
- Up to 70 jobs on the line at Nominet as .uk regs dwindle
- Governments back down on new gTLD next round delay
- Private auctions could be banned in new gTLD next round
- ICANN meeting venue “insensitive and hurtful”
- GoDaddy to start selling graphic.design domains
- GAC spinning up new gTLD curveball at ICANN 79?
- GoDaddy’s GlobalBlock supports blockchain names
- Police .uk domain takedowns dive in 2023
- GoDaddy wants to cut the bullshit from .xxx
- Dueling domain blocking services to launch at ICANN 79
- Freename tries to bridge DNS and blockchain
- Olive retires from ICANN
- Whois policy published without life-saving disclosure rule
- UK gov takes its lead from ICANN on DNS abuse
- Tucows reports 2023 results
- Twitter “completely unresponsive” on clickable domains
- ICANN spends $5 million more than planned in first fiscal half
- .art takes a million domains off its premium list
- KeyTrap ‘the most devastating vulnerability ever found in DNSSEC’
- Freenom settles $500 million Meta lawsuit and will exit domain business
- New gTLD lottery to return in 2026
- First GlobalBlock prices revealed — they ain’t cheap
- Domain universe grows on new gTLDs despite .com shrinkage
- D3 signs up crypto gTLD client number five
- GoDaddy reports strong domains growth
- How to qualify for a $40,000 gTLD
- Registry service provider evaluation handbook published
- WebUnited inks deal to “mirror” country’s TLD in the blockchain
- GoDaddy project unveils brand-blocking calculator
- Report: Monster “misappropriated” millions from Epik
- .com is shrinking but Verisign raises prices again anyway
- D3 announces fourth crypto new gTLD client
- Donald Trump loses second UDRP case
- UK cybersquatting complaints hit record low
- No excuses! PIR to pay for ALL registries to tackle child abuse
- ICANN insists it is working on linkification
- Namecheap sues ICANN over .org price caps
- GoDaddy offers free Ethereum blockchain integration
- Epik reveals who is running the company
- Epik gets acquired again! The plot thickens…
- Airline gTLD crashes and burns
- First chunks of new gTLD Applicant Guidebook drop
- Epik to reveal its owners soon
- Another crypto firm to apply for a new gTLD
- Monster and Royce are NOT involved in Epik?!
- Nominet to overhaul .uk registry, turn off some services
- Russia blames DNSSEC, not Ukraine, for internet downtime
- Team Internet says revenue beat estimates
- Sold for over $20k, insure.ai and dog.ai back in .ai’s expired names auction
- .ai helps UDRP cases rise in 2023, WIPO says
- Freenom’s domains land at Gandi after termination
- .ru domains fly off the shelf as Western sanctions bite
- ICANN picks its first ever Supreme Court
- Lebanon’s ccTLD going back to Lebanon after ICANN takeover
- ICANN picks the domain it will never, ever release
- ICANN approves domain takedown rules
- Has Epik gone “woke”?
- First bits of new gTLD Applicant Guidebook expected next week
- ICANN bans closed generics for the foreseeable
- You can’t use money to buy .box domains
- After 14 years, ICANN practices what it preaches on IDNs
- Weak demand for private Whois data, ICANN data shows
- .ing doing way better than .meme
- DNS Women barred from ICANN funding?
- Dev releases free open-source TLD registry platform
- INCO flips a gTLD to Identity Digital
- Anguilla fears the .ai junk drop
- Five more gTLDs get launch dates
- $10 million of ICANN cash up for grabs
- Almost 50,000 .ai domains sold in a quarter
- ICANN threatens to regulate your speech [RANT]
- Life insurance company kills dot-brand
- ICANN finds new home for Lebanon’s TLD after founder’s death
- ICANN begs people to use its new Whois service
- Shiba Inu outs itself as crypto new gTLD applicant
- Over 50,000 .ai domains sold in three months
- Amazon planning new push into registrar market?
- Registries and registrars vote ‘Yes’ to new DNS abuse rules
- ICANN predicts flattish 2025 for domain industry
- Fast-growing Gname buys another 150 registrars
- GoDaddy service to let you block domains in over 650 TLDs
- Did I find a murder weapon in a zone file?
- ICANN drops the “man” from Ombudsman
- Have your say on police domain takedown powers
- Most registrars are shunning ICANN’s new Whois system
- Nominet to take over .gov.uk
- ICANN picks Istanbul for 2024 meeting
- ICANN’s private Whois data request service goes live
- .au regs slide on 2LD anniversary
- ICANN accused of power grab over $271 million auction fund
- A registrar is getting blamed for an Israeli war propaganda site
- Two more dot-brands bite the dust
- Google sells five-figure AI domain and six-figure .ing hack
- .blackfriday is still a bit rubbish
- Internet Naming Co acquires five more gTLDs
Plural gTLDs give ICANN huge credibility risk
Can .pet and .pets co-exist peacefully on the internet? Or would they create such confusion among internet users that the whole new gTLD program would look irresponsible and foolish?
That’s the question ICANN is due to face today, as constituents line up at the public forum in Beijing to question its board of directors about the problem of plurals in new gTLDs.
The Governmental Advisory Committee, the Business Constituency, the Intellectual Property Constituency and others have all openly questioned the sanity of allowing plurals in recent days.
Right now there are 59 collisions between singular and plural gTLD applications (in English, at least, according to my analysis), involving 23 unique string pairs.
These are: .accountant(s), .auto(s), career(s), .car(s), .coupon(s), .cruise(s), .deal(s), .fan(s), .game(s), .gift(s), .home(s), .hotel(s), .kid(s), .loan(s), .market(s), .new(s), .pet(s), .photo(s), .review(s), .sport(s), .tour(s), .web(s) and .work(s).
None of these singular/plural clashes are currently in contention sets with each other, meaning there’s nothing to stop them all being delegated by ICANN. We could have a .loan alongside a .loans a year from now.
It seems to be only common sense that these clashes will cause frequent confusion. I doubt many would pass the longstanding “shouted across a crowded bar” test for URL clarity.
Would you want to register a .photo domain if you knew .photos was also available, and vice versa? If you did, wouldn’t you also want to register the .photos equivalent, just in case?
That’s one of the things ICANN’s commercial stakeholders are worried about: 23 extra TLDs means 23 extra defensive registrations for every brand they want to protect.
But there’s also the risk that gTLD registries that are successful in this application round will feel obliged to apply for the plurals of their strings in future rounds for defensive purposes.
The plurals issue also highlights shortcomings in how the new gTLD program was structured.
Why is this happening?
Unless two companies applied for the exact same strings, there are only two ways they could end up in a contention set together.
The first way was if the String Similarity Panel decided that the two strings were too visually similar to be allowed to co-exist, and that didn’t happen in the case of plurals. The panel only decided two things in the end: that I and l are confusingly similar, and that rn and m are confusingly similar.
To date, nobody except the Panel and ICANN knows what the logic behind this decision was, but it appears to be based on a very narrow (though not unreasonable) interpretation of what constitutes visual similarity.
The second way to end up in a contention set was to file a successful String Confusion Objection, or to be on the receiving end of one.
But of the 33 such objections filed, only 11 were filed against plurals, covering only six new gTLD strings in total: .pets, .tours, .webs, .games, .cars, and .kids. There was also an objection to .tvs, due to a clash with the existing ccTLD .tv.
(UPDATE: it appears that only approximately half of the String Similarity Objections filed have actually been revealed to date).
The main reason there weren’t more objections is that only existing registries and new gTLD applicants had standing to file an objection. Nobody else was allowed to.
Applicants were of course disincentivized from filing objections. Winning a String Confusion Objection doesn’t kill off your rival if you’re an applicant, it merely places both applications in a contention set.
Being in a contention set means you’re going to have to pay money to get rid of your competitor, either by negotiating some kind of private deal or by punching it out at auction.
By not filing objections, applicants in singular/plural situations risk looking like they don’t care about user confusion or are blasé about forcing defensive registrations.
(And by defensive registrations, remember here we’re not only talking about trademark owners, we’re talking about every potential future registrant in those gTLDs.)
They do have the slight excuse that they were only given a week or so to file objections after the results of the String Similarity Panel’s deliberations, delayed several times, were revealed.
There’s also the possibility that some of the apparent clashes won’t be as big of a concern in the marketplace due to, for example, registration restrictions.
What happens next?
The GAC is almost certain to issue advice about plurals in the next day or two, having brought the topic up with ICANN’s board of directors earlier this week.
The Business Constituency is also expected to make a few proposals directly to the board during the Public Forum in Beijing, Thursday afternoon local time.
The BC is likely to suggest, for example, that if one String Similarity Objection decision finds that a plural and a singular are confusingly similar, then that ruling should apply to all plural clashes, even if no objection has been filed.
It’s an audacious idea: it would certainly do the trick, but it would require some severe goal-post moving by ICANN at a time when it’s already under fire for pulling last-minute stunts on applicants.
It would also risk capturing fringe cases of strings that look plural but, in the context they are used in everyday language, are not (such as .new and .news).
Without some kind of action, however, ICANN is pretty much guaranteed to attract negative publicity.
Looking like it’s the stooge of the domain name industry, forcing regular registrants to double-buy their domains to the enrichment of registries and registrars, could look bad.
Totally Agree
Users will look at .pet and .pets and think it’s all stupid.
IMO same goes for .law, .lawyer, .attorney.
Redundancies
this new gtld thing is a goldmine for lawyers and nothing else. Nobody needs those TLD´s there is no demand at all. We will end up with thousands new TLD´s after few years which nobody needs. They will maybe influence search, but they will definitely confuse the enduser. The Enduser is used to differentiate in a SLD, most users don’t know that so many TLD´s exist.
I feel the same about iPads.
Not all of the objections have been published yet. We filed a string confusion objection. and it’s not in the list yet.
Interesting. ICANN said there was 33, and all 33 have been published. Perhaps ICANN doesn’t have all the data yet.
Perhaps 33 passed the review on that stage. We had to cure a deficiency which we did this week.
You’re right. There are about 67 objections in total, only 33 of which have been published. I’ve added a note to the post accordingly,
This whole gTLD concept is the most ill concieved stepchild in Marketing History. This is turning into a Dog and Pony show that is laughable. WOW is all we can say!
Gratefully, Jeff Schneider (Contact Group) (Metal Tiger)
The concept of visual similarity is mention in the Applicant Guidebook only in connection with IDNs. was wondering why ICANN squeezed this into the ASCII space.
I believe .fungus and .fungi can co-exist. But there might be some confusion between .deer and .deer 😀
more new confusion…..
.big
.bigger
.biggest
.work
.works
.worked
.working
Allowing plural and singular TLDs will not only add negatively to ICANNs credibility, but also confuse Internet users significantly. It was very surprising to see this outcome from the string similarity panel
The process lacked the ability for the Independent Objector to also file String Similarity Objections. The panel analysis was only visual, and the objection process looks at other angles like meaning and phonetic.
What could still be done is to let the Independent Objector, only, have a window for filing string similarity objections. The lack of standing to object is what allowed plurals and .ong x .org similarities to go without proper review.
There’s another highly serious issue of potential consumer confusion – this one applies to some of the proposed closed gTLDs.
That is, ownership of a closed gTLD may give the owner an undeserved and unearned status as a respected authority in that field, instant bought credibility, even possessing an implied endorsement by industry federations or the government (in the minds of consumers).
Imagine exclusive ownership of all domains in strings like:
Warranty.insurance
Official.forex
Health.food
Education.game
Hospital.store
Pharma.med
Share.markets
Internet.security
Priority.mail (US Postal Service is objecting to this one, since they own a mark on the term.)
I hope the GAC has closely studied the comments on the ICANN closed generic forum. The following two excerpts illustrate this risk. The first refers to insurance and the second to finance and insurance, but the principle applies to other generic words to different degrees.
(Note, I think the .insurance application has been withdrawn)
———————— Q U O T E
“The statements in these applications also evidence the potential to create consumer confusion. Consumers will likely be misled into believing that one entity represents the entire insurance industry, has established measures that have set them apart from (or is safer than) the rest of the industry, or has somehow obtained governmental license or endorsement that it is superior to other members of the larger insurance community.”
American Insurance Association (AIA)
———————— Q U O T E
“The public interest is particularly at risk in the case of generic terms that are defined by statute or other legal authority. For example, the term ‘IRA’ stands for ‘individual retirement account’ and has specific, statutorily defined meaning under United States tax law… Allowing any one company in a particular industry to obtain proprietary rights to a statutorily-defined term by using that term as a closed gTLD would suggest to the public that the company has a unique, preferred, or even government-sponsored role with respect to the products marketed under that domain.”
TD Ameritrade
Charles Schwab & Co., Inc.
Teachers Insurance and Annuity Association of America (TIAA)
————————————
Two more singular/plural pairs:
.reise x .reisen
.property x .properties
Plurals are not formed only by adding “s” to the end of the string…
.supply x .supplies as well