news Google Leaks Whois Data for Over 282,000 Protected Domains

Quite shocking. Google is the last company on earth that I would expect to make this mistake.

Wow very unprofessional, though I do think they're kind of out of line saying they are now at risk of identity theft..

That's crazy, I was thinking about giving them a try. Now that we are finding out that maybe they do make mistakes/errors I wonder if that will hurt them.

ulterios said:

Now that we are finding out that maybe they do make mistakes/errors I wonder if that will hurt them.

Click to expand...

This incident will hurt Google in the short run. In the long run, especially if Google does fix this mistake, they'll recover.

Everybody makes mistakes; after all, all of us are human. The important things are to fix those mistakes, acknowledge them, and ensure those don't happen again.

Only time will tell how this thing goes.

Dave_Z said:

This incident will hurt Google in the short run. In the long run, especially if Google does fix this mistake, they'll recover.

Everybody makes mistakes; after all, all of us are human. The important things are to fix those mistakes, acknowledge them, and ensure those don't happen again.

Only time will tell how this thing goes.

Click to expand...

That's exactly what had crossed my mind. One thing that makes it worse is the fact that they are fairly new as a registrar. Some people might see this as a warning to not try them out. I know eventually it will be a thing of the past but the timing was not the best for this to happen to them.

If anyone can recover from bad press, it's Google

It is really a big question mark on whois data's protection but i am still in doubt that how i could be happen? It is domain providers' duty to secure their "Protected" data.

@johnfsander a human error might be involved. It's a connection from Google to their registrar partners.

Just in. Another incident, unauthorized certificates issued to Google domains.
http://que.com/2015/03/25/twitch-se...s-issued-for-several-google-domains-and-more/

I'm assuming this incident does not directly affect Google Domains, their new product. From reading the article the OP posted, it is talking about domains registered through Google that are utilizing Enom as the registrar. If these domains were registered through Google but are utilizing Enom as the registrar, I am wondering how much of this problem may also be Enom's fault? Was the privacy protection service being provided by Google or Enom? I suppose it is possible that upon renewal on the Google site an API call could have mistakenly removed the privacy protection service at enom for that domain. That is the only way I could think of it being Google's fault which may have happened in this case.

@TheWatcher i wonder how it possible where they have lot of guys in security teams and it is their duty to protect the data. I am going to post this new on my blog and i hope it will a good topic for my readers

@johnfsander we will never know the real reasons behind the flaw. Their PR knows how to change the subject and forget about it. They are good at it.