Deprecated: Assigning the return value of new by reference is deprecated in /home/ddomain/public_html/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /home/ddomain/public_html/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /home/ddomain/public_html/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /home/ddomain/public_html/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /home/ddomain/public_html/wp-settings.php on line 18
Google.de back under Google's control Database error, check your configuration

Google.de back under Google's control

This is a follow-up to last night's post. According to heise.de, google.de was indeed hijacked by a client of the German web hosting company goneo.de. The client had claimed to Goneo that he was the owner of google.de, and Goneo had automatically passed on the claim to the .de registry DeNIC. In accordance with DeNIC policies, the registry sent emails to Google's domain registrar MarkMonitor to confirm if they had any objections to the ownership transfer. MarkMonitor failed to respond to the inquiry within the required time limit, which DeNIC (in accordance with its flawed transfer policies) interpreted as approval.

When Goneo realized what had happened and that google.de was resolving to their server, they immediately authorized DeNIC to transfer the domain back to Google. But during that process it appears that DeNIC briefly dropped google.de, which led to its immediate registration by Fresh Domains, a German drop catching firm.

Google.de is now back under Google's ownership. This chain of events has been confirmed by Goneo and DeNIC, but not by Google or MarkMonitor. DeNIC says that Goneo is to blame, but Goneo claims they are not responsible because "nobody looks at these automated transfer requests anyway". DeNIC could not explain how the domain eventually ended up in the hands of drop catching firm Fresh Domains. There is only one way this could have happened, though. DeNIC must have briefly dropped google.de when trying to transfer the domain back to Google.

As for MarkMonitor, they didn't respond to requests for comment. It appears that Google did nothing wrong (other than registering their domain at MarkMonitor) because in accordance with the flawed DeNIC transfer policies they were never asked whether they wanted to give up their domain.

It is possible that the DeNIC registry will soon introduce an optional LOCK status as well as AUTH codes for all .de domains to prevent similar incidents from happening again in the future. (An AUTH code is basically a password for a domain which ensures that only the actual owner can transfer the domain.)

Update: The following "confession email" was received by The Register:

Hello Chris, I am the person in question registering the domain with Goneo, although it did happen inadvertently. I showed my girlfriend how one of my domains had been taken over by somebody else with the Goneo ordering system - but before entering my contact details, I went back in the ordering process and registered a different domain. Somehow, the Goneo system must have received both domains to register…

Greetings,

- The accidental few-hours owner of google.de

Share/Save/Bookmark

4 Responses to “ Google.de back under Google's control ”

  1. [...] Según El Comerdio de Peru el dominio caducó inexplicablemente, pero según Daily Domainer fue Denic (entidad que gestiona los dominios .de) quién inexplicablemente canceló el dominio, lo que permitió a un tercero registrarlo. [...]

  2. [...] Actualización: En Dirson y Com.es también comentan que en Daily Domainer dicen podría ser debido a un intento de transfer del dominio. Lo que está claro es que se ve "algo raro" en el whois con cambios de titular en los últimos días. [...]

Leave a Reply

You can use these XHTML tags: <a href="" title=""> <abbr title=""> <acronym title=""> <blockquote cite=""> <code> <em> <strong>