Should an agency or the client own the domain?

The most common professional model is "client owns, agency monitors" — the domain stays registered under the client's account and contact details, but the agency tracks the expiry date and sends proactive renewal reminders. This avoids the awkward, sometimes contentious transfer required when an agency-owned domain needs to move to the client at the end of a relationship.

What happens to a domain if an agency-client relationship ends?

If the client owns the domain, nothing changes technically — the agency simply stops monitoring it and should formally hand off renewal responsibility in writing. If the agency owns the domain, it must be unlocked and an authorization (EPP) code issued to the client's new registrar within a reasonable timeframe, typically specified in the service agreement.

How many domains can one person realistically track manually?

Most people can reliably track two or three domains from memory or a spreadsheet. Past that, tracked renewal dates start slipping. An agency with 20+ client domains across multiple registrars needs a centralized dashboard with automated reminders — manual tracking at that scale is a matter of when, not if, something gets missed.

Who pays for domain renewal when the agency manages it?

This should be explicit in the client contract, not assumed. Common models are: the client pays the registrar directly (agency just monitors), the agency pays and invoices it as a pass-through line item, or renewal is bundled into a retainer. Whichever model you use, put it in writing before the first renewal comes due.

Agency team reviewing client domain portfolio on multiple screens

Freelancers

The Complete Guide to Domain Management for Agencies and Freelancers

Domain 360 Team

·May 13, 2026·8 min read

When a client domain expires on your watch, you do not just have a technical problem — you have a relationship problem. The client's website goes down, their email stops working, and they call you first. The fact that the renewal was technically their responsibility matters very little in that moment.

Quick answer: Agencies and freelancers manage client domains across dozens of registrars. One missed renewal can damage a client relationship irreparably. Here is the system that prevents it.

This is the unique challenge of agency and freelance domain management: the operational responsibility often falls on you even when the legal and financial responsibility belongs to the client. Getting this right is not optional — it is a core professional competency.

The Scale Problem

A typical web design agency with 30 active clients might manage 50 to 100 domains. Each client registered their domains at a different registrar — the one their previous developer used, the one that had a promotion when they launched, or the one their nephew recommended. As the agency grows, the portfolio grows, and the complexity compounds.

Managing this through memory, spreadsheets, or calendar reminders is a system that will eventually fail. The failure always comes at the worst possible moment — a Friday afternoon, a holiday weekend, or during a busy project launch.

The Three Models of Agency Domain Responsibility

Client owns, client manages: The domain is registered under the client's account. You have no access and no responsibility. The risk is that the client forgets to renew and you get the call when the site goes down.

Agency owns, client pays: The domain is registered under the agency account and invoiced to the client annually. You have full control. The risk is that you need to transfer the domain if the relationship ends — which requires cooperation at a potentially tense moment.

Client owns, agency monitors: The domain is registered under the client's account, but the agency tracks expiry dates and sends proactive renewal reminders. This is the most common professional model. It gives the client ownership while ensuring the agency provides continuity of service.

Domain 360 is designed for the third model. Add every client domain to your dashboard without needing access to the client's registrar account. The domain is publicly visible in WHOIS records, and Domain 360 pulls the expiry date from there automatically.

Building Your Client Domain Tracking System

Start with a complete audit of every client domain in your portfolio. Add every domain to Domain 360 with the client name in the notes. For an agency onboarding dozens of domains at once, adding them one by one is unnecessary — our CSV import guide covers the exact column format for bulk-adding an entire portfolio in one upload instead. The dashboard sorts by days until expiry so the most urgent domains are always visible at the top.

Set up email reminders to go to your agency's shared operations email — not any individual's personal inbox, which may not be monitored when they are on leave.

For domains the client controls, send a renewal reminder email 45 to 60 days before expiry. Document the outcome of every renewal conversation. This documentation protects you if a domain lapses through client inaction after you provided timely notice.

Protecting Yourself Legally

Include domain management clauses in your client agreements. Specify whether domain management is included in your retainer or billed separately, who is responsible for renewal costs, and what your notification obligations are.

Domain 360's Agency plan at $15.99 per month covers unlimited domains. For an agency with 100 client domains, that is less than 16 cents per domain per month — far less than the cost of recovering a single lapsed client domain.

Handling the Transition When a Client Relationship Ends

Offboarding is where agency domain management most often breaks down, because it happens under time pressure and sometimes friction. Build a standard offboarding checklist you run every time, regardless of why the relationship is ending: confirm who currently holds registrar access, unlock the domain and request the authorization code if the agency is the registrant, verify the client's contact email on file is current (transfer approval notices go there), and set a hard date by which the handoff completes.

Put a specific clause in every client contract covering this scenario before you need it — not during a dispute. Specify a maximum number of business days to release an authorization code after a written request, and note that domain ownership records (WHOIS registrant data) are the deciding factor in ownership disputes, not who happens to have dashboard access. Agencies that skip this step sometimes find themselves holding a client's domain hostage unintentionally, simply because no one defined the handoff process in advance — which is a fast way to turn a professional disagreement into a legal one.

Frequently Asked Questions

Never lose a domain again

Track every domain you own in one dashboard. Free for up to 15 domains.