Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Alias runbook · Beginner · 5 min each

How to park an extra domain — Alias or Redirect: Two Routes, One Canonical Host

You hold four spare names and want them doing something useful without quietly publishing your entire site at four different addresses.

View WordPress Hosting plansBrowse more How-To Library

The short answer

Redirect, do not mirror. An alias makes your whole site reachable under a second hostname, which means two addresses serving identical content and a permanent reliance on canonical tags to sort it out. A single 301 gives you one authoritative address and one set of URLs in your logs.

The exception is a name you want to hold rather than use, where a small holding page is honest and cheap. Either way the spare name needs a certificate, because a visitor typing https:// at a name with no certificate meets a browser warning before your redirect ever runs.

By the HostingFast team · Reviewed 24 August 2026

Beginner

Skill floor

4

Stages start to end

Free

Support, every tier

Proven

Run on the live stack

You need cPanel access and the spare names delegated here. Five minutes per name, and it is entirely reversible.

cPanel calls these things aliases, addon domains and redirects, and they do three different jobs. Knowing which is which is most of the work on this page.

Alias, addon and redirect are three different things

An alias, which older panels call a parked domain, points a second hostname at the same document root as your main site. Same files, same database, two addresses. An addon domain creates a new document root and behaves as a separate website inside the same account.

A redirect creates no site at all: the name answers, returns a status code and a Location header, and sends the visitor somewhere else. For a spare name you have no intention of developing, that third option is almost always the right one, and it is the cheapest of the three to reason about later.

Why a mirror costs you and a 301 does not

With an alias left mirroring, every page on your site exists at two URLs. You now depend on canonical tags being correct on every template forever, your analytics splits across two hostnames, and any link somebody builds to the alias accrues to an address you did not want to be known by.

A 301 removes the ambiguity at the protocol level rather than papering over it with a hint. One address is authoritative, one set of paths appears in the access log, and there is nothing for a crawler to have to decide. It is also less work: one rule instead of a standing obligation.

Certificates on names nobody will ever read

This is the step people skip because it feels pointless. It is not: TLS is negotiated before HTTP exists, so a request to https://spare.example with no certificate for that name fails at the handshake and shows a security warning. The redirect you configured never gets a chance to run.

Let AutoSSL cover the alias once it resolves to the account, then confirm with openssl s_client -connect spare.example:443 -servername spare.example that the SAN list includes it. Do it for the www form as well, because people type both and only one of them is in your head.

Making a spare name earn something

The defensive registrations — the misspelling, the plural, the .co.uk beside the .com — earn their keep as one-hop redirects and nothing more. A name with a genuinely different purpose deserves an addon domain and its own document root, subject to your plan's website allowance.

Everything else should be reviewed at renewal rather than renewed by reflex. A domain you cannot describe a use for is a subscription, and the honest options are a holding page, a redirect, or letting it go.

Hunting down the right domain name before someone else takes it

Why the follow-through is quick here

Guides written against imaginary hosting go stale fast. These are written against the real thing: the same panel, the same installer, the same defaults sitting in your account when you log in.

NVMe storage sits behind a LiteSpeed cache on every tier including the smallest, so speed is the baseline rather than the upsell.

  • Alias, addon and redirect kept distinct
  • The duplication cost stated plainly
  • Certificates issued on names nobody reads
  • Engineers on support at any hour

Why HostingFast

Standard on every plan

Three tools, distinguished

Alias, addon domain and redirect do different jobs, and the page names which one suits a spare you never intend to develop.

The duplication cost stated

A mirroring alias publishes your whole site twice and makes canonical tags a permanent obligation, which the page says outright.

The TLS failure named early

A spare name without a certificate breaks before the redirect runs, so issuing one is a step rather than an optional extra.

4 steps, no padding

Four actions per name, each ending in something observable, including the www form people forget.

Renewal discipline included

The page tells you to review spare names at renewal instead of accumulating a shelf of subscriptions you cannot justify.

Engineers on call

If AutoSSL will not cover an alias, support answers at any hour with the actual reason rather than a retry suggestion.

Quick Start

From order to online

  1. 1

    Point the spare name at the platform

    Change its delegation or its A record so it resolves to this account, then confirm with dig A spare.example @1.1.1.1. Nothing else here can be configured until the name arrives, and this is the step with the TTL attached.

  2. 2

    Add it as an alias, then decide alias or redirect

    In cPanel, Domains and then Aliases attaches the name to the account. Stop there and make the real decision: leave it mirroring the main document root, or convert it to a redirect. For a defensive registration, choose the redirect.

  3. 3

    Set a single 301 to the canonical host

    Create the rule so the spare name targets your canonical URL in one hop rather than via the www form or the http version. Then verify with curl -sIL -o /dev/null -w '%{num_redirects}\n' https://spare.example/ and confirm it prints 1.

  4. 4

    Issue the certificate and test all four entrances

    Wait for AutoSSL, then check the SAN list with openssl s_client. Test http and https, with and without www, on the spare name. Any of the four that fails at the handshake is a visitor who sees a warning instead of your site.

Built In

Loaded onto every plan

  • NVMe storage on every tier, not only the expensive ones
  • LiteSpeed caching in the server, not bolted on by plugin
  • No setup fee on any plan, at any tier
  • Year one of the domain free when you order annually
  • Free migration: our engineers move the existing site
  • WordPress Toolkit, with updates applied for you
  • Daily backups with self-service restores from the panel
  • In-place account upgrades, with no migration to change plan
  • Mailboxes that run on your own domain name
  • 99.9% uptime as the target, monitored around the clock

Frequently Asked

What people ask us most often

Does leaving an alias mirroring actually harm anything?

It creates duplicate addresses for every page you have, and it makes correct canonical tags a permanent requirement rather than a nice-to-have. Practically, your analytics splits, your access log carries two hostnames for the same paths, and any inbound link to the alias builds authority at an address you did not choose. None of it is catastrophic, and all of it is avoidable with one redirect rule.

What happens if the spare name has no certificate?

The request fails before your redirect exists. TLS is negotiated ahead of any HTTP response, so a browser asking for https://spare.example with no certificate covering that name aborts at the handshake and shows a security warning instead of following your rule. Since links, bookmarks and typed addresses now default to HTTPS, that is most of your traffic. AutoSSL covers aliases attached to the account, so it is usually a matter of waiting for its next run and then confirming the SAN list with openssl s_client.

Do I need MX records on a redirect-only domain?

Only if you want mail to it. A spare with no MX record means senders get an immediate rejection, which is honest and generates no work. A spare with MX records pointing at a mailbox nobody reads is worse than nothing, because it accepts mail and silently discards it. If the name is a common misspelling of your main domain, a catch-all forwarder to a monitored address is the useful middle option.

How many spare names can one account hold?

Aliases and addon domains draw on your plan's website allowance, so it depends which tier you are on and how many are real sites rather than redirects. Redirect-only names are cheap in every sense. If you are running out, that is usually a signal to review the shelf rather than to upgrade, and account upgrades here are a plan change rather than a migration in any case.

Keep reading

Changing hosts? Run through our checklist first.

A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.

You'll get the checklist email, then occasional pointers on keeping a site running fast. Unsubscribe the moment you want out — the privacy policy covers the rest.

Make the spare names pull their weight.

Every plan carries the essentials other hosts bill as extras, and the support queue is answered by engineers rather than a macro.

View WordPress Hosting plans