Registering a domain name lets you create a personal presence on the web. With your own web address, you can control your online identity by linking to any other site with more information about you. For example, you can register a domain name and forward it to a website, blog, or social profile page like your Facebook, LinkedIn, or Twitter pages. A domain name can protect your personal brand and help your career.
The top ten was rounded out by #8 Ecig.co.uk ($6,613 at DomainLore.co.uk) and two more Sedo sales - #9 Wallace .co at $5,999 and #10 Poianabrasov.ro at $5,632. Sedo went on to sweep 16 of 20 chart entries overall. UnicDomains filled three spots with sales they made on the Above.com Marketplace with their marquee sale of #4 AR.ca ($25,000) joined by #12 (tie) Playground.ca ($5,000) and #20 BlackMarket.ca at $3,500. 

Sedo is where I bought my domain - over Escrow - and is a global marketplace to buy, sell, and park domain names. They've over 18 million domain names for sale, but the big part is that they're a huge, well-respected company. This may not be important if you're spending $150 on a domain, but in a $15,000+ purchase - which happens in many cases - you will be potentially buying from a foreign entity, that you don't know, and many of them will suggest an escrow payment. This means you put the money in an account owned by a third party that will hold it and only pass it on once the domain has been transferred over into their name (which in this case is what Sedo does). This can be quite disconcerting - but Sedo is well-known and has done many, many deals - and the process is about as full of hand-holding as handing tens or hundreds of thousands of dollars for a domain name can be.


If you’re still with me then you might be wondering who came up with all of this. The answer is ICANN — the Internet Corporation for Assigned Names and Numbers. ICANN is a non-profit whose role is to coordinate all the names and numbers that keep the Internet online. They outsource a lot of the heavy domain name lifting to registries like Verisign, who pay ICANN for the privilege.
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 host names 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.
Critics often claim abuse of administrative power over domain names. Particularly noteworthy was the VeriSign Site Finder system which redirected all unregistered .com and .net domains to a VeriSign webpage. For example, at a public meeting with VeriSign to air technical concerns about SiteFinder,[23] numerous people, active in the IETF and other technical bodies, explained how they were surprised by VeriSign's changing the fundamental behavior of a major component of Internet infrastructure, not having obtained the customary consensus. SiteFinder, at first, assumed every Internet query was for a website, and it monetized queries for incorrect domain names, taking the user to VeriSign's search site. Unfortunately, other applications, such as many implementations of email, treat a lack of response to a domain name query as an indication that the domain does not exist, and that the message can be treated as undeliverable. The original VeriSign implementation broke this assumption for mail, because it would always resolve an erroneous domain name to that of SiteFinder. While VeriSign later changed SiteFinder's behaviour with regard to email, there was still widespread protest about VeriSign's action being more in its financial interest than in the interest of the Internet infrastructure component for which VeriSign was the steward.
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 216.58.214.14, and your computer can then ask Google to send their homepage over.

A domain name consists of one or more labels, each of which is formed from the set of ASCII letters, digits, and hyphens (a-z, A-Z, 0-9, -), but not starting or ending with a hyphen. The labels are case-insensitive; for example, 'label' is equivalent to 'Label' or 'LABEL'. In the textual representation of a domain name, the labels are separated by a full stop (period).
Domain names put a friendly face on hard-to-remember numeric internet addresses. Every computer on the internet has a unique internet protocol (IP) number. A domain name represents one IP number or more. For example, the IP number for the domain name whitehouse.gov is 104.109.178.94. The whole purpose is to give users an easy-to-remember handle so that when sending an e-mail to, let's say, the President of the United States, you can type president@whitehouse.gov instead of the more unwieldy president@104.109.178.94.
More controversially, the new agreement guaranteed the renewal of Verisign’s contract in 2012 unless they were in “fundamental breach” of their obligations as a registry. A similar presumptive renewal clause in the 2012 agreement recently sealed Verisign’s control over .com until 2024. This kind of arrangement, ICANN say, incentivises registries to make long-term investments in infrastructure that benefit the Internet community.
Technical contact. The technical contact manages the name servers of a domain name. The functions of a technical contact include assuring conformance of the configurations of the domain name with the requirements of the domain registry, maintaining the domain zone records, and providing continuous functionality of the name servers (that leads to the accessibility of the domain name).
Editorial Disclosure: Inc. writes about products and services in this and other articles. These articles are editorially independent - that means editors and reporters research and write on these products free of any influence of any marketing or sales departments. In other words, no one is telling our reporters or editors what to write or to include any particular positive or negative information about these products or services in the article. The article's content is entirely at the discretion of the reporter and editor. You will notice, however, that sometimes we include links to these products and services in the articles. When readers click on these links, and buy these products or services, Inc may be compensated. This e-commerce based advertising model - like every other ad on our article pages - has no impact on our editorial coverage. Reporters and editors don't add those links, nor will they manage them. This advertising model, like others you see on Inc, supports the independent journalism you find on this site.
If you get a domain name that describes your company's business or name, people can remember the name easily and can return to your site without having to consult their documents. In fact, if you get a good name that describes your product or service, you might even get people who were trying their luck by typing "www.yourproductname.com" in their browser.

A fully qualified domain name (FQDN) is a domain name that is completely specified with all labels in the hierarchy of the DNS, having no parts omitted. Labels in the Domain Name System are case-insensitive, and may therefore be written in any desired capitalization method, but most commonly domain names are written in lowercase in technical contexts.[2]
×