Ownership and Control
The free domain is easy; deciding whose name it goes in is not
The registration is the cheapest part of the arrangement and the only part that cannot be rebuilt from a backup, which is why it is the part to get right first.
Straight answer first
Take the included registration — the first year is covered on annual hosting plans and it renews at ordinary list price afterwards — but register it in the client's name from the outset, because a domain is the one asset in this arrangement that cannot be restored from a backup.
Below: why the registrant field matters more than the DNS, how to keep operational control without holding the name hostage, what actually happens at the renewal you forgot, and the transfer mechanics that decide whether a departing client leaves quietly.
Written by the Hosting Seller staff · Checked 4 August 2026
99.9%
Target on the hosting behind it
24/7
Cover for DNS emergencies
Free
SSL once the name points here
NVMe
Disks under the site it serves
Bundled-domain savings are a first-year story. Across five years the quality of the hosting dwarfs the one-off saving, which makes the interesting question for a reseller not whether the domain is free but who ends up holding it and what that does to the relationship.
The mechanics here are straightforward and worth stating plainly: order an annual hosting plan and the first year of the domain registration is included, after which it renews at our ordinary list price — the same figure anyone would pay buying it separately. There is no inflated bundle renewal, and there is no condition tying the name to staying with us.
The registrant field is the whole argument
Everything else in a hosting relationship can be rebuilt. Files come out of a backup, mailboxes come out of an IMAP copy, a certificate reissues itself. A domain registration is the exception: it is a record at a registry, it has exactly one registrant, and if that registrant is your agency then the client does not own the address their entire business answers to.
Agencies do this for understandable reasons — it is quicker at signup, it keeps the renewal in one place, and it feels like it protects the relationship. What it actually does is make you the bottleneck for every DNS change and make an ordinary parting into a dispute, at exactly the moment when goodwill has run out.
So register in the client's name, with the client's own contact details, even when you place and pay for the order. Domains remain registered in the client's name for the term paid, and can move to any registrar once the registry's usual 60-day lock has passed. Say that to the client at signup and you have removed the single most common source of suspicion in this trade.
Control without a hostage
Ownership and operational control are separable, and the split most agencies want is: the client is the registrant, you manage the DNS zone. That gives you the ability to change records at speed — which is where the actual day-to-day work is — without giving you a veto over the client's ownership of their own name.
Practically, that means the name points at nameservers you control, whether your private nameservers under your own brand or the ones attached to the hosting. Records for mail, verification, third-party tools and subdomains all live in one zone you can edit, so a client asking for a text record for their marketing platform is a two-minute job rather than a support conversation with a registrar.
Document what is in the zone. A client who moves away, or who brings in another supplier for one system, will need to know what the records are and why. A one-page note per client — what the A record points at, where the MX records go, which verification records exist and who asked for them — turns a fiddly handover into a copy and paste.
The renewal nobody diarised
Domain renewals are the most damaging small failure a reseller can have, because the consequences are disproportionate and public. A lapsed hosting account is restored from a backup; a lapsed domain goes through registry expiry stages and can end up costing a redemption fee to recover, if it can be recovered at all.
So the renewal belongs in a system rather than in a memory. Somewhere past ten clients, the cost of manual billing shows up as missed renewals rather than as hours — a WHMCS licence is resold here at $6.99/mo and the reseller plans are ready to wire into WHMCS billing. Before that, a calendar with a reminder ninety days out will do, and it is better than nothing by an enormous margin.
Be clear with the client about who is responsible. If you renew on their behalf and bill them, say so and confirm the payment method is current every year. If they renew it themselves, tell them the date in writing. The failure mode here is always the same: both parties assumed the other was watching.
The transfer that decides how you are spoken about
A client leaves and wants their domain. If you did the registration properly, this is a formality: unlock the name, supply the auth code, and their new provider completes the transfer with whatever registration time remains coming across with it. DNS keeps answering throughout, so nothing goes dark.
Two mechanical details prevent the two common complaints. First, the registry's usual 60-day lock after a registration or a previous transfer — tell a client about it before they need to know, because being told during a departure sounds like an excuse. Second, the DNS: if you have been running the zone, the records need recreating wherever they are going next, and that is where a departing client's email gets stranded if nobody thinks about it.
Hand over the zone documentation with the auth code. It costs you nothing, it prevents the client's email breaking in a way they will attribute to you, and in a small industry the reseller who makes a clean exit easy is the one who gets referred by the client who left.
Included, but not conditional
The first year of the domain comes with an annual hosting order and renews at ordinary list price afterwards. There is no inflated bundle renewal, and the name is not held to the hosting — which is precisely what makes it safe to pass on to a client.
Free SSL is issued as soon as the name points at the account and reissues before it lapses, so the certificate never becomes a second thing to diarise alongside the registration.
- Registered in the client's name from the start
- Ordinary list price at renewal, no bundle premium
- Transfer out once the usual 60-day lock has passed
- DNS control kept separately from ownership
Why Hosting Seller
On every plan, as standard
No bundle-renewal premium
The included first year renews at ordinary list price — the same figure anyone would pay buying the name on its own.
Ownership you can pass to the client
Registration in the client's name is what turns a domain from a point of friction into a straightforward part of the service.
DNS control without the hostage
Run the zone for speed of work while the registrant remains the client, which is the split that suits both sides.
Certificates that follow the name
Free SSL is issued once the domain points at the account and reissues itself, so it never becomes a separate renewal to track.
A transfer that is a formality
Unlock, supply the auth code, and the remaining registration time comes across — with DNS answering the whole way.
Billing that can take the renewals over
The reseller plans wire into WHMCS when manual tracking stops being safe; the licence is resold here at $6.99/mo.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Set the registrant to the client at order time
Their name, their contact details, even when you place and pay for it — this is the decision the whole relationship rests on.
- 2
Keep the zone, not the name
Point the domain at nameservers you control so day-to-day record changes are fast, while ownership stays where it belongs.
- 3
Document the zone per client
One page naming the A record, the MX records, the verification records and who asked for each one.
- 4
Put every renewal in a system
A reminder ninety days out at minimum, and automated billing once you are past ten clients — this failure is disproportionate to its cause.
In the Box
Packed with every plan
- Every client domain registered in the client's own name
- Client contact details current on the registration
- A written note of who is responsible for the renewal
- A renewal reminder at least ninety days out
- DNS zone documented per client, one page each
- Nameservers under your own brand where you run the zone
- The 60-day transfer lock explained to the client in advance
- Auth code procedure known before anybody asks for it
- Free SSL confirmed issuing once the name points here
- Zone documentation included in your handover pack
Across the Counter
Things people ask us all the time
Should I register client domains in my own name to protect the relationship?
No. It protects nothing and creates two problems: you become the bottleneck for every record change, and an ordinary parting turns into a dispute over an asset the client believes is theirs. Register in their name, keep operational control of the DNS zone if that suits your workflow, and you get the speed without the argument. Clients who discover afterwards that their domain was never theirs do not stay quiet about it.
What does the included domain actually cost after the first year?
It renews at our ordinary list price, which is the same figure anyone would pay registering the name on its own. There is no inflated bundle renewal and no penalty for moving it elsewhere. That matters to a reseller more than to an end user, because you are the one who will have to explain the year-two invoice to somebody who was told the domain was free.
A client is leaving and their email must not break. What is the order of operations?
Document the zone first, then transfer. Give the new provider the full record set — particularly the MX records and any verification entries — so they can recreate it before the nameservers change. Unlock the name and supply the auth code once that is confirmed. The classic failure is transferring the registration while the mail records exist only in a zone that is about to stop being authoritative.
Why can I not transfer a domain immediately after registering it?
A registry lock of around 60 days applies after a new registration or a previous transfer. It is a registry rule rather than a supplier policy, and nothing anyone can waive. Tell clients about it at signup rather than at departure, because the same fact sounds like a technical constraint in month one and like an excuse in month twelve.
How do I stop myself missing a client domain renewal?
Take it out of your memory and put it in a system. Below about ten clients a calendar with a ninety-day reminder is adequate. Above that, automated billing pays for itself in avoided incidents — the reseller plans are ready to wire into WHMCS and a licence is resold here at $6.99/mo. A lapsed domain is the one failure in this trade whose consequences are entirely disproportionate to its cause.
Read next
WooCommerce Hosting for Growing Stores
The trading client whose growth arrives as sustained load, and the point at which containment stops being enough.
cPanel vs Plesk
The panel decision from a reseller's side: what your clients see and what your staff have to support.
Web Hosting
cPanel accounts on NVMe with SSL, migration and year-one domain — the shelf most client packages are modelled on.
AI Website Builder
Describe the site and the builder drafts it on real hosting — the low-touch option for a client with no build budget.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Get the ownership right first.
Year-one registration included with annual hosting, renewing at ordinary list price — registered in whichever name you tell us to use.
See Web Hosting plans