If you ever did a whois on say google.com , miscrosoft.com or yahoo.com you have been most likely been exposed to some obscenity and there is nothing the owners of the named domains can do about it.
This is to say that they or their providers or the dns servers have not been in any way hacked or exploited , responsible for this is a feature (turned into a flaw in the light of this) in whois clients that returns everything within the namespace of the queried domain name.
It did not take long for malicious or plain disgruntled individuals to turn dns spammers by creating a google.com.my.spam.rant.whatever.text.example.com subdomain on their own example.com to spam google whois for example.
As the whois query searches for any entries containing google.com in this case, the subdomain on example.com would be returned too , it is expected behaviour of the program.
Inexplicably unexpected was the exploitation of this , however funny MICROSOFT.COM.SMELLS.SIMPLECODES.COM might look to you , there could have been ways to prevent this being displayed in the whois for microsoft.com
November 22, 2006, 11:51 am
dns spam defined
Trackbacks
The trackback uri for this entry ishttp://alexamancini.com/blog/trackback.php/1/27
Listed below are the weblogs that reference this post
Comments
Most lame explanation ever.
I think is good to know that big corporations can't control everything
very interesting, but I don't agree with you
Idetrorce
Idetrorce
Hello my friends :)
;)
;)
WHDZEy
good site dude
interesting site man
tickets_3.txt;2;2
tickets_4.txt;2;2
tickets_5.txt;2;2
on March 29, 2007, 4:19 pm