You wanted your .net or .in variant to just "work" alongside your main domain, so you added it in cPanel under Domains. Now it loads — showing your homepage, which is what you expected — but a few weeks later you notice Google has indexed both versions as separate pages, or the SSL padlock on the second domain shows a certificate for the wrong name. Neither is a bug. It's a Parked Domain doing exactly what a Parked Domain does, which is not quite what most people assume.
What a Parked Domain Actually Is
In cPanel's Domains section you'll see three ways to attach a second domain to an account: Addon Domain, Subdomain, and Alias (older cPanel themes call this a "Parked Domain"). They look similar in the UI but behave very differently under the hood:
| Type | Own document root? | Typical use |
|---|---|---|
| Addon Domain | Yes — separate folder, separate site | Hosting a second, unrelated website on the same account |
| Subdomain | Yes, or a subfolder | A section of your main site, e.g. shop.yoursite.com |
| Parked Domain / Alias | No — mirrors your main domain's content exactly | Brand protection, alternate spellings, old TLDs you don't want to lose |
A parked domain doesn't get its own public_html folder. It's just another hostname pointed at the same content as your primary domain. Visit either one and you'll see identical pages, because as far as Apache/LiteSpeed is concerned, there's only one site — just two doorbells.
Symptom: "It's Showing My Site, But Something's Off"
The tickets we get about parked domains usually fall into one of three buckets:
- Duplicate content in search results. Both domains get crawled and indexed separately, and Google occasionally picks the "wrong" one to rank, or splits authority between them.
- SSL warnings on the parked domain. The padlock shows, but clicking it reveals a certificate issued for the primary domain only, not the parked one — because AutoSSL never ran for it.
- "I wanted it to redirect, not mirror." A lot of customers park a domain expecting a 301 redirect to their main site. By default, cPanel doesn't redirect anything — it serves the exact same content under the new name, with no indication in the address bar that anything happened.
Cause: The Default Behavior Nobody Reads About Until It Bites
When you add a parked domain, cPanel does two things automatically: it creates a DNS zone entry for the new domain (an A record pointing at your server IP, plus the usual MX/CNAME defaults), and it adds a ServerAlias line to the virtual host config for your primary domain. That second part is the whole story — the web server is told "also answer to this name," nothing more.
Because there's genuinely one set of files being served under two hostnames, search engines that crawl both will see identical <title> tags, identical body content, identical everything. Without a canonical signal telling them which one is authoritative, you're relying on the crawler to guess — and it doesn't always guess right.
The SSL gap happens because AutoSSL, by default, secures your account's main domains and subdomains but doesn't always pick up newly parked aliases in the same run. Depending on your cPanel version and the AutoSSL provider, a parked domain can sit unsecured for a cycle or two until it's included in a certificate's Subject Alternative Names (SAN) list.
Fix: Setting It Up the Way You Actually Want
If you just want brand protection (no redirect, mirrored content is fine)
- cPanel > Domains > Create A New Domain.
- Enter the domain, untick "Share document root" only if you specifically want a separate folder — leave it ticked for a true parked/alias setup.
- Confirm the domain's nameservers or A record point at your SkyServer server IP (check via
dig yourdomain.com A +short). - Go to SSL/TLS Status in cPanel, select the parked domain, and click Run AutoSSL manually rather than waiting for the next scheduled pass.
If you actually want a redirect (the more common real-world need)
Skip the SEO ambiguity entirely and force a 301 to your primary domain. Add this to the .htaccess in your document root, above any WordPress rewrite block:
RewriteCond %{HTTP_HOST} ^(www\.)?parkeddomain\.com$ [NC]
RewriteRule ^(.*)$ https://www.yourmaindomain.com/$1 [R=301,L]
This keeps the parked domain registered and pointed at your account (so nobody else can grab it), but sends every visitor and every search crawler straight to your real domain with a permanent redirect — no duplicate content, no confusion about which version is canonical.
If you want to keep the mirror but stop the SEO split
Add a canonical tag to your site's <head> (most SEO plugins like Yoast or Rank Math do this automatically once you set a preferred domain), so crawlers know which hostname is the "real" one even when content is identical:
<link rel="canonical" href="https://www.yourmaindomain.com/" />
Prevention: Decide the Behavior Before You Click "Create"
- Ask yourself first: separate content (Addon Domain), a section of the main site (Subdomain), or same content under a different name (Parked Domain/Alias)? Picking the wrong one is the root cause of most of these tickets.
- If a parked domain is purely defensive — a misspelling, an old TLD, a competitor-adjacent name you don't want squatted — redirect it immediately. Don't leave it mirroring live content indefinitely.
- Check SSL/TLS Status after adding any new domain, parked or not. Don't assume AutoSSL caught it in the same run.
- If you manage several parked domains, keep a simple spreadsheet of which ones redirect, which ones mirror, and why — it's easy to forget the reasoning six months later when a client asks why two domains show the same site.
Frequently Asked Questions
Does a parked domain cost extra or need its own hosting plan?
No. A parked domain uses your existing account's resources and doesn't need a separate hosting plan — you're just pointing another registered domain name at content you're already hosting.
Can I give a parked domain its own content later?
Yes, but you'll need to convert it to an Addon Domain instead (or manually create a separate document root and virtual host), since a true parked domain always mirrors the primary domain's files by design.
Will Google penalize me for duplicate content from a parked domain?
It's not a manual penalty, but crawlers can split ranking signals between the two versions or index the "wrong" one as primary. A 301 redirect or a canonical tag both solve this cleanly.
Why doesn't my parked domain have SSL yet?
AutoSSL sometimes needs an extra run to pick up a newly added alias. Go to SSL/TLS Status in cPanel and click Run AutoSSL manually instead of waiting for the next scheduled cycle.
What's the actual difference between a parked domain and a redirect?
A parked domain, left alone, mirrors content under a second hostname with no indication to the visitor that anything changed. A redirect (301) sends the visitor's browser to the real URL, which is almost always the better choice unless you have a specific reason to keep both names showing identical content silently.
