how to manage client domains as an agency.

when a client's domain expires, the site goes dark, the email stops, and the phone call comes to you. it does not matter whose account it was in or whose card declined. you are the agency; domains are what agencies are assumed to be handling.

that asymmetry is the problem: the responsibility is yours in practice and frequently not in contract, while the control sits somewhere else. everything below closes that gap without taking on liability you do not want.

who should own the registration

the argument recurs on every engagement. each option, with its failure mode:

agency-owned. the domain sits in your registrar account, billed to your card, renewed by you. operationally the easiest — full control, no chasing anyone, nothing depending on a client remembering a password.

it is also the option that ends badly. when a relationship sours you hold an asset the client believes is theirs, and the optics are terrible even when your conduct is impeccable. if you disappear — illness, insolvency, a bus — the client has no route to their own domain that avoids lawyers.

client-owned, agency-managed. the registration sits in the client's account, in the client's name, on the client's card, and you have delegated access. the right default for most agencies, worth pushing for even when the client would rather you handled it.

the reasons are unglamorous. the asset sits where it legally belongs, so no ownership argument later. renewal is on the client's card, so your cashflow is not underwriting their infrastructure. and offboarding becomes a permissions change rather than a transfer negotiation.

practically: the client registers, then adds you through the registrar's delegated-access mechanism. registrant contact the client, technical contact you.

agency-owned as a deliberate service. legitimate, but only written down: say so in the contract, state what happens at termination, name the transfer process. the failure mode is not the arrangement, it is the arrangement existing by accident.

whichever model you pick, write down which one it is per client. the dangerous state is not agency-owned or client-owned. it is nobody being certain which.

the expiry calendar across accounts you don't control

the constraint that makes agency domain management different: you need visibility over domains that are not in your accounts. a client-owned domain does not appear in your dashboard, does not email you a renewal notice, and does not tell you when their card expires.

the way through is that registration data is public. expiry date, status codes, nameservers and the accredited registrar are published by the registry over RDAP, and reading them needs no credentials and no permission. you do not need access to a client's account to know their domain expires in eleven days.

the calendar is buildable regardless of ownership model. take every domain across every client, put the list through bulk WHOIS for real expiry dates rather than remembered ones, and monitor the lot from one place. owndle is built for that shape — one inventory across every registrar, alerts at 90, 30, 7 and 1 days, no requirement that you hold the account. the free tier covers ten domains; paid plans run from £9 to £99 a month.

the staging matters more for agencies than individuals. 90 days is a line in a scheduled call, without drama. 30 is an email to the client's finance contact. 7 is a phone call. 1 day is a problem you are personally handling on a weekend. that is the argument for renewal reminders over registrar notices, which go to whoever registered the domain — frequently a former employee's mailbox nobody reads.

two agency-specific failure patterns. a client-owned domain on a card belonging to a marketing manager who has since left, where the charge declines and nobody sees the notice. and a domain nobody has looked at since launch, because working things do not generate tickets. why auto-renew fails covers both.

know what happens when one lapses, because clients ask immediately. the grace period still allows a renewal at the ordinary price, usually with the site already dark; after it, recovery costs many times a renewal and is not self-service. the difference between a phone call and an invoice.

exportable reports, and why they justify your invoice

"domain management" is hardest to defend as a line item when it is working, because the visible output is nothing happening. an exportable report turns invisible diligence into something a client can read.

what belongs in it, per client: every domain, its registrar, expiry date, auto-renew state, renewal cost, and the market comparison. that last column changes the conversation. a client seeing their domains cost meaningfully more than the same registrations elsewhere gets a reason your oversight is worth paying for, with a concrete saving attached. that gap is renewal arbitrage; quote it against the live price tables so the numbers are current rather than remembered.

a quarterly export does something quieter too: it gives you a dated record of having flagged an expiry. when a domain lapses because a client ignored three warnings, the difference between an awkward conversation and a liability is a report with a date on it.

the offboarding problem

most agencies handle onboarding carefully and offboarding badly, and domains are where that costs most. a departing client whose domain is stuck in your account is a dispute; one whose domain quietly stops being monitored is a lapse in eight months with your fingerprints on it. the termination checklist:

• transfer or release, explicitly. if you hold the registration, move it to the client's account and get written confirmation it arrived. a recent transfer or registration triggers a 60-day lock at most registrars, so start early rather than the last day.
• remove your access, and say that you have. delegated access you forget to give up outlives the engagement, and becomes a security question in a year.
• hand over auth codes and account details in writing, not in a chat message somebody will delete.
• tell them what expires when. a final export of every domain with expiry date, renewal price and auto-renew state. thirty seconds of work, and the most useful thing a departing client gets.
• take them off your monitoring, deliberately. either remove the domains or agree in writing that you are still watching them. do not leave it ambiguous, because "I assumed you were still handling it" is how a domain dies.
• check the registrant contact. if it is still an address at your domain, the client stops receiving renewal notices when you decommission that mailbox.

the shape that works

client owns the registration; you have delegated access. every client domain, whoever holds it, sits in one monitoring view built from registry data rather than registrar emails. staged alerts land early enough to be a diary item. a quarterly report carries expiry dates and a cost comparison, justifying the line item and creating a paper trail. offboarding is a checklist rather than a memory.

none of it is difficult. it is just what nobody sets up until after the first lapse, which is an expensive way to buy a checklist. if the domains are spread across accounts you do not control, managing domains across multiple registrars covers building the inventory from nothing.