# White label hosting control panel: the complete branding checklist

> Build a white label hosting control panel - panel name, panel domain, nameservers, mail, welcome emails, billing SSO - with a fair look at cPanel, Plesk and DirectAdmin.

Source: https://zopanel.net/blog/white-label-hosting-panel  
Updated: 2026-10-21

## Key takeaways

- A white label hosting control panel shows customers your brand, not the software vendor's.
- Renaming the panel is only part of it; the panel address, nameservers, mail hostname and customer emails should carry your brand too.
- cPanel, Plesk and DirectAdmin all offer logo customization; ZoPanel replaces the panel name server-wide.
- Single sign-on from your billing system means customers rarely need to see the panel's address at all.

A white label hosting control panel is one where your customers log in and see only your company: your panel name, an address like `panel.yourhost.com`, nameservers like `ns1.yourhost.com`, and welcome emails signed by you. They never need to know whether cPanel, Plesk, DirectAdmin or ZoPanel runs underneath. Most mainstream panels let you change a logo or a name; the real differences are **how far** the customization goes and **which licence tier** you need for it.

This article gives you a complete checklist of everything that should carry your brand (much of it outside the panel's interface), compares what popular panels let you customize, and walks through the setup in ZoPanel, including what ZoPanel doesn't do yet.

## What does white label mean in hosting?

In the hosting industry, white label usually means one of three things:

1. **White-label reseller hosting:** you rent resources from a large provider and resell them under your own name. Customers never see the upstream provider.
2. **A white-label panel:** you run your own servers with a control panel you can rebrand.
3. **A fully white-labelled stack:** billing, panel, email, nameservers and support all carry your name.

This article focuses on the second and third. The goal isn't to hide the software (a technical customer can usually tell) but to deliver a **consistent experience**: customers buy on your website, receive your emails, log in at your domain and contact your support. That consistency builds trust and makes customers less likely to drift to another provider.

## Checklist: where should your brand appear?

Changing the logo in the panel is only the most visible part. A customer meets the vendor's name in many other places:

| Touchpoint | Should be | Why it matters |
|---|---|---|
| Panel name and logo | Your company name | Customers see it every time they log in |
| Panel address | `panel.yourhost.com` with a valid certificate | `https://IP:8888` with a certificate warning looks amateur and trains customers to click through security warnings |
| Nameservers | `ns1.yourhost.com`, `ns2.yourhost.com` | Visible in WHOIS and DNS lookups for every customer domain |
| Mail hostname, webmail | `mail.yourhost.com` | Customers type it into their phones and Outlook |
| IP reverse DNS (PTR) | Your hostname | Shows up in email headers and affects inbox placement |
| Welcome and notification emails | Your wording and signature | The first email a customer receives after buying |
| Login from billing | A "Log in to panel" button in the client area | Customers rarely need to remember the panel address |
| Support link | Your ticket desk or chat | Customers with a problem look for you, not the vendor |
| Suspension and default pages | Your contact details | Seen by customers and their visitors |

If you're just starting a hosting business, set up your own nameservers from day one; moving hundreds of domains to new nameservers later is painful. Our guide to [private nameservers](/blog/private-nameservers) covers it in detail.

## How popular panels compare on white labelling

The information below comes from each vendor's official documentation at the time of writing (October 2026). Features and licence tiers change, so confirm with the vendor.

| Panel | What you can customize | Where |
|---|---|---|
| cPanel & WHM | Logos (SVG, light and dark backgrounds), main menu colour, favicon (ICO), Documentation and Help links, public company name and contact URL | WHM → Customization ([cPanel docs](https://docs.cpanel.net/whm/cpanel/customization/)) |
| Plesk Obsidian | Page title, logo (GIF/JPEG/PNG) with a link, favicon | Tools & Settings → Branding ([Plesk docs](https://docs.plesk.com/en-US/obsidian/administrator-guide/customizing-the-plesk-interface/appearance-and-branding/branding-and-themes.59452/)) |
| DirectAdmin | Logos, colours, custom CSS and the login page, for the Evolution skin | Admin Tools → Customize Evolution Skin ([DirectAdmin docs](https://docs.directadmin.com/directadmin/skins-and-templates/evolution.html)) |
| ZoPanel | Panel name (up to 40 characters) in place of "ZoPanel" in the panel and notifications, server-wide | Settings → General → Panel name (white-label) |

To read this table fairly: cPanel and DirectAdmin offer deeper visual customization than ZoPanel does today (logos, colours, CSS). ZoPanel's strength is the rest of the checklist: a panel domain with SSL, nameservers, mail, welcome emails with placeholders, support links, customer announcements and billing SSO are all built in, no plugins required. If you need **a different brand per reseller** on the same server, note that ZoPanel's white-label setting is server-wide: every reseller and customer sees the same name.

Licence costs differ a lot between panels, especially as account counts grow; our [cPanel alternatives comparison](/blog/cpanel-alternatives-2026) lists prices at the time of writing.

## Building a white label hosting control panel with ZoPanel

These steps follow the [panel settings](/docs/panel-settings) and [resellers](/docs/reseller) documentation.

### Step 1: Put the panel on your domain

1. Create an A record for `panel.yourhost.com` pointing at the server's IP.
2. In **Settings → General**, fill in **Administrator email** and save (Let's Encrypt needs it).
3. Enter the domain in **Panel domain** and click **Issue certificate**.

The panel is now at `https://panel.yourhost.com:8888` with a trusted certificate that renews automatically. The mail server and webmail use the same certificate once they're installed.

### Step 2: Rename the panel

In **Settings → General → Panel name (white-label)**, enter your brand (up to 40 characters). It replaces "ZoPanel" in the interface and in notifications. This feature requires a Business licence, which isn't on the public pricing page, so contact us if you need it. If the licence lapses, the custom name stops being used, but websites keep running.

### Step 3: Your own nameservers

1. Pick names such as `ns1.yourhost.com` and `ns2.yourhost.com`.
2. At the registrar of `yourhost.com`, create glue (host) records pointing those names at the server's IP.
3. In ZoPanel, open **DNS**, enter the **Nameservers** and install the DNS server (PowerDNS).

See the [DNS documentation](/docs/dns) to run `ns2` on a second server for redundancy.

### Step 4: Mail hostname and PTR

In **Email**, set **Mail hostname** to something like `mail.yourhost.com` (it must resolve to the server). Ask your VPS provider to set the IP's PTR record to the same name. Without it, much of your customers' mail lands in spam, and the VPS provider's hostname shows up in every email header.

### Step 5: Welcome email and support channels

- **Welcome email:** edit it in **Settings → General** (administrators) or **My account → Welcome e-mail** (resellers). The placeholders `{{username}}`, `{{password}}`, `{{panel_url}}`, `{{sftp_host}}`, `{{nameservers}}` and `{{support}}` are filled in automatically.
- **Support link:** under **My account**, set where customers get help; they see **Contact support** in their menu.
- **Announcements:** **Accounts → Announcements** shows a banner in customers' panels (information, important, maintenance), optionally emailed too.

Each reseller sets their own welcome email and support link, so even with one panel name per server, each reseller's customers get that reseller's contact details.

### Step 6: Single sign-on from billing

With the WHMCS, Blesta, HostBill or Paymenter module (Pro licence, since it uses API tokens), customers click **Login to ZoPanel** in the client area and land straight in the panel. Buying, paying and logging in all happen through your portal. See the [WHMCS documentation](/docs/whmcs).

### Step 7: Test it as a customer

Create a test customer account and walk the whole journey: receive the welcome email, log in, create a website, add a mailbox, configure mail on a phone, open a support ticket. Note every place where a name other than yours appears.

## What white labelling doesn't change

- **You are first-line support.** Customers don't know the vendor, so every question comes to you. Prepare help articles under your own brand.
- **Licence terms still apply.** Rebranding the interface doesn't change your rights and obligations under the software licence. Read the terms before you sell.
- **Security is on you.** Require 2FA for administrators and resellers (**Settings → General → Require two-factor authentication**); one compromised reseller account damages your whole brand.

## Conclusion

A convincing white label hosting control panel is about more than a logo. Customers trust you when every touchpoint, from the first email to the nameservers and mail hostname, carries the same name. Work through the checklist, pick a panel whose customization depth matches what you need, and test it from the customer's side.

You can try most of the flow (panel domain, nameservers, mail, welcome emails) on ZoPanel's Free plan: 3 hosting accounts, 10 websites, 10 databases, no time limit. Reseller accounts and the billing API need Pro (see [pricing](/pricing)); white-label needs a Business licence, so contact us. Install it with `curl -fsSL https://get.zopanel.net | sudo bash`, and read our [reseller hosting guide](/blog/reseller-hosting-guide) for the business side.

## Frequently asked questions

### What is a white label hosting control panel?

A control panel that lets a hosting company replace the software's name, logo or address with its own brand, so customers only ever see that brand. How far you can go varies by panel, from just the name to logos, colours and custom CSS.

### Can I upload my own logo in ZoPanel?

According to the current documentation, ZoPanel's white-label setting replaces the panel name (up to 40 characters) in the interface and notifications, server-wide. Logo upload is not documented. Combined with your panel domain, nameservers, mail hostname and welcome emails, customers still see your brand at every main touchpoint.

### Can each reseller have their own brand?

In ZoPanel, the panel name applies to the whole server. Each reseller still sets their own welcome email and support link. If you need a different panel name per reseller, the practical answer is one server per brand.

### Do I need private nameservers for white labelling?

They're not required, but strongly recommended. Nameservers are public in WHOIS and DNS lookups for every customer domain, so `ns1.yourhost.com` shows you're the actual provider. Changing nameservers after you have many customers is far harder than starting with your own.

### Will customers know which panel software I use?

Technically minded customers can often tell from the interface, port or headers. White labelling isn't about perfect concealment; it's about a consistent experience under your brand.