Afilias loses back-end deals on two Chinese gTLDs
TLD Registry, the Finnish/Irish registry that runs two Chinese-script gTLDs, has ditched Afilias in favor of a Chinese back-end provider.
Afilias said tonight that as of Friday it will no longer be the back-end for .在线 (.xn--3ds443g, “Chinese online”) and .中文网 (.xn--fiq228c5hs, “Chinese website”).
The company said:
Afilias has been directed by TLD Registry to shut down the Afilias operated SRS’s for .xn—3ds443g and .xn—fiq228c5hs on June 17, 2016 at 00:00:00 UTC and transfer the registry files to TLD Registry and its new provider. In accordance with this directive from our client, the SRS will be shut down and the files will be transferred, and Afilias will no longer operate the SRS for these two strings.
TLD Registry VP Pinky Brand declined to name the registry’s new back-end provider, beyond that the winning provider is Chinese.
The new back-end will be named in the next day or so, he said.
Registrars have been informed about the switch, Afilias said.
It’s not yet clear whether TLD Registry has decided to switch providers for cost reasons or in order to more deeply embed itself in China.
The company was founded by and is managed by Finns and is legally based in Ireland, but it only runs Chinese-script gTLDs.
The Chinese government has regulations, and is proposing more, preventing Chinese citizens using domains that do not meet certain guidelines, which include a corporate presence in China.
Several registries are opening up offices in China in order to abide by these rules, but I’m not aware of any that have switched back-ends for that reason.
The two gTLDs have fewer than 30,000 domains in their zone files between them.
Lorem ipsum
Apparently it’s no secret information as it will be named “the next day or so” anyway: they will switch to Beijing Teleinfo Network Technology Co., Ltd.
The formal reason communicated to registrars is neither cost nor deeper engagement in the Chinese market, but although it was in a semi-public mailing to registrars there must be a reason why registry and back-end providers are remaining silent on it, so will I be.