Should I Let My Agency Own My Domain?

No. Your domain should live in a registrar account your business controls, full stop. The agency gets delegated access to do its job — DNS edits, site launches — without the power to hold your name. As a practical matter, whoever controls the registrar account controls the domain, and "the agency handles all that" means you've outsourced ownership of the one asset everything else hangs from.

This arrangement almost never starts as a power grab. It starts as launch-week convenience: the agency is building the site anyway, they register the domain in their master account, everyone's happy, and the invoice says "domain registration — $20." Five years later the relationship sours, and you discover the practical difference between paying for a domain and controlling one.

What can actually go wrong?

• The breakup scenario. You leave the agency; the routine handover request now sits in the queue of a company you just fired. Even without malice, you're waiting on their timeline. With friction — a disputed final invoice, hurt feelings — your domain becomes leverage in a negotiation you didn't know you'd entered.
• The disappearance scenario. Agencies fold, get acquired, or lose the one person who knew the logins. Your domain is now an asset inside someone else's abandoned account, and recovering it means proving ownership to a registrar's support desk — slow at best.
• The neglect scenario. The most common by far. The renewal card on their account fails, notices go to their inbox, and your domain lapses without a single email reaching you. The expiry lifecycle that follows is covered in how to secure a domain — none of it is fun.
• The invisibility problem. Even when nothing breaks, you can't audit what you can't see: no view of expiry dates, lock status, or who else has access. Every security switch is set by someone else, or not set at all.

Isn't this just how it's done?

It's how it's often done, which is different. The web is full of businesses whose most critical digital asset — the name on the sign, the address on every business card, the domain their email lives on — sits in a vendor's account as a convenience from 2019. Common practice built on nobody-thought-about-it is exactly the kind of default an architect audits. You'd never let your web vendor hold the deed to your office because they built the reception desk.

What's the right structure instead?

Separate ownership from operation. The layers make this clean — the full map is in registrar vs DNS vs hosting:

Modern providers make delegation genuinely easy — Cloudflare accounts support adding members with scoped permissions, so "but the agency needs access" stopped being an argument for agency ownership years ago. A good agency won't resist this structure. Most will be relieved: holding client domains is liability for them too.

How do you take a domain back gracefully?

1. Check reality first. WHOIS your domain; better, apply the operational test — can you log into an account that lists it? Do this for every domain, and log the answers in the inventory sheet from the consolidation playbook.
2. Make the ask while relations are good. "We're consolidating all company domains into our own registrar account as a policy matter — can you unlock and send the auth code?" No accusation; it's an audit, not a divorce. Any competent agency has done this dance dozens of times.
3. Run the transfer into your account. DNS-first if the records also live with them — the sequence is in how to transfer a domain without downtime. Nothing goes offline; the agency's day-to-day work doesn't change.
4. Grant delegated access back. The agency keeps doing its job. The deed stays in your name.

If step 2 meets resistance — delays, "our policy," a fee to release your own name — you've learned something important about the relationship, and the written record you've started will matter. Documented ownership (contracts, invoices) plus registrar dispute processes resolve most standoffs, but the honest lesson is upstream: the time to fix agency-owned domains is before you need to.

FAQ

How do I find out who actually owns my domain?

Run a WHOIS lookup on your domain. If privacy masking hides the details, the operational test is simpler: can you, right now, log into a registrar account that lists the domain? If the answer is no — if you'd have to ask someone — you don't control it.

What if my agency refuses to transfer my domain to me?

Escalate in writing, reference your contract and invoices showing you paid for the registration, and be aware that ICANN has a transfer dispute process. In practice, a firm written request citing ownership documentation resolves most cases. A flat refusal is a five-alarm signal about the whole relationship.

Can my agency still manage the website if I own the domain?

Yes — that's the correct architecture. You hold the registrar account; the agency gets delegated or DNS-level access to do its job. Modern providers support member access with scoped permissions, so the agency can edit records without the power to transfer or hold the name.

Is it normal for agencies to register domains for clients?

It's common, usually as launch-week convenience rather than malice. Common isn't the same as acceptable: the practice concentrates your most critical digital asset in an account you can't see, tied to a relationship that won't last forever. Register in your own account and delegate access instead.