Portfolio & Delegation
Reseller hosting for agencies — Reselling hosting means holding other people's names — do it deliberately
The day you resell hosting you become, in your client's mind, their registrar — and every renewal date they forget becomes yours.
The short answer
Resell on a WHM plan sized to your client list — Reseller 1 comfortably carries the first hundred accounts, all branded as yours — but decide first whose details go on each client's registration, because that record, not the hosting, is what a dispute will turn on.
The working sits below: private nameservers and what they conceal, one zone per client, and the renewal calendar that stops a client's name lapsing on your watch.
By the Hosting & Domains team · Reviewed 24 August 2026
24/7
Desk that answers
1-click
App installs
Free
SSL per account
Daily
Copies, all plans
Reselling changes an agency's arithmetic. A project worth one invoice becomes a subscriber worth a margin every month, and clients whose hosting you hold are famously reluctant to move.
It also changes your exposure. Hosting you can rebuild from a backup. A client's domain that lapsed because the renewal notice went to your inbox and you were on holiday is a conversation that ends a relationship, and occasionally a referral chain.
You are about to become somebody's registrar in their eyes
Clients do not distinguish between registry, registrar, reseller and host. They know who they pay, and that is you. Every question about a name — why it expired, who can move it, why mail stopped — arrives at your desk regardless of who is technically accredited.
So decide the policy before the third client, not the thirtieth. Either client domains sit in the client's own registrar account and you manage them by delegated access, or they sit in yours and you accept the duty that comes with that.
Both are defensible. What is not defensible is drifting into the second by accident, with no register of what you hold and no idea which renewals are yours.
Private nameservers, and what they actually conceal
Private nameservers are nameservers branded on your own domain, such as ns1.yourbrand.com, created with glue records at the registrar. Functionally identical to any other, cosmetically yours.
They are included with reseller hosting here, and they matter because a client who looks up their own delegation sees your brand rather than your supplier's. That is the single most common way an upstream supplier leaks to an end client.
What they do not conceal is everything else. Reverse lookups, mail headers, support signatures and the certificate chain will all tell a curious client something. White labelling is a discipline applied across the stack, not one setting.
One account per client, one zone per client
WHM above, one cPanel account beneath each client, so one customer's mess stops at that customer. The same logic applies to the zone: each client's records in their own zone, editable without going near anybody else's.
The tempting shortcut is stacking client sites as addon domains inside one account. It saves a few pounds a month and it means a single compromise or suspension takes your whole recurring revenue offline at once.
It also makes departures ugly. A properly separated cPanel account lifts out intact when a client leaves; an addon domain inside your own account has to be untangled, usually in a hurry, usually while somebody is annoyed.
Renewals are the part that breaks at scale
Forty accounts is manageable. Forty registration dates spread across a year, on a mixture of endings with different registry rules, is not — not from memory.
Keep one register: the name, the registrant, the registrar it sits at, the renewal date, where the zone is hosted, and who pays. Review it monthly. That one document is the whole difference between reselling as a business and reselling as a liability.
Then automate what you can. Auto-renew on everything, one card that does not expire mid-year, notices going to a shared mailbox rather than one person's, and a diary entry a fortnight before each date for names you have decided not to auto-renew.
The plan, and what the care line is worth. The Reseller 1 plan: WHM above, one cPanel account per client beneath, overselling permitted so you price on the value you add, per-account resource ceilings, and private nameservers on your own brand included.
Charge for the care rather than the disk. The £15 to £30 a month most agencies charge, with updates and minor fixes wrapped in, is entirely ordinary — and domain management, renewal watching and a documented handover are exactly the parts of that a client cannot do themselves.
Reseller hosting carries a seven-day refund window, and the hosting renews at the rate you ordered at. Domain registrations sit outside any refund, because the registry charges the instant a name is secured.
Your brand in front, ours nowhere
Private nameservers on your own domain, panels branded as yours, and no reason for a client to learn who your supplier is. We are content to be invisible; that is what white label means.
Hosted somewhere else already? We move the whole site at no charge, usually within 24 hours, and it goes on answering visitors throughout.
- Private nameservers with glue records at the registrar
- One cPanel account, and one zone, per client
- Accounts that lift out intact on departure
- Overselling permitted, ceilings applied per account
Why Hosting & Domains
Standard on every plan
Delegation that reads as yours
Private nameservers on your own brand, created with glue records at the registrar and included with reseller hosting.
Clean departures by design
One cPanel account per client means a leaver's account lifts out whole, with nothing to untangle from anybody else's.
Per-client zones
Each client's records in their own zone, so an MX change for one is never a risk to the other thirty-nine.
One rate, published in the open
What you order the hosting at is what you renew it at, which is the only way to price a care plan honestly.
An upgrade path that is real
Shared, reseller, VPS and dedicated on one platform — today's client list never boxes next year's in.
The trading name, and the company
Azaanex Inc., federally incorporated in Canada — diligence your own clients may reasonably ask you to have done.
Quick Start
Order placed to site online
- 1
Write the domain policy before client three
Client's registrar account or yours, and who is named as registrant. Decide it once, in writing, and apply it to everybody.
- 2
Set up private nameservers and use them everywhere
ns1 and ns2 on your own brand, glue records created at the registrar, every client delegated to them. Consistency is what keeps the supplier invisible.
- 3
Build the register, then review it monthly
Name, registrant, registrar, renewal date, zone location, payer. Forty accounts do not fit in anybody's head, and this is the document that stops one lapsing.
Built In
Fitted to every plan
- Private nameservers on your own brand, glue records included
- WHM above, one cPanel account per client beneath
- Overselling permitted, with resource ceilings per account
- A daily copy, with restores you run yourself from the panel
- Free SSL on every plan, reissued before the old one lapses
- Webmail in the browser plus IMAP, POP and SMTP for any client
- Softaculous included for one-click application installs
- Upgrades applied in place, with no migration when you change plan
- PHP versions set per site from the control panel
- Money back within 7 days on reseller, 30 on hosting plans
Frequently Asked
Questions we field again and again
Should client domains sit in my registrar account or the client's?
The client's, wherever they will tolerate it, with you given access to manage the records. It keeps the registrant record correct, keeps renewals their liability, and removes the awkward conversation on the day they leave. Holding names yourself is defensible, but only with a written register and an explicit agreement about who renews what.
What do private nameservers actually stop a client seeing?
The delegation. A lookup on their own name returns ns1.yourbrand.com rather than a supplier's hostnames. That is genuinely the most common leak, and worth closing. It does not hide mail headers, support signatures or reverse lookups, so treat white labelling as a checklist across the stack rather than one setting.
A client leaves. How do I hand the name over cleanly?
Confirm the registrant details are theirs, unlock the name, issue the auth code, and let their new registrar pull it. Remaining term carries over. Then tell them plainly that the registry usually locks a name for sixty days after a transfer, so they do not think you have obstructed them. Their cPanel account lifts out separately and intact.
How do I stop a client's name expiring on my watch?
One register, reviewed monthly, plus auto-renew on everything you hold and a card that does not expire mid-year. Send renewal notices to a shared mailbox rather than a person. For any name you have deliberately chosen not to auto-renew, put a diary entry a fortnight before the date — the grace period is not a plan.
Keep reading
Reseller Hosting
White-label WHM hosting with private nameservers on your own brand, and monthly billing behind.
DirectAdmin Reseller Hosting
A lighter DirectAdmin reseller tier, for client accounts that need separating rather than tuning.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
Your brand on the delegation.
Private nameservers included, one account and one zone per client, and a hosting renewal at the rate you ordered at.
View Reseller Hosting plans