Do Not Build a Website on Someone Else's Domain Name Address

We've blogged a few times about the importance of owning the domain name your blog is on. This is a similar post. You should also never build a website on a domain name someone else owns. Why? Well, here's an example.

UK small businesses by the thousands no longer have a website. This past weekend they discovered that their websites had become collateral damage in a legal fight between a domain name company and its founder.

Websites on a subdomain of the domain name gb.com were all shut off recently. The former head of registrar CentralNIC took control of the domain name gb.com without warning all the business owners that had websites on the URL address.

GB.com URL addresses had been sold as an alternative to .co.uk by London-based CentralNIC. GB.com is not an officially recognised top level domain, but the URL address was used by some UK businesses who were unable to aquire the .uk domain name they wanted.

The sudden switch came completely without warning to .gb.com domain owners, which has left many irate and others contemplating legal action.

This is yet another example of why you shouldn't build a website on a domain address that you don't own and control. Use website hosting reviews to vett a website hosting company that will work for your website. Build your site using reliable web hosting on a domain that has been registered in your name and you control.

Do Not Build a Website on Someone Else's Domain Name Address

 

Add comment


Security code
Refresh