« My Side of the Story | Main | Here's the Story of a Funny Lady »
August 26, 2005
Update:: Domain Hijacking noevilproductions.com
Well it turns out my domain was the victim of an attack but not permanently. The registry records were not changed and I am guessing that since this domain was not yet being used by me in October 2004, that use of inactive domains might be a special form of hijacking. Turns out it is not hijacking, and it's not pagejacking in the usual definition of the word. And it is not a 302 redirect exploit of the search engines, as I first suspected.
It is still a mystery wrapped in a conundrum and it is beyond me still as to WHY anyone would do this.
Of course with all of the accusations against me I am a bit paranoid. Sometimes you really are being followed! There are people who have been trying to find something that proves I am corrupt; finding (maybe creating) anything that questions my integrity.
I will find out the WHO. I have the WHERE, IP address of the server that served those pages of porn and I will do whatever it takes to clear my name and clear my company.
I am hoping that this is a random act of piracy made possible by the fact that I did not lock my domain. It will be a dark day if I discover that this was another attack on my integrity. Was this personal?
Posted by photocartoonist at August 26, 2005 6:53 PM
Comments
well here's another example of not knowing enough to even ask the right questions and I really didn't know about DNS.
Domain Name Servers, like in a telephone book, look up where a site is hosted; what physical machine out there on the Web a website's files are actually on. Sounds simple huh? Well it actually is simple.
But as paranoid as I am it never even dawned on me until after I was talking to a security expert just HOW it is possible for the unscrupulous to use an inactive domain to make money. Ha, yes follow the money trail.
At this point I have tracked down the source but I have yet to get any explanation from them as to WHAT happened. I know part of the HOW it happened and even though there was an user-error on my part, I have been told that it couldn't have caused this issue directly on its own.
So WHAT did happen??
Posted by: Kat Caverly at September 7, 2005 3:30 PM