ICM Registry has negotiated lower ICANN transaction fees as part of a broad amendment to its Registry Agreement that also includes new trademark protection measures.
The company’s uniquely high $2 per-transaction fee could be reduced to the industry standard $0.25 by mid-2018.
As part of the renegotiated contract, ICM has also agreed to impose the Uniform Rapid Suspension policy on its registrants.
URS is the faster, cheaper version of UDRP that allows trademark owners to have domain names suspended in more clear-cut cases of cybersquatting.
The $2 fee was demanded by ICANN when ICM first signed its RA in 2011.
At the time, ICANN said the higher fee, which had doubled from a 2010 draft of the contract, was to “account for anticipated risks and compliance activities”.
The organization seemed to have bought into the fears that .xxx would lead to widespread misuse — something that has noticeably failed to materialize — and was expecting higher legal costs as a result.
The companion TLDs .adult, .porn and .sex, all also managed by ICM, only pay $0.25 per transaction.
The overall effects on registrants, ICANN and ICM will likely be relatively trivial.
With .xxx holding at roughly 170,000 domains and a minimal amount of inter-registrar transfer activity, ICM seems to be paying ICANN under $400,000 a year in transaction fees at the moment.
Its registry fee is usually $62, though a substantial number of domains have been sold at lower promotional pricing, so the cost to registrants is not likely to change a great deal.
The reduction to $0.25 would have to be carried out in stages, with the earliest coming this quarter, and be reliant on ICM keeping a clean sheet with regards contract compliance.
Under the deal, ICM has agreed to adopt many of the provisions of the standard Registry Agreement for 2012-round gTLDs.
One of those is the URS, which may cause consternation among domainers fearful that the rights protection mechanism may one day also find its way into the .com registry contract.
ICM has also agreed to implement its existing policies on, for example, child abuse material prevention, into the contract as Public Interest Commitments.
The RA amendment is currently open for public comment at ICANN.
NameCheap may have sold over a million .xyz domains, but apparently it will sell no more than that.
The registrar confirmed to DI this evening that it is no longer taking .xyz registrations. It declined to explain why.
It has also stopped selling .college and .rent domains — two other gTLDs owned by XYZ.com. Other new gTLDs are not affected.
It’s reportedly not accepting inbound transfers either, though existing domains can be renewed.
The switch-off happened at the end of last month, a NameCheap representative said.
That’s just one month after the registrar celebrated its one millionth .xyz registration, which XYZ.com commemorated with a blog post bigging up NameCheap’s user-customers.
The move is peculiar indeed. NameCheap is the third highest-volume .xyz registrar, behind West.cn and Uniregistry, responsible for about 15% of .xyz’s domains under management.
It’s also NameCheap’s biggest direct-selling gTLD by a considerable margin.
NameCheap is well-known as primarily an eNom reseller — it accounts for 28% of eNom’s domains under management and 18% of its revenue, largely from .com sales.
But with new gTLDs it has started selling domains on its own IANA ticker, meaning a direct connection to the registry and more gross profit for itself.
According to June’s registry reports, the million .xyz names accounted for roughly two thirds of NameCheap’s total DUM (not counting names sold via eNom).
The closet rival in its portfolio is .online, which provided the registrar with about 81,000 DUM.
The registrar added about 350,000 .xyz domains in June, a month in which it briefly offered them at $0.02 each.
At that time, the company reported technical issues that led to a 12-24 hour backlog of registrations to process, though its blog post announcing the problem appears to have since been deleted.
NameCheap has declined to comment on the reason for the surprise move, and XYZ did not immediately respond to a request for comment.
The fact that all of XYZ.com’s TLDs have been cut off suggests some kind of dispute between the two companies, but the fact that renewals can still be processed would suggest that NameCheap has not lost its .xyz accreditation.
More info if I get it…
XYZ.com has hired its first Beijing-based employee, as part of its ongoing plan to formally enter the Chinese market.
The company said yesterday that it has appointed Mason Zhang, until recently chief marketing office at .top gTLD registry Jiangsu Bangning Science & Technology Co, as its new director of business development for China.
It’s part of XYZ’s seemingly interminable entry to the Chinese market, which is over a year old.
While the majority of .xyz’s registrations have been into China, the registry (along with pretty much every other Western registry) still does not have the necessary government permissions so that its customers can start using their names.
The company said in a blog post that it expects to get its Chinese accreditation “very soon”.
Zhang’s former employer, .top, is second only to .xyz in terms of new gTLD registration volume, also due to Chinese sales. It has about 3.7 million names in its zone file, compared to .xyz’s 6.1 million.
The DNS root saw its 1,500th concurrent live TLD come into existence on Friday, just hours before the US relinquished its oversight powers.
Amazon received its delegation for .通販 (.xn--gk3at1e, Japanese for “online shopping”) and satellite TV company Hughes got .dvr, meaning “digital video recorder”.
That took the number of TLDs in the root to exactly 1,500, which is where it still stands today.
Both went live September 30, which was the final day of ICANN’s IANA contract with the US National Telecommunications and Information Administration, which expired that night.
An ICANN spokesperson confirmed that the two new gTLDs “were the last ones requiring NTIA’s approval.”
From now on, the small clerical role NTIA had when ICANN wanted to make changes to the root is no more.
The fact that it hit a nice round number the same day as ICANN oversight switched to a community-led approach is probably just a coincidence.
Amazon’s .通販 was almost banned for being too confusingly similar to “.shop”, but that ludicrous decision was later overturned.
Hughes’ .dvr was originally intended as a single-registrant “closed generic”, but is now expected to operate as a restricted but multi-registrant space.
The .pharmacy new gTLD has been dragged into the ongoing trademark dispute between two pharmaceuticals giants called Merck.
Germany-based Merck KGaA has accused the .pharmacy registry of operating an unfair and “secretive” process to resolve competing sunrise period applications.
The domain merck.pharmacy was awarded to US rival Merck & Co, which was spun off from the German original a hundred years ago, after both Mercks applied for the domain during .pharmacy’s January-March 2015 sunrise.
Now Merck KGaA has become what I believe might be the first company to reveal an attempt to invoke ICANN’s Public Interest Commitments Dispute Resolution Procedure to get the decision reversed.
The National Association of Boards of Pharmacy, a US entity, operates .pharmacy as a tightly controlled gTLD with pre-registration credential validation.
When it launched for trademark owners in last year, it was vague about how contentions between owners of matching trademarks would be handled, according to Merck KGaA.
Merck KGaA claims that NABP awarded merck.pharmacy to Merck & Co and initially refused to disclose how it had arrived at its decision other than to say the German firm “met fewer criteria” than its rival.
After some back-and-forth between their lawyers, Merck KGaA was still not happy with NABP’s response to the dispute, so it decided to start filing compliance reports ICANN.
A year on, it tried to invoke the PICDRP.
Public Interest Commitments are addenda to ICANN Registry Agreements that bind the registries to certain behaviors, such as fighting malware and working with industry-specific regulatory bodies.
The PICDRP, heard by ICANN or an independent standing panel, is a way for third parties to challenge registries’ compliance with their contracts when they believe PICs have been violated.
No PICDRP disputes have actually made it before a panel to date, to my knowledge. Indeed, this is the first time I’ve heard of anyone even attempting to file one, though ICANN Compliance reports indicate about 20 were filed last year.
Merck KGaA claims that by not disclosing how it decided Merck & Co should win merck.pharmacy, NABP is in breach of the PIC that states:
Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.
It suspects that NABP was biased towards Merck & Co because the US firm is a $100,000+ contributor to its coffers.
NABP has denied any wrongdoing, saying it applied “objective criteria” to decide which Merck most deserved the name.
This June, over a year after the domain was awarded, Merck KGaA filed its PICDRP complaint with ICANN. Two weeks ago, ICANN responded saying the complaint had been rejected, saying:
The detailed review criteria used to resolve the contention for the registration of the domain name
was part of an operational procedure that the registry operator applied to both applicants’ websites and was consistent with .pharmacy’s community restrictions in Specification 12 of the RA. As the internal operational procedure does not conflict with ICANN’s agreements and policies, it is deemed outside of ICANN’s scope of enforcement.
The decision seems to have been made by ICANN staff. No independent panel was appointed. The PICDRP grants ICANN “sole discretion” as to whether a panel is needed.
The only reason the dispute has come to light is that Merck KGaA has decided to challenge ICANN’s decision with a Request for Reconsideration. The RfR and 600-odd pages of exhibits are published here.
It’s the second concurrent RfR Merck has on the go with ICANN. The Mercks are also simultaneously fighting for the right to run .merck as a dot-brand gTLD.
Both applications for .merck went through the Community Priority Evaluation process, but both failed.
The next stage in resolving the contention said would have been an auction, but Merck KGaA has filed for Reconsideration on its CPE panel’s determination.