Which domain variants are worth registering

For most small UK businesses, buy your main brand in .co.uk or .uk, plus the matching .com if you can, then point the extras at one primary site. Add two or three obvious misspellings if they are likely. You do not need dozens of other extensions.

This picks up from a website you already have online and a hosting plan in place. If you host your site with Hostworld on cPanel, the steps below show how to point and redirect extra domains to that site.

Before you start

• Decide your primary domain. You will redirect everything else to this. A single canonical home keeps search signals and analytics in one place.
• .uk versus .co.uk is a naming choice, not a technical one. Nominet runs both. The five-year priority window for .uk that applied to .co.uk holders ended on 25 June 2019. Owning one does not affect your right to keep the other.
• Buying many new extensions does not improve search rankings. Google treats all generic TLDs alike for ranking. A country-code like .uk is a strong UK signal.
• Changing nameservers moves your domain’s authoritative DNS. That affects where the world asks for your website and mail records. Plan a move, lower TTLs in advance, copy the zone to the new provider, and remove any DNSSEC DS record before you switch. Re-enable DNSSEC after you are stable on the new provider.
• Redirects should be permanent: use 301 or 308. Avoid 302 for a move you intend to keep.
• HSTS is powerful. Only enforce HSTS on a variant once you have a valid certificate for that domain and your redirect is proven. Do not preload a variant unless you understand the permanence and you intend to serve HTTPS on all its subdomains.
• Registry-level “wildcard” behaviour is not a thing you can rely on. TLDs are prohibited from wildcarding at the registry. Implement redirects at your hosting layer.

Step 1: Pick your primary domain and extension

Choose the web address you will advertise and build on. Your options for a UK business are usually:

• .co.uk: established and familiar for UK businesses.
• .uk: shorter and modern. Nominet launched direct .uk registrations in 2014. Many UK organisations use it.
• .com: globally recognised generic TLD. Treated the same as other generic TLDs for ranking.

The right choice depends on audience and brand tone. For a UK‑only market, .co.uk or .uk makes sense. If you aim beyond the UK, you may prefer .com as primary and still own the UK versions. Whichever you choose, plan to own the others defensively and redirect them to the primary.

Step 2: Decide the defensive set to register

Buy the small set that protects your brand without creating admin you do not need. UK government guidance recommends registering multiple common extensions to protect your name. For a UK SME, that usually means .co.uk, .uk and .com for the same label, plus a handful of obvious typos.

You do not need to chase every possible extension. Google does not reward you for owning many TLDs. Focus on the three core ones and one or two typos that a real user might make. If a typo is very unlikely, do not buy it.

Step 3: Register the domains

Register your chosen set with your registrar of choice. Notes for .uk names:

• The special right for a .co.uk holder to claim the matching .uk ended in 2019. Any unclaimed .uk names became first come, first served.
• Nominet is standardising .uk transfers to an EPP “TAC” code pull model. If you need to consolidate domains at one registrar, follow your registrar’s current transfer instructions for .uk.

As soon as the domains are active, plan where their DNS will live and where you will set up redirects and email handling.

Step 4: Plan DNS and any nameserver changes

Decide who will be authoritative for the domains you have added:

• Hosting on Hostworld shared or reseller hosting: point the domains to Hostworld nameservers. We will serve the DNS zone in cPanel for you.
• Hosting on a Hostworld VPS: you may run your own DNS or use a third‑party DNS provider. Keep authoritative DNS where you can manage it confidently and test it before a switch.

What a nameserver change does: at your registrar, the nameserver set tells the internet which DNS provider is authoritative for your domain. When you switch nameservers, everyone will begin asking the new provider for your A, AAAA, MX, CNAME and other records. If the new provider does not already hold a correct copy of your zone, your website and mail can stop working.

If you are moving DNS for a live domain, follow best practice:

• Lower TTLs several hours or a day in advance so you can move quickly when ready.
• Replicate the zone at the target DNS provider and verify lookups.
• If DNSSEC is enabled, remove the DS record at your registrar before the switch. Re‑enable DNSSEC with the new provider’s DS record after the move.

Step 5: Point variants to Hostworld and add them in cPanel

If your website is on Hostworld shared, reseller or WordPress hosting, set the nameservers at your registrar for each extra domain to our nameservers:

ns1.serverworld.uk
ns2.serverworld.uk
ns3.serverworld.uk
ns4.serverworld.uk

Once the registrar accepts the change, add the domain in cPanel:

• Log in to cPanel for the hosting account that serves your primary site.
• Add each extra domain as an Alias (also known as a parked domain) if you only want it to redirect. If you need it to have its own document root or subdomains, add it as an Addon Domain instead.
• Open cPanel’s Redirects tool. Create a Permanent (301) redirect from each extra domain to your primary domain URL. Include the scheme and host you have chosen, for example https://www.yourbrand.co.uk.

Why this matters: adding the domain tells Apache or NGINX on the server to answer for that hostname. The 301 redirect instructs browsers and search engines that the move is permanent. This consolidates links and avoids duplicate‑content issues.

AutoSSL in cPanel can issue certificates for addon domains and aliases so your redirect is covered by HTTPS. Note that some “service subdomains” of an alias (for example mail.aliasdomain.tld) are not included by AutoSSL unless you add the domain as an addon. If you only need the bare domain and www variant to redirect, an alias is often enough.

If you need help identifying the right cPanel option for your case, please open a support ticket.

Step 6: Pick www or non‑www and make it canonical

Decide whether your canonical host includes www. Both are fine. What matters is consistency and a permanent redirect from the non‑canonical one to the canonical one.

• In cPanel Redirects, add a Permanent redirect from http://yourbrand.co.uk to https://www.yourbrand.co.uk or the other way round, matching your choice.
• Ensure the redirect covers both HTTP and HTTPS so that any entry point ends at the same canonical URL in one hop.
• In your site templates, add rel="canonical" tags that point to the canonical URL. Keep your XML sitemaps listing only canonical URLs. This helps Google’s canonicalisation.

Use 301 or 308 for this. Avoid 302 for a canonical redirect because temporary redirects can delay consolidation and keep the wrong URLs indexed.

Step 7: Handle HTTPS and HSTS correctly on variants

HTTPS should work on every hostname a customer might type. For addon domains and aliases in cPanel, AutoSSL can request certificates. After adding the domains and before enabling any strict policies:

• Run AutoSSL and confirm a valid certificate covers each extra domain and www.
• Visit https://variant-domain.tld in a browser and ensure you see a valid padlock and a 301 to your primary site.
• Only then consider adding HSTS on the primary site. Be cautious about enabling HSTS or preloading it on redirect‑only domains. Preload is sticky and applies to all subdomains. If you force HTTPS without maintaining valid certificates, users can be locked out.

Step 8: Plan email handling for the variants

Decide what should happen to mail sent to the extra domains. In cPanel you can:

• Use Domain Forwarders to forward all mail addressed to one domain to another domain.
• Create per‑address forwarders, for example [email protected] forwards to [email protected].
• Set a Default Address (catch‑all) to accept anything that is not a defined mailbox or forwarder. This attracts spam and is usually not recommended.

Important deliverability notes:

• Simple forwarding often fails SPF and can break DMARC alignment. Gmail and other providers have tightened authentication checks. Plan forwarding with authentication in mind.
• DKIM on the original message helps when mail is forwarded. Some forwarders implement SRS and/or ARC to preserve authentication, but if you forward to third‑party mail, expect mixed results and test with major providers.
• Domain forwarders in cPanel do not forward messages for addresses that already exist as mailboxes or autoresponders on the source domain.

If email to the variant is mission‑critical, consider receiving it directly at the primary domain instead of forwarding across domains, or use per‑address aliases that keep DMARC alignment. Test any forwarding plan before publishing addresses.

Step 9: Test redirects and indexing

After configuration:

• Type each extra domain in a browser with and without www, and with http and https. You should land on your canonical URL in a single hop with a Permanent redirect.
• Check SSL certificates for the variants using your browser’s padlock details. Fix any mis‑matched names before adding HSTS.
• Search for your brand and click a few results. Any legacy URLs should redirect to the canonical site.
• Update your XML sitemap to list only canonical URLs. Keep internal links consistent with the canonical host.

This avoids duplicate site signals. Google’s canonicalisation factors include redirects, sitemaps and rel=canonical tags, so keep them aligned.

Step 10: Renew and review

• Set auto‑renew on the core three: .co.uk, .uk and .com. Letting one lapse invites impersonation and recovery is costly.
• Annually review any typos you registered. If a variant has had no hits and is not plausible, you can drop it. Keep renewals lean without opening a gap.
• Keep DNS documentation up to date. If you later move DNS providers, repeat the nameserver change checklist: lower TTLs, replicate the zone, handle DNSSEC, then switch.

What next

If you are running your own stack on a VPS and want to manage redirects at the web server level, see our VPS guides. If you need scalable compute close to your UK audience, our Linux VPS plans run in our Maidenhead, Berkshire data centre on the London network range.

If you would like us to check your DNS or cPanel setup for the variants you have bought, please open a support ticket.