4 ms·

google.ps has not been hacked. The .ps registry was. Google DNS servers have been changed to omar.genious.net and hamza.genious.net

sp332 13y ago
If they hacked the .ps registry, did they redirect any other sites?
- aray 13y ago
  Looks like nike.com.ps (for example) still redirects to the nike homepage.
baddox 13y ago
I think saying "google.ps was hacked" is a perfectly reasonable way to describe what happened.
- UVB-76 13y ago
  That implies the site itself was hacked, when it was not. It appears the .ps domain registry was hacked.
- reflectiv 13y ago
  I don't agree at all, the system which was hacked is not in Google's control at all, even though it does depend on it for DNS SOA. Every site depends on root DNS servers to do their job right...the root for .ps was hacked...that's what happened here...google was affected, but not hacked.
  - dsl 13y ago
    You are using these words, but I don't think you know what they mean. The SOA record is almost irrelevant in this case, unless you are seeing some trickery where they set high TTLs or something to keep the "hack" around longer after it has been corrected. There is only one root (which is kinda what makes it a root) - and in this case the root servers are doing their job just fine. DNS is hardly even involved. As far as I can tell this was simply a compromise of the web UI that allows for the management of domains under the .ps ccTLD. Probably just another sloppy front end developer.
    - reflectiv 13y ago
      Forgive me, it has been several years since I dealt with DNS authority, however it still does not change the argument that it was not google who was 'hacked'...the title of this post is just blatantly wrong.
ck2 13y ago
Hacking a registry is even more alarming.
- baq 13y ago
  i would surely be more alarmed if google got hacked, not some 2.5-world registry. there's been worse, like CAs getting hacked.
- benatkin 13y ago
  Not all registries are created equal. I'm a heavy Internet user and I'd get along just fine without the .ps nameservers.
  - aray 13y ago
    Still, it goes to show that even if you lock down your website, you could still be vulnerable if your registry is vulnerable.
    - jonknee 13y ago
      That has been shown since the first day of DNS.

sp332 13y ago

If they hacked the .ps registry, did they redirect any other sites?

aray 13y ago
Looks like nike.com.ps (for example) still redirects to the nike homepage.

baddox 13y ago

I think saying "google.ps was hacked" is a perfectly reasonable way to describe what happened.

UVB-76 13y ago
That implies the site itself was hacked, when it was not. It appears the .ps domain registry was hacked.
reflectiv 13y ago
I don't agree at all, the system which was hacked is not in Google's control at all, even though it does depend on it for DNS SOA. Every site depends on root DNS servers to do their job right...the root for .ps was hacked...that's what happened here...google was affected, but not hacked.
- dsl 13y ago
  You are using these words, but I don't think you know what they mean. The SOA record is almost irrelevant in this case, unless you are seeing some trickery where they set high TTLs or something to keep the "hack" around longer after it has been corrected. There is only one root (which is kinda what makes it a root) - and in this case the root servers are doing their job just fine. DNS is hardly even involved. As far as I can tell this was simply a compromise of the web UI that allows for the management of domains under the .ps ccTLD. Probably just another sloppy front end developer.
  - reflectiv 13y ago
    Forgive me, it has been several years since I dealt with DNS authority, however it still does not change the argument that it was not google who was 'hacked'...the title of this post is just blatantly wrong.

ck2 13y ago

Hacking a registry is even more alarming.

baq 13y ago
i would surely be more alarmed if google got hacked, not some 2.5-world registry. there's been worse, like CAs getting hacked.
benatkin 13y ago
Not all registries are created equal. I'm a heavy Internet user and I'd get along just fine without the .ps nameservers.
- aray 13y ago
  Still, it goes to show that even if you lock down your website, you could still be vulnerable if your registry is vulnerable.
  - jonknee 13y ago
    That has been shown since the first day of DNS.