The fastest way to learn domain names is to take the subject in the order a domain actually lives: first what a domain name is, then how its parts and the companies behind it fit together, then how it is registered and owned, how it is pointed at a website and email, and finally how it is kept, moved and protected. This page is that learning path. Each stop below explains one idea in a few paragraphs and then sends you to the full DNAccess guide on that topic, so you can learn domain names step by step without reading everything at once. A domain name, in one sentence, is the human-readable address of a website, such as example.com, that the internet translates into the numeric address of a server.
Why Learn Domain Names in This Order
Most people meet domain names at the checkout page of a registrar, and that is the wrong place to start. The checkout asks for decisions about privacy, auto-renewal, nameservers and contact details before the buyer knows what any of them do. The result is a domain that works on day one and causes problems in year three.
In the recovery cases we handle at DNAccess, the trouble rarely begins with an attacker. It begins with an early decision nobody understood: a developer listed as the owner, a renewal tied to a personal card, or a contact email nobody reads. Learning domain names in the order they are used, from concept to ownership to maintenance, prevents those decisions. That is the logic of the path below.
Stop One: What a Domain Name Is
Every device on the internet is reached by an IP address (Internet Protocol address, the numeric address of a server, such as 192.0.2.10). People do not remember numbers well, so the Domain Name System, or DNS (the internet’s directory service), lets a name stand in for the number. When someone types a domain name into a browser, DNS looks up the current address and the browser connects to it.
Two points matter for beginners. First, a domain name is not a website; it is a pointer that can be aimed at a website, an email service, or nothing at all. Second, you do not buy a domain name outright. You register the right to use it for a fixed term and renew that right over time. The full explanation is in our guide to what a domain name is, which also covers why a domain is a business asset worth protecting.
Stop Two: The Parts of a Domain Name
A domain name is read from right to left. The last part, such as .com, .org or .uk, is the top-level domain, or TLD (the extension at the end of the name). The part to its left, such as “example” in example.com, is the second-level domain, which is the part you choose and register. Anything to the left of that, such as “shop” in shop.example.com, is a subdomain, which the owner can create freely without registering anything new.
Extensions fall into a few families. Generic TLDs such as .com and .net are open to anyone. Country-code TLDs such as .us, .ca and .de belong to countries and set their own rules. The newer generic TLDs, such as .shop, .law and .bank, were added through ICANN’s new gTLD program. The scale is large: there were 386.9 million domain name registrations across all TLDs at the end of 2025, including 161.0 million in .com alone, according to Verisign’s Domain Name Industry Brief release for the fourth quarter of 2025. Our guide to top-level domains compares the families and explains how to choose an extension.
Stop Three: Registrars, Registries and ICANN
Three kinds of organization stand behind every domain name. ICANN (the Internet Corporation for Assigned Names and Numbers) sets the policies for generic TLDs. A registry operates one TLD and keeps its master database; Verisign, for example, operates .com. A registrar is the retail company that sells registrations to the public and passes your instructions to the registry.
The practical lesson is that your relationship is with the registrar, and the registrar account is the control panel for the domain. Whoever can log in to that account can change where the domain points, unlock it, or move it to another company. Our guide to the difference between a registrar and a registry walks through how a change flows from one to the other and why resellers complicate recovery.
Stop Four: Registering a Domain Name
Once the roles are clear, registration makes sense. You search for an available name, choose an extension and a registrar, pick a term of one to ten years, enter the registrant details, and pay. Behind the scenes, the registrar creates the record at the registry, and the name begins to resolve once nameservers are set.
The choices made at this stage last for years. The name should be easy to spell and say aloud, free of hyphens and numbers where possible, and clear of anyone else’s trademark. The registrant details should name the person or business that is meant to own the domain. Our walk-through of how buying a domain name works covers each step of the purchase, what it costs, and what to do in the first hour after checkout.
Stop Five: Who Owns the Domain
Ownership is where beginners most often go wrong. The registrant (the person or organization recorded as the holder of the domain) is the legal owner. The account holder, the person who logs in at the registrar, can be someone else entirely. When a web developer registers a client’s domain in the developer’s own name or account, the client may discover years later that it does not control its own address.
The public record of a registration used to be called WHOIS. For generic TLDs it has now been replaced by a newer, structured lookup protocol; ICANN’s schedule set 28 January 2025 as the WHOIS services sunset date, according to ICANN’s notice on the 2013 RAA global amendment. Most records today show little about the owner. Only 10.8% of gTLD domains have identifying contact data for the actual registrant available through public lookups, according to the Interisle gTLD Registration Contact Data Study (2024). That makes your own records of ownership more important, not less. Our guide to domain name ownership explains how to check who owns your domain and how to fix the record if it is wrong.
Stop Six: Pointing the Domain at a Website and Email
A registered domain does nothing until DNS tells the internet where its services live. Nameservers (the servers that publish a domain’s DNS records) are set at the registrar. The records themselves are edited wherever those nameservers are hosted. An A record points the name to a web server’s IPv4 address, a CNAME record points one name to another, an MX record names the servers that accept the domain’s email, and TXT records carry verification and email-authentication data.
The key concept here is separation. The domain, the DNS host, the website host and the email provider can be four different companies, and changing one does not automatically change the others. That flexibility is useful, and it is also why a careless nameserver change can take a website and every mailbox offline at the same time. Our guide to nameservers and DNS records explains each record type, how resolution works, and how to change DNS safely. The Domain Name Basics hub also links a dedicated guide to how email on your own domain works.
Stop Seven: Renewal and Expiration
Because a registration runs for a fixed term, every domain needs a renewal plan. Registrars send reminder notices before expiration, and most offer auto-renewal, but auto-renewal only works if the payment card and the contact email are current. After expiration there is a grace period, and after deletion a 30-day redemption period, before the name is released to the public.
Once a name is released, it can be gone in seconds. A USENIX Security study found that 10.1% of deleted .com domains were re-registered on the same day they were deleted, and that over half of .org drop-day re-registrations occurred within the first 30 seconds, according to Lauinger et al., WHOIS Lost in Translation (2017). Our guide to domain renewal covers the full expiration timeline and how to set renewals so they cannot fail quietly.
Stop Eight: Transferring a Domain
Sooner or later most owners move a domain, either to a different registrar, to a different account, or to a new owner after a sale. Each is a different procedure. A move between registrars requires the domain to be unlocked and an authorization code (a password unique to the domain, also called an EPP code) to be given to the new registrar. A domain also cannot usually move between registrars within 60 days of being registered or transferred.
Transfers matter to a beginner for a second reason: the transfer is the moment a domain is most likely to be stolen. Every lock and code on a registration exists to stop an unauthorized one. Our guide to domain transfers explains the three kinds of transfer, the safeguards on each, and what to do when a transfer you did not request appears.
Where to Go After the Basics
With those eight stops behind you, the rest of domain names builds on familiar ground. Buyers can move on to the aftermarket: buying a name that is already taken, domain auctions, backorders and how domain names are valued. Owners can move on to security: multi-factor authentication on the registrar account, registrar and registry locks, DNSSEC (DNS Security Extensions, which let resolvers verify that DNS answers have not been altered), and monitoring for expiration and lookalike domains. A glossary of domain name terms rounds out the set. Every one of those guides is listed on the Domain Name Basics hub linked at the end of this page.
How DNAccess Helps
We wrote this learning path because the domain problems we are hired to fix, from lost ownership to missed renewals to stolen names, almost always trace back to a basic step that was skipped years earlier. For businesses that would rather not manage that detail themselves, our domain name management service audits who owns each domain, consolidates names into accounts the business controls, and keeps renewals, contacts and security settings in order. If you have a question about a domain you already hold, we can review its registration with you.
This article is part of the DNAccess Domain Name Basics guides, which explain how domain names, registrars and DNS work in plain English.