Quick answer
It depends entirely on what's written down, and most agencies never write it down anywhere public. Of five named agencies I checked directly, only two state a position on their own pages: LeadHaste says everything, domains, inboxes, and data, is registered in the client's name from day one. CIENCE's graph8 terms guarantee you keep contact data you paid for and exported, but say nothing about sending domains or mailboxes. Belkins and SalesHive say nothing either way on their own service pages. Ask for the clause in writing before you sign. Don't assume it either way.
The conflict I need to disclose
I'm Hlib Storchak. I build outbound systems for B2B founders and sales teams, and I've booked 2000+ meetings for B2B clients running that kind of engine myself. That makes me a competitor to every agency named in this article, not a neutral party. I've also been the person a client calls after they've already given notice to an agency and discovered, too late, that nobody had agreed in writing who keeps the sending domains.
What I can offer is an honest read, built only from what each company states about itself on its own public pages, plus direct quotes from their own terms where I could find them. I did not use pricing-aggregator or "we vetted 50 agencies" roundup sites as a source for any ownership claim, since several of those are themselves written by a competing agency and have an obvious incentive to make the subject look bad.
What "ownership" actually has to cover
"We own our data" is the kind of sentence that sounds reassuring and settles nothing. A cold email program actually has four separate assets, and a contract can grant you some without granting the others:
- The domains themselves. Who is the registrant on record, and is the registrar account in your name or theirs.
- The mailboxes and their sending reputation. You can own a domain and still lose the warmed-up sender reputation if the agency controlled the actual inbox provider account.
- The contact data and lists. The prospects you paid to find and the enrichment built on top of them.
- The sequences, copy, and campaign history. What was sent, to whom, and what worked, which matters if you want to keep running the same program rather than start from a blank page.
A clause that only says "you own your data" can quietly mean only the third item on that list. The 12-point vetting checklist I wrote earlier covers the pre-signing version of this question, whether domains are dedicated to you or shared across the agency's client base. This article is about the other half: what happens to all four assets specifically when the engagement ends, which is a different clause and one most buyers never ask about until they're already leaving.
The three ownership models I actually see
Contracts in this space tend to land in one of three shapes, whether or not they say so explicitly:
| Model | What happens on termination | Who it favors |
|---|---|---|
| Client-owned from day one | Domains, mailboxes, and data were always registered in your name. Nothing to transfer, you just stop paying the agency. | You, especially for a multi-year program |
| Agency-bought, client as registrant | The agency purchases and configures everything but lists you as the owner. A transfer is still needed but it's a formality, not a negotiation. | Roughly even, if the transfer process is actually documented |
| Agency-owned outright | The agency's name is on everything. You can ask for a handover, but nothing obligates them to agree, and warmed sender reputation often can't transfer even if the domain does. | The agency, by default, unless the contract says otherwise |
The third model isn't automatically a scam. A lot of retainer agencies run this way because it's simpler for them to manage infrastructure across every client from one pool, and plenty of clients never plan to leave anyway. The problem is only when a contract defaults to model three silently, and you find out which model you're in after you've already announced you're leaving.
Five agencies' own pages, compared
| Source | What it states about ownership | Where I checked |
|---|---|---|
| Danish Lead Co (sets the standard) | Its own buyer's guide recommends demanding explicit contract language for client ownership of domains, prospect data, and any custom infrastructure built during the engagement | Its own 2026 contract red-flags guide |
| LeadHaste | Explicit: domains, mailboxes, and data are "registered in your name from day one" | Its own cold email agency services page |
| CIENCE (graph8 platform terms) | Explicit, but partial: you may keep contact data you paid for and exported after termination. Sending domains and mailboxes aren't mentioned | graph8's own published Terms and Conditions |
| Belkins | No statement either way | Its own cold email services page |
| SalesHive | No statement either way | Its own email outreach services page |
A Clutch badge or an award logo on an agency's homepage tells you about reviews and client count, not about who's listed as the registrant on your sending domain. I've gone further into how much to actually weight those badges in Clutch Champions vs Global Award Winner, and the short version applies here too: neither is a substitute for reading the actual contract.
Danish Lead Co: writes the standard, claims to meet it
Danish Lead Co's own 2026 guide to red flags in outbound agency contracts names "ownership ambiguity over data, domains, and infrastructure" as its third red flag, and recommends buyers demand explicit language covering client ownership of all email domains and accounts, all prospect data generated, and clear transfer of any custom infrastructure built during the engagement. Its own pricing-models article makes the same point from a different angle: who owns the domains, mailboxes, and data once the contract ends is a question ownership should sit with the client on, regardless of which pricing model you're on.
Its own site states that it handles domains, inboxes, data, and copy on the client's behalf while the client keeps full ownership of that data and those tools. I want to flag the obvious caveat here, since it applies to every self-description in this article, including this one: that's Danish Lead Co's own claim about itself, not an independently audited fact. A company that writes the industry's buying guide has an incentive to also claim it clears its own bar. I couldn't find an independent source confirming it, which isn't the same as finding a reason to doubt it, just a reason not to treat it as settled.
LeadHaste: ownership as the actual pitch
LeadHaste's own cold email agency page goes further than most, making ownership the explicit differentiator rather than a footnote. Its language states that domains, inboxes, and data are registered in the client's name from day one, and its own comparison framing contrasts its infrastructure, described as "yours, engineered and registered in your name", directly against a shared-infrastructure model at unnamed competitors.
The real limitation here isn't the claim itself, it's that "registered in your name" is a marketing headline, not a contract clause. If this model genuinely matters to you, the practical step is still the same regardless of which agency you're evaluating: ask to see the actual registrar account access or the specific contract clause, not just the sales page, before you sign anything.
CIENCE's graph8: half an answer, in writing
CIENCE's own graph8 platform publishes its Terms and Conditions publicly, which already puts it ahead of most named agencies on transparency alone, whatever you think of the actual terms. Section 2.9 states that the customer may retain and perpetually use any B2B contact data or website visitor identification data that was identified and used for a specific campaign, for which fees were paid, and that was exported to the customer's own data warehouse as part of the service. Section 6.5 separately commits to deleting customer content within 60 days of a request.
What's missing is just as informative as what's there: nothing in those terms addresses sending domains, mailboxes, or sender reputation specifically. That's consistent with how I've described graph8's model in CIENCE vs Leadium, graph8 bundles data and intent as its real differentiator, and the published terms track that: strong, explicit language on the data layer, silence on the infrastructure layer.
Belkins and SalesHive: no public answer either way
I read Belkins' own cold email services page and SalesHive's own email outreach page directly, looking specifically for any language about what happens to domains, mailboxes, or data after the engagement ends. Neither page mentions it in either direction. Both pages describe the setup process in detail, domain configuration, SPF and DKIM and DMARC records, warmup schedules, but stop short of saying what happens to any of it on exit.
I want to be fair to both here, because silence on a public sales page genuinely isn't the same as a bad contract. Both are established agencies with real track records on the parts of the job their public pages do describe well. The honest conclusion from checking their public pages is simply that you cannot answer this question from the public page for either one. You have to ask, and get the answer in the master service agreement, not infer it from what isn't mentioned on the marketing site.
Note. I checked each agency's own public pages and published terms directly rather than relying on third-party "best cold email agencies" roundups, several of which are written by competing agencies with an incentive to make each other look worse on exactly this point.
Why silence isn't automatically a red flag
It's tempting to read "doesn't mention it" as "the answer is bad," but that's not a safe inference. A lot of standard contract terms live in the master service agreement a prospect only sees after an initial sales call, not on the public marketing page, and plenty of agencies that handle this fairly in the actual contract simply never thought to turn it into a selling point the way LeadHaste has. I've seen real red flags in agency contracts, and a quiet public page by itself isn't one of them. An actual red flag is a contract that explicitly states the agency retains ownership, or a sales rep who gets evasive when you ask the question directly in a call.
It's also worth being honest that for some engagements, this clause genuinely doesn't matter much. A three-month pilot to test whether outbound works for your offer at all isn't the moment you've built years of sender reputation worth protecting. The stakes rise with the length and maturity of the program, not on day one.
What starting over on new domains actually costs
If you don't own the domains and have to rebuild from zero, the cost isn't abstract, so here's the maths with every input labeled as an assumption you should swap for your own numbers.
Assume you run 5 sending domains with 3 inboxes each, 15 inboxes total, each capped around 30 to 40 emails a day once fully warmed, a volume range I've covered in more depth in how many cold emails per day per inbox. Assume a new domain needs roughly 3 to 4 weeks of warmup before it can carry that full volume, ramping up gradually rather than starting at the cap. Modelled simply, that's the equivalent of about 2 weeks of fully lost sending volume per domain, not 3 to 4 weeks of zero output.
Assume your program was producing 20 booked meetings a month at full volume. Two weeks of lost capacity, spread across a re-warming cohort of domains, costs you somewhere in the range of 8 to 10 of those meetings in the transition month, a delay rather than a permanent loss, assuming you don't also lose the list and sequence history along with the domains. Multiply that gap by your own average deal value and close rate to turn it into a pipeline number, since that part is specific to your business and not something a generic model should guess at for you.
That's the soft cost. The harder cost shows up if the agency also controlled the contact list, the sequence history, and the CRM records of who already replied, since none of that re-warms on a timer, it's simply gone. The full agency cost model I've written walks through the broader cost-per-meeting maths if you want to size the whole relationship, not just the exit cost.
What I check when I take over an account
This is the first thing I check when a client asks me to audit an outbound relationship they've inherited or are trying to exit cleanly: I pull the actual DNS records for the sending domains and check who the registrant is, rather than asking the agency and taking their word for it. The mistake I see most often isn't a bad contract clause, it's that nobody checked the registrant field until the week notice was already given, at which point there's no more leverage to negotiate a clean handover. If you're still mid-contract, that's the week to check it, not the week after you've announced you're leaving.
The clause to ask for before you sign
Whatever agency you're evaluating, ask for this in writing before you sign, not as a verbal assurance on the sales call: explicit client ownership of the sending domains and registrar access, explicit ownership of the mailbox and inbox-provider accounts, explicit ownership of all contact data and lists generated during the engagement, and a defined handover process with a timeline, not just a promise that "we'll work it out." If an agency won't put that in writing, that refusal is the actual answer to the ownership question, whatever the sales page says.
If outright ownership matters enough to you that you'd rather not negotiate for it at the end of a relationship, running your own infrastructure from the start is the other way to solve this. Salesforge for sending, with Mailforge and Infraforge handling the domains and mailboxes themselves, is what I default to for clients who want to own that layer outright rather than license it through someone else's pool, purely as a personal preference from running it both ways, not a verdict on any of the agencies above. Plenty of them do solid work on their own infrastructure too.
Key takeaways
- Ownership isn't one thing: domains, mailboxes and sender reputation, contact data, and sequence history can each be owned separately.
- Of five named sources checked directly, only LeadHaste and CIENCE's graph8 state an explicit ownership position on their own pages, and graph8's only covers contact data, not domains.
- Belkins and SalesHive say nothing either way on their public pages, which isn't proof of a bad contract, just proof you have to ask.
- Check the domain registrant field directly rather than taking an agency's word for it, and do it while you still have leverage, not after giving notice.
- If you don't own the infrastructure, rebuilding costs roughly 2 weeks of lost volume per re-warmed domain, which you can translate into your own pipeline number.
- Ask for the ownership clause in writing before you sign. A refusal to put it in writing is itself the answer.
Who this matters most for, and when I'd skip the fight
This matters most if you're signing a program meant to run a year or more, where the sender reputation you're building is itself a real asset, or if you've already been burned once by an agency that went quiet about infrastructure on the way out. In those cases, pushing for the written clause, or simply owning the infrastructure yourself from day one, is worth the friction it causes in the sales conversation.
I'd skip the fight on a short pilot explicitly meant to test whether outbound works for your offer at all. Three months in, you haven't built sender reputation worth protecting yet, and the bigger question is still whether to continue at all, not who keeps the domains if you don't.
FAQ
Who owns the domains if I cancel my outbound agency?
It depends entirely on the contract, and most agencies state nothing about it publicly. Of the five named sources I checked, LeadHaste explicitly states everything is registered in the client's name from day one. CIENCE's graph8 terms explicitly cover contact data you paid for and exported, but don't mention domains. Belkins and SalesHive say nothing either way on their own pages. Ask directly and get the answer in writing.
What should "ownership" cover in an agency contract, just the domains?
No. A full clause should cover four things separately: the sending domains and registrar access, the mailbox and inbox-provider accounts, the contact data and lists, and the sequence and campaign history. A contract can grant you one of these without granting the others.
Is it a red flag if an agency's site doesn't mention domain ownership at all?
Not automatically. Most standard contract terms live in the master service agreement, not the public sales page, and silence there isn't proof of a bad clause. A real red flag is a contract that explicitly states the agency retains ownership, or a sales rep who won't give you a straight answer when you ask directly.
How much does it cost if I have to rebuild on new domains?
Modelled simply: assume roughly 2 weeks of lost sending volume per domain during a 3 to 4 week warmup, applied against your current meetings-per-month rate to estimate the delay in pipeline. That's the soft cost. The harder cost is losing contact lists or reply history that don't re-warm on any timer, so check whether those transfer too, not just the domains.
Which named agencies explicitly guarantee client ownership?
LeadHaste states it for domains, mailboxes, and data together. CIENCE's graph8 terms guarantee it for contact data you paid for and exported, but not for domains or mailboxes. Danish Lead Co's own guide sets this as the standard to demand and its own site claims to meet it, though that's a self-description, not an independently audited one, same caveat that applies to any agency's claim about itself.