XeonBD Official Blog

21Jul/090

What is Domain Hijacking and how to Prevent it?

Losing a domain is an incredibly frustrating experience for domain owners. This article will help explain how this happens, and how you can keep it from happening to you.

There are three main ways that people lose domain names:

  • An owner allows the domain registration to lapse.
  • A domain is stolen after a hijacker gains access to the registry record.
  • An owner does not keep up-to-date contact information in their record and their record is deleted after the registrar concludes that contact with the owner is not possible.

The good news is that there are steps you can take to keep this from happening to you. The most basic way to avoid losing your domain is to keep track of expiration dates and maintain your contact information. One smart way to do this is to consolidate your domains at one high-quality registrar. This allows you to manage a domain portfolio more easily and comprehensively. But remember, your domain can be deleted if your contact data is out of date. Registrars now have to verify ownership annually.

A second and related tip is to make sure that you are listed as the Administrative Contact. If it is a corporate domain name, then make sure the business owner or a senior executive is the Administrative Contact; this person is authorized to modify the website hosting, the records and he or she can change the domain’s ownership.

Next, it is important to use a paid email account for your Administrative Contact email address whenever possible. Free email addresses can be suspended or deleted. If this happens, you will not receive notices from your registrar for renewal, and someone else could register that email address and then use it to request a domain transfer.

You can also place a registrar lock on your domain. This can help prevent it from being transferred, modified or deleted by a third party. It is also important that you make sure your registrar gives you the ability to unlock your domain at any time without having to call or email them (at DS-Hosting Solutions you can lock/unlock your domain at any time). Otherwise, when you sell a domain name you will have to wait for someone at the registrar to process your request, and then the transfer will take more time and most importantly, it will take more time for you to receive your payment.

It is also important for you to be an educated email user. Never respond to emails that ask you to click on a link or respond without investigating the source and fully understanding the e-mail’s contents. Be especially careful with domain-related emails that look official but are from an unknown source. Contact your registrar to find out what is happening and if the email is from them. Domain hijackers have been known to send out mass transfer requests hoping that a small number of people will actually accept the transfer request. Do not let yourself fall prey to this type of scam.

Another step you can take to make sure you do not lose your domain is putting your registrar on your email list of "approved senders". This will ensure that you receive emails from your registrar, including the all important registry renewal notices.

Finally, on a related note, it is a good idea to renew your domain early and for long periods of time.

Protect your domains by following these guidelines:

  1. Keep track of expiration dates and keep your contact information up-to date. (Consider domain consolidation.)
  2. Make sure you are listed as the Administrative Contact so that only you can modify the domain record or change ownership.
  3. Try to avoid using free-email addresses.
  4. Make use of registrar locks over which you have control.
  5. Be an educated email user: investigate email senders and email contents.
  6. Place your registrar on your "approved sender" email list and have emails from them go straight to your inbox.
  7. Renew your domain early and for long periods of time.
21Jul/090

What is suPHP and what are the benefits?

The earlier version was PHPsuExec but that is quickly being replaced by suPHP and the two do basically the same thing.
suPHP provides an additional layer of protection on servers. It causes php scripts to run under the account username instead of the user ‘nobody’ which is the user that apache/php would run under on a server that is not running suPHP. This feature allows us to more easily track any potential security breaches that come in via insecure php script(s) that a user is running.

suPHP also does away with the requirement of using 777 permissions on directories/files that need write permission. In fact if a directory and/or file has the permission set to (CHMOD) 777 and it is access via a browser, then an internal server error 500 will be generated. The highest level of permissions that a user can use on a suPHP enabled server is 755. This permission setting is sufficient enough for any directories/files that needs to be written to.

The benefit of using suPHP besides better security, is that it will make any PHP applications (most often CMS systems) such as Mambo more user friendly. Case in point: If you upload/install anything via Mambo such as a template on a non-suphp server, then those template files will be owned by ‘nobody’ and you will not be able to edit them manually or even delete them from your account. This ownership issue is done away with suPHP. On a suPHP enabled server, those same template files will be owned by the account username and the account holder will be able to manipulate those files as he sees fit.

No longer do you need to use (chmod) the dangerous file permission of 666 or the folder permission of 777 to make things writable.

The correct permissions should be:

  • Writable Folders: 755
  • Writable Files: 644
  • Files that need to be un-writable: 444