The safest way for a web agency or freelancer to manage client domains is to have each client own their domain as the registrant, with the agency given delegated access to manage it, and to keep one central list of every client domain with its registrar, expiry date, auto-renew status, DNS, hosting and SSL details. Group that list by client, set alerts for domains and certificates, and send each client a short report so they know what they own and what is due.
Domains are where agency relationships most often go wrong: an expired domain takes a client's website and email down, and a domain registered in the agency's name causes disputes when the client leaves. Here is how to set things up so neither happens.
Get ownership right first
The registrant is the legal holder of a domain. Whoever is listed there controls it in a dispute, receives transfer approvals and can move it elsewhere. For client work, the options are:
| Setup | Pros | Risks |
|---|---|---|
| Client owns the registrar account, agency has delegated access | Clear ownership. Client keeps everything if you part ways. | Client must keep billing current, or you need to watch it for them. |
| Domain in the agency's reseller or registrar account, client listed as registrant | Easy for the agency to manage and bill. Ownership still with client. | Transfers out take some admin when the client leaves. |
| Domain in the agency's account with the agency as registrant | Simplest to set up. | The client does not legally own their own name. A common source of disputes. Best avoided. |
Whichever setup you choose, put it in writing in your contract: who owns the domain, who pays for renewals, and what happens to the domain if the relationship ends.
Build a central client domain register
For every client domain, record:
- Client name and the person who approves renewals
- Registrar and which account holds it (client's or agency's)
- Registrant name, so you can confirm the client is the owner
- Expiry date and auto-renew status
- Lock status
- Nameservers and where DNS is hosted
- Hosting provider and server IP address
- Email provider (from the MX records)
- SSL certificate expiry date
- Who pays: client directly, or agency rebills
Most of these come straight from public WHOIS, RDAP and DNS lookups. The rest, such as who pays and who approves, you add yourself. A domain tracking spreadsheet works for a handful of clients; beyond that, you want the public data to refresh itself.
Take control of renewals
Even when the client owns the domain, they will blame the agency when it expires. Protect both of you:
- Turn on auto-renew for every client domain, and confirm whose card it uses.
- Set your own alerts at 90, 30 and 7 days before each domain and each SSL certificate expires, independent of the registrar's reminders.
- Contact the client at 90 days if they pay directly, with a short note saying what is due and when.
- Check after renewal that the expiry date actually moved forward.
- Flag domains with auto-renew off and get a written decision from the client: renew or let it go.
Our guide to domain expiration alerts explains the intervals and how to make reminders reach the right person.
Watch DNS and SSL, not just expiry
Client sites break for reasons other than expiry, and the agency usually gets the call. Three checks catch most of them early:
- DNS and nameserver changes. Clients sometimes change DNS themselves, or another supplier does, without telling you. An unexpected MX or nameserver change is also a classic sign of a compromised account.
- SSL certificate expiry. With certificates now limited to 200 days and getting shorter, automated renewals that fail after a hosting or DNS change are a frequent cause of "the site says it is not secure" calls.
- Site up or down. A quick check that each client site still responds catches hosting problems before the client does.
See how to monitor DNS record changes for which records matter most.
Secure the accounts
- Use two-factor authentication on every registrar and DNS account, including the client's own.
- Keep registrar lock on for every domain that is not being transferred.
- Use delegated or team access rather than sharing the client's login when the registrar supports it.
- Store credentials in a password manager, never in the domain list or in email.
- Remove former staff from registrar accounts as part of your offboarding checklist.
Send clients a domain report
A short, branded report once or twice a year shows clients what they own and positions you as the one keeping it safe. Include:
- Each domain with its registrar and expiry date
- Auto-renew and lock status
- Hosting, nameservers and email provider
- SSL expiry for each site
- Anything that needs a decision, such as domains with auto-renew off
PDF works best for most clients. If a client is moving hosts or switching agencies, a DNS records report for their domains makes the handover much smoother.
Handling a client who leaves
When a client moves on, a clean handover protects your reputation:
- Confirm the client is the registrant for every domain.
- Provide a DNS records report so the new provider can rebuild anything they need.
- Unlock the domain and supply the transfer authorization code if they are moving registrars.
- Remove your access once the transfer is complete, and archive their entries in your domain list.
How Names Organizer helps agencies
Names Organizer, a domain manager for Windows, was designed with agency work in mind. You can tag each domain with its client, use separate portfolios, and keep registrar account names and notes alongside every domain. It fills in registrar, dates, nameservers and status automatically, warns you before domains and SSL certificates expire, and monitors DNS, nameservers, status changes and whether each site is responding.
The client report shows one client's domains, hosting and SSL with your logo, and can be saved as PDF or Word. Report layouts can be saved for next time, so producing a fresh report for every client each quarter takes seconds. Names Organizer keeps everything in a password-protectable file on your PC with no limit on the number of domains or clients.
Frequently asked questions
Should an agency register domains in its own name for clients?
It is safer for the client to be the registrant, with the agency given access to manage it. That avoids disputes and lost domains if the relationship ends.
How do I track which domains belong to which client?
Tag every domain with its client and keep the registrar account, renewal date, hosting and SSL details alongside it, so you can filter and report one client at a time.
What should a client domain report include?
The domain names, registrar, expiry dates, auto-renew status, nameservers, hosting and SSL expiry, so the client can see what they own and what is due.
