Your business should normally control its own domain name and the account used to register it. A web designer can manage the technical setup, but the business should not be dependent on that designer simply to retain access to its own web address.
Your domain may look like a small technical detail.
It is not.
For many businesses it becomes one of the most important digital assets they have.
It is the address customers know.
It may also be connected to business email.
It appears on printed material, invoices, advertising, Google listings and social profiles.
Losing control of it can create a much bigger problem than losing access to the website design itself.
The domain is not the website
This distinction matters.
yourbusiness.ie is the domain.
The website is the content and technology displayed when someone visits it.
The domain can point to one hosting provider today and another tomorrow.
That is possible because DNS connects the domain to the services behind it.
So changing web designer does not require changing the public domain.
Provided, of course, that the business controls it.
What does "owning the domain" actually mean?
Strictly speaking, a domain is usually registered for renewable periods rather than purchased forever.
The useful practical question is:
Who controls the registrar account and registration?
That account should ideally belong to the business or be accessible to the business.
The business should know which registrar is being used.
It should know which email address receives renewal and security notices.
It should have a way to regain access without asking a former web developer for permission.
That is the level of control that matters day to day.
Worth knowing
Convenience at setup can quietly become dependency later. I have no issue with a designer handling the technical work, but I think the business should still be able to recover the registrar account without needing that designer's permission. The owner does not need to understand DNS records or nameservers; they do need a credible route back to control of the name their customers use.
Why do web designers sometimes register domains for clients?
Often because it is convenient.
The client says:
Can you just sort all of that out?
The designer registers the domain inside their account, configures it and launches the site.
Nothing malicious has happened.
The problem appears years later.
The designer retires.
The agency closes.
The relationship breaks down.
The client wants to move supplier.
Nobody remembers which account holds the domain.
Convenience at the start can create dependency later.
The domain should not be leverage
I strongly dislike arrangements where a client is frightened to move provider because they do not know whether they will keep the domain.
A domain should not become a bargaining chip.
If the business has paid for and built its identity around that address, the ownership/control arrangement should be clear from the beginning.
That is one of the simplest ways to avoid an ugly supplier dispute later.
What if the web designer pays the renewal for me?
That can be fine.
Managed domain renewal can be a genuine service.
The important issue is not who clicks the renewal button.
It is who ultimately controls the asset and what happens if the management arrangement ends.
A provider could manage the domain on behalf of the client while still keeping ownership and access clearly documented.
Convenience and control are not opposites.
Use an email address the business controls
This is easy to overlook.
If the registrar account uses the web designer's personal email address, password recovery and security notifications may also depend on that person.
Ideally, use an email address controlled by the business.
There is one practical complication:
do not make the only recovery address an email account that itself depends on the domain you are trying to recover.
For important accounts, recovery arrangements should be thought through properly.
Two-factor authentication matters
Registrar access is sensitive.
If somebody gains control of the account, they may be able to change where the domain points.
Use a strong unique password and enable two-factor authentication where available.
The business should also know where the recovery codes or backup access method lives.
Again, the owner does not need to become a DNS engineer.
Basic account security is enough.
What about Cloudflare?
A business can register a domain with one provider and use Cloudflare for DNS.
Or, depending on the domain and setup, Cloudflare may also be involved at the registrar level.
Those are separate roles.
This is why I want clients to understand the broad setup rather than simply hear:
It's on Cloudflare.
Which account controls registration?
Which controls DNS?
Where is the site deployed?
Those are the useful questions.
What I'd do
If a provider currently controls the domain, I would identify the registrar first, confirm the renewal contact and recover business-controlled access before changing anything technical. I would also record the existing DNS setup so a transfer of control does not accidentally break the website or business email. Ownership problems are much easier to solve while the site is still working and the relationship with the provider is healthy.
What if my agency owns the domain now?
Do not panic.
First identify the registrar and ask the provider how the domain is currently registered.
If the relationship is good, this may be a straightforward administrative transfer.
Get the account structure clarified before changing anything.
Do not start randomly changing nameservers or records if business email also uses the domain.
That can create unnecessary downtime.
Should the business name match the registrant?
Registration rules and displayed registration data vary by domain extension and registrar.
The practical aim is still the same:
the business should have clear legitimate control and a documented right to retain the domain.
If there is any dispute about legal ownership, contracts or registration rights, that moves beyond ordinary web-development advice and into something that may require the registrar, registry or legal advice.
Domain control and website ownership are different
You can control the domain and still not own every part of the website.
Images may be licensed.
Software may have separate licences.
A developer may retain rights to some code unless the contract says otherwise.
That broader question deserves its own guide: who owns a website after it is built?.
The domain is simpler.
I want the business to control it.
How Built by Gavin approaches domain ownership
My preference is for client-controlled accounts.
I can handle the setup.
The client should not need to understand DNS records.
But the business should not have to depend on my continued existence to retain its domain.
That is part of the wider Built by Gavin philosophy around ownership.
Good technical service should make the client's position stronger.
Not create a future reason they cannot leave.
Why this matters if a developer disappears
If the business controls the domain, you already have one of the most important pieces needed to recover.
A new developer can potentially point the domain toward a replacement website.
If the old developer controls the domain and stops responding, the recovery problem becomes much more serious.
I cover that scenario properly in what happens if your web designer disappears.
The bottom line
Your business should normally control its domain registration and registrar account.
Let your developer manage the technical details if that is convenient.
But know where the domain is registered.
Use business-controlled access.
Secure the account.
Understand who is responsible for renewal.
And make sure changing supplier does not mean negotiating for your own web address.
Not sure who controls your domain right now?
Send me the domain and I can help you understand the setup before anything is changed.
If I build the new site, domain control is something I would rather make clear at the beginning than turn into a problem years later.
---