You pay someone to build a website. Does that mean your company also controls the name printed on its business cards? Not necessarily. The website and its domain name are different things, even when one supplier sells them together. Understanding that difference makes changing suppliers much less confusing.

Take the example name bakery.example. It is a label people can remember. The pages showing the bakery’s opening hours are content, kept on a computer that answers requests from visitors. That computer is called a server. The name helps visitors find the service; it is not the service itself. The same domain can also be used for email, such as [email protected]. 1

Before looking at account ownership, follow what the customer does. They type bakery.example into a browser, the program that displays web pages. The device asks the naming system for information needed to reach that name. Once it has a network address, it can contact the service at that address. The service then answers the request for a page. The address lookup and the request for the bakery’s opening hours are separate conversations. This naming system supplies the directions, not the opening hours. 1

That separation is useful. If the bakery changes the computer service holding its pages, the administrator can update the directions while customers keep the same name. The name on packaging does not have to change with every hosting arrangement. Hosting means providing the computer service on which the website runs. Registration means keeping the right to use the registered domain under the registration agreement. Neither is the same as writing the page’s text or designing its appearance. 1 16

A name, an address book and a website

An internet service needs a network address so other computers can contact it. People should not have to remember those addresses, especially when a business moves its website. A system looks up the information associated with a name instead. This is the Domain Name System, or DNS. Think of it as an address book: the familiar name can stay while the destination changes. Unlike a single printed book, DNS is maintained by many cooperating systems. 1

For the bakery, three separate jobs are involved. Someone maintains the registration that lets the business keep using its domain. Someone publishes its DNS information. Someone runs its website. Email is another service again. One company may do all these jobs, but paying for one does not tell you whether the others are included. Registration and renewal have their own arrangements. 1 16

This explains why “we are moving the website” need not mean “we are changing our email addresses.” The website destination can change while the mail information remains in place. The important part is preserving the information for the services that are not moving, rather than treating everything called “the domain” as one indivisible purchase. 1

What registration actually gives you

A domain registration is maintained for a specified period and needs renewal. The company through which you arrange it is called a registrar. The person or organization holding the registration is the registrant. These similar words describe different roles: the registrar provides the registration service; the registrant holds the registered name. ICANN cautions against casually putting a web designer or hosting company down as the registrant. 16 17

Suppose the bakery’s designer arranged everything years ago. That can be convenient. But if only the designer’s account and contact details are known, the bakery may struggle to manage the name after that relationship ends. A paid design invoice does not answer who is recorded as the registrant or how the business can recover access. This is a reason to clarify the arrangement, not a reason to avoid outside help. 17

Nor is registration a once-and-for-all purchase. Renewal dates, payment and current contact details matter. Automatic renewal is helpful, but it still depends on the payment and account arrangements working. The sensible check is that renewal actually completed, not merely that a switch once said “automatic.” Expiration and recovery terms should be checked for the particular registration; do not assume every domain ending follows one timetable. 16

Why the registration account matters during a move

Imagine that the bakery wants a new website but wants to keep receiving orders at the old email address. The new web supplier prepares the replacement pages. Someone with the necessary DNS access changes the web destination, leaving the mail instructions alone. The registration can remain with its existing registrar. Alternatively, the business may also choose to move the registration service, but that is a separate decision. A request to redesign the homepage does not automatically authorize or require all three changes. 1 17

This is why the practical meaning of “we control the domain” is more than seeing the website work today. The bakery needs an agreed way to keep the registration renewed and to authorize changes to its naming arrangements. A helpful designer can administer services on the company’s behalf, but the company should understand whose registration and accounts are involved. Being able to edit a page is not the same as being able to recover the registration account. 17

There is also a difference between a registration expiring and a website server failing. In a server failure the name may still point to the expected destination, but the destination does not answer usefully. Expiration can affect continued use of the name itself and services that depend on it. Recovery procedures, fees and deadlines depend on the registration arrangements. Do not use a working homepage as your only evidence that next year’s renewal is taken care of. 1 16

Protect the account behind the name

Protect the account used to administer the registration. ICANN recommends a strong, unique password and avoiding shared login details. Where your registrar offers additional sign-in protection, I recommend using it too. An extra check at sign-in means that the password alone is not enough to enter the account. 17

There is a particularly easy trap with recovery email. If the only way to recover the domain account is a message sent to [email protected], what happens when that same domain stops working? ICANN recommends a contact email address independent of the registered domain. For a business, that should be a protected contact the organization can keep using, not a forgotten personal mailbox belonging to someone who has left. 17

For example, an employee who leaves may have been the only person who could read renewal notices or approve account recovery. The solution is not to circulate that employee’s password. It is to arrange authorized access and recovery with the registrar and keep the business’s contact information current. Additional sign-in protection helps protect entry to the account; a workable recovery arrangement helps the rightful business regain entry when something goes wrong. Both need attention. 17

Ask the person who manages your website to show you where the domain is registered, who holds it and how your business would regain access if that person were unavailable. Keep the renewal date and recovery instructions somewhere your authorised replacement can find them. Do not put passwords in that explanation.

Sources

1 — RFC 1034 — Domain names: concepts and facilities

16 — ICANN — Renewing Domain Names

17 — ICANN — Do You Have a Domain Name? Here’s What You Need to Know