Confirm the feature exists on your installed service and the new domain is registered and under your control. Back up website and email data, record DNS and certificates, and review application URLs, mailbox addresses and external integrations.

1. Open Domains > Manage for the intended domain and inspect the available Rename Domain action.
2. Check that the proposed new name is different and does not already exist elsewhere on the server. Subdomains are not eligible for the same rename workflow.
3. Prepare authoritative DNS and any required external-provider changes. Do not assume cPanel can change records hosted by Cloudflare or your registrar.
4. Enter the new hostname, review the confirmation and complete the rename. Inspect the resulting domain, document root, mail accounts and DNS entries.
5. Update application base URLs and arrange HTTPS for the new name. Test mail clients, webhooks, cron jobs and redirects from the old address where those must continue.

The new hostname should serve the intended site with valid HTTPS and expected mail identities. Check that the old name has a deliberate redirect or retirement plan rather than an accidental broken link.

If the action is unavailable, ask support for the supported procedure for that version and account. Do not rename cPanel system directories manually. If the change disrupts a critical service, use your recorded settings and support guidance to reverse the configuration safely.

No. Registration ownership and renewal remain with the registrar. Renaming the hosting configuration does not purchase the new domain, cancel the old registration or update every third-party service that knows the old address.

• Understanding domains, aliases and subdomains in current cPanel
• Editing or deleting a DNS record in cPanel Zone Editor
• Retrying AutoSSL after fixing a certificate-validation problem
• Adding a domain alias that shares an existing cPanel website

• cPanel: Manage The Domain