The short answer
Your business should own every account behind its website. Your web designer, host or marketing company should be added to those accounts as a user who can do the work, and removed when they stop. That way changing providers is a matter of removing someone's access, not asking for things back.
In practice that means five logins in your name: the domain registrar, the DNS (often in the same account), the hosting or the plan that includes it, your email admin, and access to your site files. Most small businesses we talk to don't have all five. That's common and fixable, and the step-by-step section below covers how.
The pieces behind every website
A website looks like one thing, but it's several services joined together. When something breaks or you want to change designers, the question is always which piece, and who holds its login.
| The piece | What it is | Who should hold the login | If you don't |
|---|---|---|---|
| Registrar account (the domain) | The company you rent your domain name from, renewed yearly | You, in the business's name, with your own email | It can lapse, or be held when you change designers |
| DNS | The settings that point the domain at your website and your email | Usually lives in the registrar or Cloudflare account. You own it; your designer gets access | Nobody can move the site or fix email without the person who has it |
| Hosting account | Where the site's files are served from | You, or a provider whose contract says the site is yours | Your site is only as available as that relationship |
| Email (Google Workspace or Microsoft 365) | Your mailboxes at your own domain | You, as the main admin. Add a second admin you trust | You can't add staff, reset passwords or recover old mail |
| Site files | The pages, images and code, or the export of them | A copy you can get on request, owned by you in the contract | You rebuild from scratch when you leave |
| Google Business Profile, Search Console, Analytics | Your listing on Maps and your search data | You as owner; your designer as a manager | You can lose control of your listing, its reviews and your data |
The rule of thumb: you own every account, your designer or provider is added as a user. When you part ways, you remove their access. You never have to ask for anything back.
Two of these trip people up most. First, the domain and the website are separate. You can keep the same domain for twenty years while the site moves between three platforms. Second, email usually has nothing to do with the website, except that both use your domain. Moving the site should never touch your email, and if it does, a record got changed that shouldn't have.

Why it matters more than it seems
When everything works, nobody thinks about who owns what. The problem shows up on a bad day, and these are the usual ones:
- The designer moves on. They registered the domain in their own account years ago, and now they don't answer emails. Your site and email keep running until the renewal date, and then they don't.
- The domain lapses. The renewal notice went to an old employee's inbox, or the card on file expired. After a grace period, a lapsed domain can be registered by someone else.
- You want to leave, and can't easily. The provider owns the account, so leaving means asking them to hand things over, on their schedule.
- Email breaks during a move. Someone changed the nameservers and didn't copy the email records. Mail bounces for a day before anyone notices.
- You sell the business. A buyer will want the domain, the email, the listings and the site in clean order. Untangling them during a sale is stressful.
None of these needs anyone to act in bad faith. Most come from a well-meaning designer setting things up quickly in the account they already had. That's why it's worth checking now, while everyone is friendly.
The domain: registrant, registrar and WHOIS
Three terms come up whenever you deal with a domain. They're simpler than they sound.
- Registrant. The person or business the domain is registered to. This is the legal holder. It should be your business.
- Registrar. The company you register and renew the domain through, such as the one your designer or builder used. You can move between registrars.
- Registry. The organization that runs an ending like .com. You don't deal with it directly.
Above all of them sits ICANN, the nonprofit that sets the rules accredited registrars follow for endings like .com, .net and .org, including how domains move between registrars. Some country endings have their own rules, so check if yours isn't one of the common ones.
WHOIS is the public lookup for domain records. You can search any domain at ICANN's lookup tool and see which registrar it's with, when it was registered and when it expires. Since privacy rules tightened, the owner's personal details are usually hidden, so the lookup tells you where the domain is, not always whose it is. To see who the registrant is, you need to log in to the registrar account, or ask whoever has.
The registrant's email address matters more than people think. Renewal notices, transfer approvals and security alerts go there. If it's your old designer's address, they get the messages instead of you. A domain is typically about $15 a year, so it's an easy thing to own yourself and a costly thing to lose.
DNS: the address book behind the domain
DNS is the set of records that says where your domain's website and email live. It sits wherever your domain's nameservers point: often the registrar, sometimes Cloudflare or your host. When a designer "points your domain" at a new site, they're editing these records.
| Record | What it does | Why you care |
|---|---|---|
| Nameservers (NS) | Says which company answers for the domain's DNS | Change these and every other record must already exist at the new place |
| A and AAAA | Points the domain at a server address | This is usually what sends visitors to your site |
| CNAME | Points a name, often www, at another name | Common for hosts and for service verification |
| MX | Says which servers receive your email | Get these wrong and mail stops arriving |
| TXT | Text notes, including SPF, DKIM and DMARC for email, and ownership checks for Google and others | Missing email records send your mail to spam |
| TTL | How long the internet caches each record | Lower it a day before a move so changes take effect faster |
Every DNS provider shows these in a list. Before any move, export or screenshot the whole list. It takes two minutes and it is the step that prevents most email outages.
The one habit worth having: before anyone changes nameservers or moves the domain, export or photograph every DNS record. Moving the website only needs the A, AAAA or CNAME records changed. Email relies on the MX and TXT records staying exactly as they are. Problems almost always come from switching nameservers to a new provider before the old records were copied over.
Email: keep it separate, and keep the admin
For a business, email should run on a proper mail service at your own domain. For most small businesses that's Google Workspace or Microsoft 365. Both are built for this, both let you add and remove staff, and both are independent of your website, so a site change never puts your mail at risk.
What to check on your email account:
- You're the main admin. Not your designer, not an IT contractor who left. The admin can add mailboxes, reset passwords and recover deleted mail.
- There's a second admin. A partner or trusted manager, so one locked-out phone doesn't lock out the business.
- Billing is on your card. If someone else pays, they can cancel it.
- SPF, DKIM and DMARC records are set. These TXT records prove your mail is really from you. Without them, more of your messages land in spam. Your mail provider's admin console tells you exactly which records to add.
Email bundled with cheap web hosting can work, but it ties your mail to your host. If you ever change hosts, your email moves too, which makes a simple website change much riskier. We don't run email servers ourselves, but we help clients set up Google Workspace or Microsoft 365 and check the records are right.
Hosting and the site files
Who holds the hosting depends on the platform. On Wix or Squarespace the hosting is the platform, so the account itself should be in your name. On WordPress it's usually a separate hosting account, and it should be yours, with your designer added. On a managed plan like ours, the hosting is part of the service, and what matters is the contract.
For the files, ask one question: if we stopped working together tomorrow, what would I get? Good answers are specific: a full copy of the site files, an export of the content, the original images. On a builder, the honest answer is your words and photos, because the site itself can only run on that platform. Our platform comparison covers what each one lets you take, and our rent vs own page explains why it matters over time.
Check where you stand
Go through this list with your logins in front of you. If you can't tick a line, that's the thing to fix first.
Ownership check: tick every line
- You can log in to the registrar account yourself, and it's in the business's name.
- The registrant contact on the domain is your business, with an email address you check.
- Auto-renew is on, with a card that won't expire before the next renewal.
- You know where the DNS is managed, and you can log in there.
- You're the main admin of your Google Workspace or Microsoft 365 account, with a second trusted admin.
- Your Google Business Profile lists you as owner, not your designer.
- Your contract says the site files and content are yours, and you can get a copy on request.
- The logins are written down somewhere safe that someone else in the business can reach.
How to get control back, step by step
If a past designer, host or marketing company still holds some of these, here's the order to work in. Stay polite and put requests in writing. Most hand-overs go smoothly once someone asks clearly.
- Find out where everything is. Look up your domain at lookup.icann.org to see the registrar and expiry date. Any free DNS lookup will show where the nameservers, website and MX records point. Write it all down.
- Note the expiry date. If the domain renews within a month or two, deal with the domain first, and make sure it's renewed whoever's account it's in.
- Ask in writing for what you need. Be specific: ownership of the registrar account, or the domain moved into an account in your name; admin on your email; owner on your Google Business Profile; a copy of the site files. Give a reasonable date.
- Take the easy route if it exists. Many registrars can move a domain from one customer account to another at the same registrar. That's often quicker than a transfer and changes nothing technical.
- Or transfer it to a registrar you choose. The domain has to be unlocked at the current registrar, which then gives you an authorization code (also called an auth or EPP code). You start the transfer at the new registrar, enter the code, and approve it from the registrant email. For common endings like .com, a transfer usually includes a year's renewal, so you lose no time already paid for, and it often completes within about a week.
- Copy every DNS record before anything moves. Export or screenshot the full list, then recreate it at the new DNS provider and check it matches before you switch nameservers.
- Protect email first. Copy the MX records and the SPF, DKIM and DMARC TXT records exactly. After the switch, send test mail in and out from an outside address.
- Tidy up. Change passwords, turn on two-step login, update the registrant email, remove old users, and turn auto-renew on.
A timing note: under ICANN's transfer rules, a domain generally can't move to another registrar within 60 days of being registered or last transferred, and some registrars apply a similar lock after owner details change. If a transfer is refused, that's the usual reason, and moving it between accounts at the same registrar may still work.
If they won't or can't help
If you are the listed registrant, the registrar has a process for verifying you and restoring access, and you should contact them directly with proof of who you are and that you're the business named. If the domain was registered in the designer's own name, you'll need them to transfer it, and invoices or a contract showing the domain was for your business help. For a Google Business Profile, Google has its own ownership request process. Start early. These take longer than an email.
Worked example
A plumbing company in Elk River wants a new site. Their old designer built the first one years ago and registered the domain in the designer's own registrar account. Their email runs on Google Workspace, set up by the same designer, who is still the only admin.
The order we'd suggest: ask the designer to make the owner a super admin on Workspace (five minutes on their side, and it protects the mail first). Then ask them to move the domain into a new account in the business's name at the same registrar, or unlock it and send the authorization code. Before anything else changes, export the DNS list, especially the MX and TXT records for Workspace. Only once the domain is in the owner's account does the new website get pointed at, with the email records untouched. Nothing goes down, and the owner holds every key.
How we handle ownership
On every site we build, the domain is registered in your name, typically about $15 a year, and you own your domain, content and site files outright. If you cancel, you get the files and help moving them. We don't run email servers, but we help set up Google Workspace or Microsoft 365 and make sure your records are right before and after launch.
A lot of our redesign work starts with untangling exactly this: finding the domain, copying the records, and moving it into the owner's name before anything else changes. After launch, our care plans keep the hosting, backups, monitoring and HTTPS running, and you stay the owner of every account. Contractors and home services businesses are the ones we see this with most, usually after a designer from years ago moved on. If you're not sure where your pieces are, our Website Launch Checklist has the domain and email checks to run, or send us your domain and we'll look.
Want a straight answer for your business?
Every Stonekept build is custom-coded, hosted on Cloudflare and kept on a monthly plan. Prices are public: builds from $2,200 with care from $199/mo. See pricing or tell us about your project and we'll give you an honest read, even if that's not us.
