An important function of domain names is to provide easily recognizable and memorizable names to numerically addressed Internet resources. This abstraction allows any resource to be moved to a different physical location in the address topology of the network, globally or locally in an intranet. Such a move usually requires changing the IP address of a resource and the corresponding translation of this IP address to and from its domain name.
Domain names are often seen in analogy to real estate in that domain names are foundations on which a website can be built, and the highest quality domain names, like sought-after real estate, tend to carry significant value, usually due to their online brand-building potential, use in advertising, search engine optimization, and many other criteria.

The right to use a domain name is delegated by domain name registrars, which are accredited by the Internet Corporation for Assigned Names and Numbers (ICANN), the organization charged with overseeing the name and number systems of the Internet. In addition to ICANN, each top-level domain (TLD) is maintained and serviced technically by an administrative organization operating a registry. A registry is responsible for maintaining the database of names registered within the TLD it administers. The registry receives registration information from each domain name registrar authorized to assign names in the corresponding TLD and publishes the information using a special service, the WHOIS protocol.
The Internet Corporation for Assigned Names and Numbers (ICANN) is the organization that governs the rules and regulations for domain name registrations. ICANN requires, for various reasons including to determine ownership of a domain should a dispute transpire, that a publicly accessible database be maintained that contains the contact information of all domain registrants. In layman's terms this means your domain name will be searchable by anyone and those search results will include your full name, physical address and other contact information. In order to protect your privacy in this regard, Domain.com offers WHOIS Domain Privacy which then masks your information using our own and implements a procedure for you to control who is able to then gain access to your contact information via a WHOIS search. Whenever you buy a domain name, no matter what domain name registration service you use, you are subject to the same ICANN rules, for this reason it is important to use a reputable service who cares about your privacy. Domain.com always recommends enabling WHOIS Domain Privacy.
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.
By definition, a domain name is simply a human readable form of an IP address. In function it is the destination that you type into a web browser in order to visit a website, such a www.google.com. Metaphorically, it is very similar to how you would scroll to a contact in your cell phone rather than manually dialing the person by entering their full phone number; the phone number would be an IP address and the saved contact would be a domain name. Always buy a domain with a reputable domain registrar.

The practice of using a simple memorable abstraction of a host's numerical address on a computer network dates back to the ARPANET era, before the advent of today's commercial Internet. In the early network, each computer on the network retrieved the hosts file (host.txt) from a computer at SRI (now SRI International),[4][5] which mapped computer hostnames to numerical addresses. The rapid growth of the network made it impossible to maintain a centrally organized hostname registry and in 1983 the Domain Name System was introduced on the ARPANET and published by the Internet Engineering Task Force as RFC 882 and RFC 883.
×