Domain, Hosting and Website: Which Bill Does What?

There are two or three charges a year connected to your website and you could not confidently say what any of them does. One renews in March, one in August, and one arrives from a company whose name you half recognise. Now a new provider has asked where your domain is registered and you do not know. Every article about this explains the difference between a domain and hosting as though you were about to buy them, which is not your situation. You already have all of it. Your question is which bill keeps the site up, which keeps the email working, and what happens if you cancel the wrong one.

The reason this is worth half an hour is that the charges do very different jobs and only some of them are recoverable quickly.

The domain registration is your address. If it lapses, the site and every email address on it stop working at once, and getting it back can be complicated or impossible. This is the one to protect above all others.

The hosting or platform is where the site actually runs. If it lapses, the site goes down and the domain still points at nothing. Recoverable, if you have a backup.

The email service is often a separate arrangement, sometimes bundled with the domain and sometimes not. This is the one people accidentally break, because email depends on records attached to the domain rather than on the website.

Anything else, analytics, backups, plugins, a booking tool, is usually inconvenient rather than fatal.

So, the order of caution is clear before you know anything else: never let the domain lapse, never change its records casually, and never cancel a service that might be carrying your email.

Start with the free thirty-second check, because it settles the most important question without touching anything.

Look your domain up in ICANN Lookup. It reports the registrar of record for many domain types, the registration and expiry dates, the nameservers and the domain status. Privacy rules limit what registrant details are shown for many domains, so you may not see a name, but the registrar and the nameservers are usually visible and those are the two facts you need.

The registrar tells you which company holds the registration. The nameservers usually tell you which company is answering for the domain, which is frequently a different one.

Then work through your own records rather than your memory. Card and bank statements for the last year, looking at the descriptor on each recurring charge. Renewal emails, which are usually filed somewhere you can search. The email address each account is registered to, which is the single most important detail and often belongs to somebody who left.

Write it down as you go. What you are building is a map, and the map is the deliverable.

One distinction worth holding onto: the person paying an invoice is not necessarily the registered owner of the domain. Those are separate roles under ICANN's policies, and only the registered holder, or in some cases an authorised contact, can approve a transfer. Discovering that gap early is much better than discovering it during a move.

Once you know who holds what, the map takes a specific shape, and each row has an owner and a recovery route.

The domain registration has a registrar, a registrant, an account email, a recovery method and a renewal date. It also has a lock status, which is what stops it being moved without your say-so.

The hosting or platform account has a provider, an account holder, a login email, a plan and a renewal date. On a bundled provider this can look like the same thing as the domain and be separately cancellable.

The site itself, meaning the code, theme, configuration and settings. Ask whether an export exists and whether it has ever been tested.

The content, meaning your words, photographs, blog posts and product information. This is the row people forget until it is gone, and it is the hardest to recreate because nobody else has it.

Two things to note while mapping. A site can be reached on a platform subdomain without a custom domain at all, and a domain can stay registered with no site behind it. Those are normal states rather than faults, and forcing every arrangement into one product model is how people cancel something they needed. The same ownership logic runs through who owns your website, and this map is the practical version of it.

If you are changing providers, the order below keeps the site and the email up throughout, which is the only requirement that really matters.

Freeze changes first and capture the current state: the live addresses, the renewal notices, the statement descriptors, the login emails and a screenshot of the working site.

Then confirm control with somebody authorised. The registrant email, the recovery email, the two-factor method, the renewal date, and whether you can obtain a transfer authorisation code. That last one is the practical test of whether you control the domain.

Then inventory the dependencies before moving anything: export the content where the platform supports it, take a backup, list the DNS records, and list every mailbox and integration that depends on the domain.

Then build and test the replacement on a temporary address. Key pages, forms, email sending and receiving, payments if you take them, and backups.

Then change only the records that need changing, at a scheduled time, and verify the site, the secure connection, the forms, the email and any third-party services afterwards.

Then, and only then, cancel the old service. Keep both running for a month. The overlap costs one month's subscription and it is the cheapest insurance in this entire process.

Some of the deadlines here are set by policy rather than by anybody's preference, and they are worth knowing because they explain why a move cannot always happen when you want it to.

That 60-day window catches people out. If a domain was registered or moved recently, a further transfer can be blocked, so a promise to move everything next week may be impossible for reasons nobody controls.

There is no market price for sorting this out, because it might be an account audit, a registrar transfer, a migration, a rebuild, a recovery, or several of those.

What the published platform prices show is why one bill can contain several things. WordPress.com's pricing page, observed on 3 September 2026, lists a free plan at $0, Personal at $4 a month billed annually, Premium at $8, Business at $25 and Commerce at $45, with different figures for monthly and multi-year billing, and notes a custom domain free for the first year on paid plans.

That last detail is the one to sit with. A domain that is free for the first year is not free in the second, and a plan that includes a domain is a bundle rather than a single product. When you cancel the plan, you need to know what happens to the domain inside it.

On professional work, the cheap end is an account inventory where the credentials exist and nothing moves. The expensive end is missing ownership access, expired services, email and DNS dependencies, a platform-specific export, assets that have to be reconstructed, a shop or booking system, or a redesign bolted on. Ask for those as separate lines rather than as one figure, which is the same discipline as what a website costs you every month.

Everything in this group is safe, free, and discovers facts without altering a live service.

Run the ICANN Lookup. Collect the statements and renewal emails. List every login email and recovery method. Ask to be added to accounts you are not on, as your own user rather than by sharing a password. Record the nameservers and the DNS records as they are today. Download the platform's documented content export. Store the whole thing as a dated ownership map.

Then stop. Do not cancel a service. Do not edit nameservers or delete DNS records. Do not change a registrant or recovery email. Do not unlock a domain because an email asked you to. And do not move an email service without a tested plan, because email failures are the least visible and the most damaging: nobody tells you their message bounced.

One specific caution, because it is how domains get stolen. A transfer should only ever be started by you, from inside a registrar account you already know, never by clicking a link in an unexpected message about your domain expiring.

If the accounts are held by somebody you cannot reach, that is its own situation and the recovery routes are in what to do when your web designer disappears.

Three clauses matter more than the rest, and they are all about what happens when the relationship changes.

Who is the registered holder. Not who pays, not who set it up. The registrant. It should be your business, and if it is not, correcting that is the most valuable single change available to you.

What happens at renewal. Automatic or not, at what price, and to which card. A domain that lapses because the card on file expired is one of the most common avoidable disasters here.

What happens at exit. Whether you receive the domain, the content export, the site files and the account access, and within what period. Get it in writing before you need it, because after a disagreement is the worst time to be asking.

Alongside those, keep a copy of every export and renewal receipt somewhere that is not the account itself. An export stored only inside the platform you are leaving is not really a backup.

One local point, because it causes a specific and understandable confusion.

If your business trades under a name that is not its legal name, you file an assumed name certificate. Tarrant County handles that filing for unincorporated businesses, while the Texas Secretary of State explains that corporations and limited liability companies file with the Secretary of State instead.

That filing identifies your business publicly. It does not grant exclusive rights to the name, and it does not establish that you own a matching domain. Domains are governed by contract with a registrar and by ICANN's global policies, not by a county or a state record.

Which also means there is no local office to appeal to in a domain dispute. No Arlington programme administers domains or hosting, and the City's economic development resources cannot change a registrar record. That is worth knowing so nobody spends a week asking the wrong people.

Everything above becomes a permanent asset if you write it down once.

One page. For each of the four records: the provider, the account holder, the login email, the recovery method, the renewal date, and roughly what it costs. Add the registrar and nameservers from the lookup. Date it.

Store it somewhere that survives a person leaving and an account being locked. A shared drive the business owns, or a printed copy in the folder with the insurance documents.

Review it once a year, ideally near your domain renewal date, which conveniently arrives with a reminder attached. Check the card on file is current and the account email is somebody who still works there.

You will know it is right when a new provider asks where your domain is registered and you answer from the page rather than from a search.

Are hosting and a domain the same thing?

No. The domain is the address; the hosting is where the site actually runs. They are frequently sold together by one company, which is why one bill can quietly cover both.

Do I need both?

To have a site on your own name, yes. A site can exist on a platform subdomain with no custom domain, and a domain can stay registered with nothing behind it. Both are normal.

How do I find out who owns my domain?

Start with ICANN Lookup, which shows the registrar and nameservers for many domains, though privacy rules often hide the registrant name. Then find the account email, which is the practical proof of control.

If I cancel my website plan, do I lose my domain?

It depends on how it was sold. A domain included with a plan, particularly a free-for-the-first-year one, is a bundle. Establish where the registration sits before cancelling anything.

Will moving my website break my email?

It can, because email depends on records attached to your domain rather than on the website. List every mailbox and record first, and test sending and receiving before you cancel the old arrangement.

How long does a domain transfer take?

The registry completes it after five calendar days unless it receives a denial, and provider steps can come before that. A domain registered or transferred recently can be blocked for up to 60 days.

The confusion is not really about vocabulary. It is that four separate things arrive on two or three invoices, and one of them can take your business email down.

Spend the afternoon finding out who holds each. The lookup is free and instant, the statements and renewal emails do most of the rest, and the account email addresses are the part worth chasing hardest.

Then change nothing until the map is complete, keep the old arrangement running for a month past any move, and write the whole thing on one page you can find in three years.

If the map turns out to have a hole in it, a domain in somebody else's name or an account nobody can get into, Arlington Website Designer works with businesses around Arlington, TX and untangling this is a common first job. Send us the domain and what you know through the contact page, and you will get back what the public records show, which records are missing, and what order to fix them in.