Mucho weirdness as Google “forgets” to renew major domain
Google has lost control of a key domain name, breaking millions of URLs used by its customers.
It emerged today that the domain blogspot.in expired in May and was deleted around June 24.
It was promptly re-registered via a non-ICANN registrar based in India called Domainming and put up for sale on Sedo for $5,999.
Blogspot is the brand used by people using Google’s Blogger platform. While the .com is the primary domain, the company localizes URLs to the ccTLD of the visitor’s home country in most cases.
There are currently over four million blogspot.in URLs listed in Google’s index.
Most of the reports I’ve read today chalk the loss of the domain down to corporate forgetfulness, but it appears to be weirder than that.
Google uses MarkMonitor to manage its portfolio, so if it is a case of the registrar forgetting to renew a client’s domain, it would be hugely embarrassing for whoever looks after Google over there.
However, historical Whois records archived by DomainTools suggests something odder is going on. It looks like MarkMonitor would have been prevented from renewing the domain by the .in registry.
These records show that from June 1, 2018, blogspot.in has had a serverRenewProhibited status applied, basically meaning the registry won’t allow the registrar to renew the domain.
ICANN describes the code like this:
This status code indicates your domain’s Registry Operator will not allow your registrar to renew your domain. It is an uncommon status that is usually enacted during legal disputes or when your domain is subject to deletion.
Often, this status indicates an issue with your domain that needs to be addressed promptly. You should contact your registrar to request more information and resolve the issue. If your domain does not have any issues, and you simply want to renew it, you must first contact your registrar and request that they work with the Registry Operator to remove this status code. This process can take longer than it does for clientRenewProhibited because your registrar has to forward your request to your domain’s registry and wait for them to lift the restriction.
The domain was placed into clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited, serverDeleteProhibited, serverTransferProhibited, and serverUpdateProhibited statuses at the same time.
Basically, it was fully locked down at both registrar and registry levels.
All of those status codes apart from serverRenewProhibited were removed in the first week of May this year, after almost two years.
The registry for .in is government-affiliated NIXI, but the back-end provider is Neustar.
At the time the domain was locked down, Afilias ran the back end, and there was a somewhat fractious battle going on between the two companies for the .in contract.
Judging by the changing status codes, it appears that two years ago somebody — Google, MarkMonitor, NIXI or Afilias — put the domain into a state in which it could not be renewed, transferred or deleted.
For some reason, the domain stayed like that until just a couple of weeks before it expired, when the prohibitions on deletion and transfer were removed.
I’ve been unable to find any information about legal trouble Google had in India two years ago that would have led to this unusual state of affairs.
It doesn’t seem to be a simple case of forgetfulness, however.
If you find this post or this blog useful or interestjng, please support Domain Incite, the independent source of news, analysis and opinion for the domain name industry and ICANN community.
Recent Comments