An outbound agency should send a client's cold email from a separate domain that is registered in the client's own name, and should get DNS access through the registrar's or DNS host's own invite feature, never a shared password. With that access you add three kinds of record: SPF, DKIM and DMARC. Never send cold email from the client's main domain. A spam complaint there lands on the same domain that sends their invoices, quotes and newsletters.

This page is for the agency side: who owns what, what to ask the client's IT contact for, which records you add, one limit on SPF that breaks setups quietly, and what happens to the domain when the contract ends.

Who owns what

Item Registered to Why
Client's main domainClient (already)Keep cold sending away from it
Separate sending domainClient, with the agency invited as a userThe reputation is the client's; if you leave, it stays with them
Mailboxes on that domainClient's mail accountReplies belong to the client's pipeline
DNS records you addOn the client's DNS hostYou can remove your records and leave

The agency registering the domain in its own name feels convenient on day one and becomes a hostage situation when the client wants to leave. Put ownership in the contract in one sentence: the sending domain and its mailboxes belong to the client.

Why a separate domain at all

Google's email sender guidelines, read November 15, 2026, tell all senders to "Keep spam rates reported in Postmaster Tools below 0.3%." Three in a thousand is not many. A campaign to 5,000 Gmail recipients gets 15 reports at that line. If those reports land on the client's main domain, the damage reaches the mail their own staff send to customers. On a separate lookalike domain, the worst case is that the cold domain is retired and the main one is untouched. The same guide also says to avoid impersonating other domains, so the lookalike should be plainly the client's brand (for example a short word added to the name), registered by them.

A new domain and new inboxes start slowly. Plan for volume to ramp over weeks, and do not promise the client a send date or any result. Deliverability depends on the list, the message and the inbox history, and nobody controls it.

The access request

Ask for the smallest access that lets you do the work. Some registrars and DNS hosts let you invite another person to an account with limited rights. Look in the account menu for users, members, team or delegate access. The names change, and I have not listed a registrar here because the menus change. Never ask for the client's login, and never accept one: when you leave, you cannot show that you did not use it.

Here is a message you can send to the client's IT contact. It is not a cold email, so it needs no address line.

Hi {{first_name}},

To set up outbound email for you, we need to add a few DNS records to a new sending domain, not your main one. Could you register the domain (a version of your brand name, for example the name plus a short word) in your company's account, then invite us as a user with permission to edit DNS only? If your host does not support invites, you can add the records yourself from a sheet we send. You keep ownership of the domain and can remove our access any time.

The three records

For a domain using Google Workspace mailboxes, the records look like this. Your mail provider shows the exact values; these are examples of the shape.

Record Type and name Example value
SPFTXT at the root of the domainv=spf1 include:_spf.google.com ~all
DKIMTXT at a selector name, such as google._domainkeyA long key your mail admin console generates
DMARCTXT at _dmarcv=DMARC1; p=none; rua=mailto:reports@example-client.example

Google's guidelines say senders to Gmail need SPF or DKIM, and that bulk senders, defined as more than 5,000 messages a day to Gmail addresses, need SPF and DKIM and a DMARC record, whose policy "can be set to none." They also say that for those bulk senders the domain in the From header must align with the SPF domain or the DKIM domain. One client's cold campaign may sit well below 5,000 a day, but set all three up from the start so you never find out at volume. The record walk-through is in SPF, DKIM and DMARC for cold email, and failures show up as in DMARC fail.

The SPF limit that breaks setups

RFC 7208, section 4.6.4, read November 15, 2026, says an SPF check "MUST limit the total number of" DNS-querying terms to 10, and that if the limit is exceeded the check must return "permerror." The terms that count include include, a, mx, ptr and exists, and the redirect modifier. In practice: each tool you authorize to send for a domain adds an include, and each include may add more behind it. A client who already authorizes a newsletter tool, a CRM, a helpdesk and a billing system can be at the limit before you add anything. The fix is another reason to use a separate domain: it starts with a clean record and only the mail provider you are using.

When the contract ends

  • Remove your records and your user from the DNS host, and confirm the client sees it.
  • Hand over the mailbox list and the reply history, since the pipeline is theirs.
  • Leave the DMARC reporting address pointed somewhere the client controls.
  • Agree in the contract that neither side sends on the domain after the end date without the other's written consent.

More on the full sending setup, including warm-up and volume, is in cold email infrastructure.

Where Rocketship fits

A team running outreach for several businesses can read what each plan includes on pricing: Frontier covers up to 3 businesses and up to 3 inboxes in total at $79 a month, and Mission Control, built for teams running outreach at volume, covers up to 10 businesses and up to 50 inboxes in total at $1,499 a month. Rocketship emails from the Gmail inboxes you connect, and when an inbox is connected it checks that domain's SPF, DKIM and DMARC and says which one is missing. It does not set up a client's DNS for you, and each plan starts with a 7-day trial and requires a card.