Who Should Own the Client's Domain: Agency or Client?

It is one of the most common friction points between agencies and clients: who registers the domain, and in whose name? Handled badly, it leads to ransom-style disputes, lapsed domains and awkward handovers. Handled well, nobody thinks about it.

*This is practical guidance, not legal advice. Check your contracts and local law for anything high-stakes.*

Two things people confuse

Registrant: the legal owner of the domain, the name in the registration record.

Account holder: whoever controls the registrar login that can renew, change DNS and transfer the domain.

They can be different. A client can be the registrant while the agency manages the domain through delegated access. Many ownership disputes come from these two being mixed up.

Option 1: The agency registers and owns the domain

Pros - Simple for the client, with nothing to set up - The agency controls renewals and DNS - Easy to bundle into a maintenance plan

Cons - Clients may feel locked in, and some will be suspicious - Legal ambiguity if the agency is the registrant on the client's brand name - If the agency closes, is sold or forgets, the client's domain is at risk - Disputes arise when the relationship ends

Option 2: The client registers and owns the domain

Pros - Clear, defensible ownership - No lock-in, which builds trust - No liability for the agency if the client's brand is challenged

Cons - Clients sometimes do not renew, or forget their login - Agency may need chasing for credentials - Renewal reminders go to the client's inbox, possibly unread

Option 3 (recommended): Client is the registrant, agency has managed access

For most agencies, the safest arrangement is:

The client is the registrant, with their legal details and a monitored contact email.
The domain lives in a registrar account the client controls, or in a shared team account where the client is the listed owner.
The agency gets delegated access (many registrars offer user roles) or a documented procedure.
Renewal responsibility and payment are written down.
The agency still tracks the expiry date and alerts both sides.

This protects the client from lock-in and the agency from blame, and avoids the situation where a domain is stuck in a freelancer's personal account.

When agency-owned can be reasonable

There are legitimate cases: a managed service where the domain is clearly part of the package, a temporary staging or campaign domain, or a white-label arrangement. If you go this route, put it in the contract:

Who is the registrant and who is the beneficial owner
That the client may request a transfer at any time
Transfer timelines and any admin fee
What happens if the agency closes or the contract ends

What to put in your contract

Domain ownership: who is the registrant and who pays
Renewal responsibility, price and notice period
Access: who holds credentials, how they are shared
Transfer procedure on termination, with a deadline
Handling of related assets: DNS, email, SSL and hosting
Consequences of non-payment (see billing clients for renewals)

How to hand over a domain cleanly

Confirm the client's registrant details are correct.
Unlock the domain at the registrar.
Provide the transfer authorization code (EPP/auth code) through a secure channel.
Be aware that many registrars apply a transfer lock of up to 60 days after a registrant change, unless the change is opted out. Plan for it.
Copy DNS records before the move, and keep email and website running during the switch.
Confirm the transfer, then remove your access.

Reduce risk whoever owns it

Enable two-factor authentication on the registrar account.
Keep contact emails on the client's domain-independent addresses (not an address on the domain itself, which stops working if it expires).
Track the expiry date in your own system. See the domain renewal checklist.
Know the consequences of a lapse: what happens when a domain expires.

Two people reviewing a signed contract at a table

Write the ownership rule into the contract

Decide before the first invoice. Either the client is the registrant and the agency has a login, or the agency is the registrant and the contract says how the client gets the name if they leave. Silence is how disputes start.

Client-owned is the cleaner default. The client can fire you without losing their name, and you are not holding their business hostage. You still need a way to see the expiry. A delegated user, or a shared mailbox on the registrar notifications, is enough.

Agency-owned is reasonable when you bundle the domain into a care plan and the client does not want an account. Then the contract needs a handover clause: price, timeline, and what happens to DNS and email. Without that clause, "who should own the client domain name" becomes a negotiation during a breakup.

Never register the name in a personal freelancer account. When that person leaves, the domain leaves with them, and the agency finds out from a browser error.

Record the choice on the domain row. Ownership you cannot name is not a policy. It is a gap. Duvento keeps that field next to the date so the monthly review shows both.

The registrant name on the WHOIS record and the person who can click renew are often different. The legal owner can be the client while the only working login sits with a former developer. Track both. "Client owns it" is false comfort if nobody can authenticate.

Ask for the auth code and the lock status before a handover, not during one. Unlocking a name and waiting out a transfer lock has burned more agency breakups than the ownership clause itself.

Email ownership follows the domain. If you hold the name, you can hold their mail. Say that out loud in the contract conversation. Clients agree to client-owned domains quickly once they understand mail, not just the website.

For agency-owned names, bill the renewal as a line item even if you do not mark it up. A domain that is "included" gets forgotten, because nothing in the accounts asks for it. A line item gets a date.

Review ownership when the client rebrands or changes legal entity. The registrant organisation field goes stale, and a future dispute will quote it.

On the kickoff call, say the rule in one sentence and put it in the proposal: the client is the registrant, the agency has a user that can renew. If they want the opposite, the handover clause is a required paragraph, not a footnote. Who should own the client domain name is a sales question, not an emergency question.

FAQ

Should an agency register domains in its own name?

Usually not for client brands. Make the client the registrant and keep delegated access.

Can an agency refuse to transfer a domain?

If the agency is the registrant and refuses, the client may have to take legal or registrar-dispute steps. This is exactly what a good contract prevents.