How to register a domain you actually own

A registrar is not a DNS provider and not a web host

A domain registrar is a company accredited to register domain names on your behalf. You open an account, pick a name, pay for a year or more, and the registrar records you as the holder. Cloudflare, Namecheap, Porkbun, GoDaddy and Squarespace Domains are common ones; there are hundreds.

Two other jobs are easy to confuse with it. A DNS provider holds the records that say where the domain points; often that’s the registrar, but it doesn’t have to be. A web host runs the website itself. One company can do all three, and a website builder can do all three and sell you the domain as well. Registering a domain is only the first job. You don’t need to decide the other two today, and you don’t need to change anything about them when you do.

The registrar account should be yours

The domain is a record at a registry. The registrar account is where the controls are: renewal, transfer, locks, and the nameservers that decide where the domain points. Whoever holds that login holds the domain, whatever name is on the paperwork.

So the person or business that owns the website should create the registrar account, with their own email address and payment method. Not the developer, not the agency, not the builder. All of those can be given access later without being given the account. If someone else has already registered the domain for you, skip to the section on domains registered elsewhere.

Before you register

1. Pick the email address the account will use. It’s the master key: password resets and renewal notices go there. Use an address you’ll still control in five years. Don’t use a contractor’s address, a shared inbox that might be closed, or an address at the domain you’re about to register, because if the domain ever breaks, so does the email you’d need to fix it.
2. Decide who the registrant is. The registrant is the legal holder. For a business, use the business name and a business address. For a personal project, you. The details are mostly hidden from the public, but the registrar uses them to decide who the domain belongs to, so they need to be accurate.
3. Have a payment method you control ready. The domain renews from it every year.
4. Choose a registrar. Any established one will do. What matters: the account is yours, the renewal price is shown clearly before you pay, two-factor authentication is available, and you can transfer the domain out later. Cloudflare charges the registry’s wholesale price with no markup but requires you to use Cloudflare’s nameservers; most others charge a little more and let you use any nameservers. Don’t spend long on this.

Registering

1. Create the registrar account with the email address from above. Do this yourself, on your own computer.
2. Search for the domain and add it to the cart. Ignore add-ons you don’t understand; you can add hosting or email later, from anywhere.
3. Enter the registrant details decided above.
4. If the registrar offers “WHOIS privacy”, “domain privacy” or “contact protection”, turn it on. It’s free at many registrars.
5. Pay, and keep the receipt. It names the registrar, the domain and the expiry date.

You now hold the domain. It doesn’t point anywhere yet, and that’s fine. Before connecting it to anything, do the next section.

The same-day settings

Six settings, ten minutes, done once. Most domain losses trace back to one of these being off.

1. Confirm the account email and add a recovery method

Check the address on the account is the one you chose, and click the verification link the registrar sends. Then add a recovery method: a second email address or a phone number, also yours. Put a reminder in your calendar to check both once a year, because the recovery method you set up today is only useful if it still works when you need it.

2. Turn on two-factor authentication

Two-factor authentication, or 2FA, means logging in needs your password plus a code from an authenticator app or your phone. Turn it on. When you do, the registrar shows a set of recovery codes; save them in your password manager. If you lose your phone without them, getting back into the account can take weeks, and a stolen domain is far harder to recover than a stolen password.

3. Turn on auto-renew

Domains expire on a fixed date. Turn auto-renew on and put the expiry date in your calendar anyway. Registrars for the common domain endings are required to email you about a month and again about a week before expiry, and again afterwards if it wasn’t renewed. Those emails go to the account address, which is one more reason it needs to be a mailbox you read.

4. Check the payment method

Auto-renew only works if the card on file works. Note the card’s expiry date next to the domain’s. When you replace a card, the registrar is one of the places to update.

5. Check privacy is on

Under current rules, registrars must hide most personal registration data from the public record where privacy law requires it, and many hide it everywhere. In practice, for the common domain endings, your name, street address, phone and email aren’t shown; your country usually is. If the registrar offers a privacy setting on top of that, leave it on. Whatever is hidden publicly, the details on the account itself must stay accurate and yours.

6. Check the transfer lock is on

Most registrars lock new domains against transfer by default. Look for “transfer lock”, “domain lock” or “locked” in the domain’s settings and confirm it’s on. It stays on until the day you deliberately move the domain.

Nameservers: you don’t need to touch them today

Nameservers are the servers that answer the question “where does this domain point?”. A new domain uses the registrar’s own nameservers, and the registrar’s DNS panel is where you’ll later tell the domain which website and which email service to use.

Registering a domain does not require changing its nameservers. Connecting it to a website usually doesn’t either: most hosts ask you to add one or two records in the DNS panel you already have. Changing nameservers replaces every record at once, which is why it’s the step that takes sites and email offline when it’s done casually. Leave them where they are until a specific service asks for a change, and when one does, read how to change DNS safely first.

Giving a developer access without giving away the domain

A developer or agency will often need to add DNS records for the website. They do not need your login to do it. There are three ways to give access, in order of preference:

1. Add them as a user or delegate on your account. Many registrars let you invite another person by email and give them limited rights, such as managing DNS but not transferring or deleting the domain. GoDaddy calls this delegate access, Namecheap calls it share access, Cloudflare calls it account members, and others have their own name for it. At GoDaddy, for instance, a delegate can never see or change your password or payment methods, whatever level you give them. Look for “users”, “members”, “delegates” or “sharing” in the account settings. When the work is done, remove them.
2. Move DNS management, not the domain. If the registrar has no sharing feature, you can point the nameservers at a DNS provider that does, such as Cloudflare, and give the developer access there. The domain stays in your registrar account. Do this with the DNS guide open, because it’s a nameserver change.
3. Add the records yourself. Ask the developer to send you the exact records, as a list of type, name and value, and type them in. It takes five minutes and you learn where the panel is.

What not to do: share the account password, or let the developer change the account email to theirs “so notifications come to them”. Both hand over the domain.

When a builder or agency offers to handle the domain for you

Website builders, hosts and agencies will often offer to register the domain as part of setting up the site. It’s convenient, and it isn’t necessarily a problem. It becomes one when the domain ends up in their registrar account, under their email, on their card. That works until the relationship ends, the card expires, or the company changes hands, and then your address may lapse or sit in an account you can’t get into.

Before accepting the offer, ask two questions:

• Whose registrar account will the domain be in? If the answer is “yours, we just set it up”, good: make sure the account uses your email and you can log in to the registrar directly, not only through the builder.
• Can I transfer it out, and how? If the domain lives in the builder’s account, you want a written answer to this before you need it.

One more wrinkle: some builders and hosts sell domains as resellers of a larger registrar. The public record shows the registrar; the place you manage the domain is the builder. That’s fine as long as you know it, and it’s the reason the diagnostic guide has you check both.

If the domain is already registered in someone else’s account

The fix is a registrar transfer into an account you control, and it’s routine. Create your own registrar account first, with all the settings above turned on, then follow the transfer guide. It walks through the timing rules and the one step that can break the live site if done carelessly. If the other party is cooperative, some registrars can move a domain between two accounts at the same registrar in minutes, without a full transfer; ask them.

What to save

Put these in your password manager or wherever your business keeps its important records:

• The registrar’s name and the login address for the account.
• The account email, the recovery email or phone, and where the 2FA recovery codes are.
• The domain’s expiry date and the payment method that renews it.
• The nameservers the domain uses today, so you know where DNS is managed.
• The receipt from registration.
• Who else has access to the account, what they can do, and why.

Checklist

Sources

The rules and product behaviour described above were checked against these pages when the guide was last updated. If something here has changed, these are the places to look.

• Expired Registration Recovery Policy · ICANN
• Registration Data Policy · ICANN
• Cloudflare Registrar FAQ · Cloudflare
• Manage account members · Cloudflare
• Invite a delegate to access my GoDaddy account · GoDaddy
• How do I share access to my domain with other users? · Namecheap
• Identify your domain registrar · Google Workspace Admin Help