The character set allowed in the Domain Name System is based on ASCII and does not allow the representation of names and words of many languages in their native scripts or alphabets. ICANN approved the Internationalized domain name (IDNA) system, which maps Unicode strings used in application user interfaces into the valid DNS character set by an encoding called Punycode. For example, københavn.eu is mapped to xn--kbenhavn-54a.eu. Many registries have adopted IDNA.
1and1 have terrible customer service and billing, quite possibly the worst ever encountered. Their billing/invoice system is all over the place, their staff untrained and unwilling to resolve and their pricing is literally plucked out of thin air. Beware, pay 12 months in advance (not monthly) then cancel the direct debit or Paypal auto payment, otherwise they will rinse your pockets when you’re not looking &/or unexpectedly take an extra payment because of an ‘oversight’.
My personal preference is to register the name directly with a domain name registrar rather than through my web host. I've heard stories, in the past, of less-than-reputable web hosts that registered the domain under their own name, making them the owner of the domain rather than you (although I don't know if such web hosts still exist today). Registering direct with a domain name registrar allows me to make sure that I am registered as the owner, the administrative and technical contacts. Being the owner is vital — if someone else places himself as the owner (such as your web host), he can always decide to charge you some exorbitant fee for the use of the name later, and there is little you can do. The various other contacts are less vital, but may still play important roles, depending on your registrar. For example, for some registrars, the administrative contact's approval is required before a domain name is transferred out of a web host (or at least, it used to be). If he/she cannot be contacted, the technical contact is used.
When you type google.com into your browser, the domain is split into parts by the “dot”, from right to left. The first part is “com”, so your computer checks the root zone file to see which registry manages the .com TLD. It then checks with this registry to see where the next part, “google”, points to. The registry returns the IP address 18.104.22.168, and your computer can then ask Google to send their homepage over.
Now it’s time to see if your domain name choices are available. Once you’ve come up with a few strong domain candidates, it’s time to plug them into Namecheap’s domain name search bar. We will search available domain names for you and let you know if your first choice of second-level domain or TLD is available. We’ll also suggest some alternate TLDs you might try if your first domain choice isn’t available.