Zone or Registry
Subdomain vs new domain — when a project has earned a registration of its own
One is a line in a zone you already control, free and instant. The other is a new entry at the registry, with its own renewal and its own fate. The difference is ownership structure, not just naming.
The short answer
Default to the subdomain: it costs nothing, exists the moment you add the record, inherits the parent name's standing, and keeps the estate on one renewal. Docs, apps, staging, regional variants and internal tools all belong there — projects that are facets of the brand rather than brands themselves.
Register a new domain when the project needs a fate of its own: a product that might be sold or spun out, a venture whose failure should not touch the parent's reputation, mail sent at volumes the parent should not vouch for, or a brand meant to stand without reference to yours. A registration is an ownership decision wearing a naming costume — make it when ownership is the question.
By the Hosting & Domains team · Reviewed 25 August 2026
1 record
What a subdomain costs to create
Instant
From zone edit to resolving
Own expiry
What a new domain adds to track
Separable
Only a registered name can be sold
Technically the two could not be more different, which is why the choice confuses people who meet it as a naming question. A subdomain is delegation within a zone you already run: add the record and shop.yourname.com resolves, no registry involved, no new renewal created, no new thing you can ever sell separately.
A new domain is a fresh registration — its own registrant record, expiry date, reputation and transferability. This page gives the comparison the registrar's framing: not 'which URL looks nicer' but 'should this project share the parent's fate, or have one of its own'. Answer that, and the naming answers itself.
What a subdomain inherits — for better and worse
A subdomain arrives with a family name: search engines associate it with the parent site, mail receivers read its sends in the light of the parent's record, and visitors extend it the trust the main name has earned.
The inheritance runs both ways. A hacked application on a subdomain, or spam from one, stains the parent's reputation directly — the family name vouches for every member.
It also shares infrastructure fate: the parent's renewal, delegation and registrar account carry every subdomain with them. One lapsed renewal and the whole family goes dark together.
What a new domain buys — and costs
Isolation, first. A separate name has its own reputation with search engines and mail receivers, its own certificate scope, and no power to embarrass the parent beyond the association you choose to advertise.
Ownership, second — the underrated half. Only a registered name can be transferred, sold or moved to a subsidiary; a subdomain is inseparable from its parent forever. Products with any chance of a life of their own deserve their own registry entry from birth.
The costs are real but boring: another renewal to track, another name to defend against lookalikes, and a brand that starts from zero standing everywhere — links, reputation and recognition all built from scratch.
The cases people argue about
The blog: subdomain or path on the main name — its whole purpose is feeding authority to the brand, and a separate domain squanders exactly that.
The shop: usually a subdomain too, unless it trades under a genuinely different brand. Customers trust shop.yourname.com precisely because of the family name on it.
Bulk and transactional mail is the sharp one: high-volume sending is commonly put on a related-but-separate domain, so a campaign mishap cannot drag down the deliverability of the parent's day-to-day correspondence. That is isolation earning its renewal.
Three tests that settle it
The obituary test: if this project died badly — hacked, spammed from, publicly embarrassing — should the main name appear in the story? If not, separate it.
The transfer test: is there any future in which this project is sold, spun out or handed to different owners? Subdomains cannot leave home; register anything that might.
The introduction test: will the project ever be introduced without mentioning the parent brand? A name that must stand alone in a sentence should stand alone in the registry. Fail all three tests, and the subdomain is not a compromise — it is the correct answer.
Zone entries are free; fates are not
The registrar's ledger of this comparison is short. A subdomain is a line in a zone: free, instant, revocable, and permanently welded to the parent's ownership, reputation and renewal. A domain is an entry at a registry: renewable, transferable, saleable, and answerable for itself.
Most projects are facets and belong in the zone. The few that are ventures deserve their own entry — and the commonest expensive mistake is realising which was which only when a buyer asks for a product that cannot be detached from your name.
- Subdomains created freely from the zone editor in cPanel
- Certificates covering the names you actually serve
- New registrations searched with renewals shown up front
- Both arrangements holdable in one account, one calendar
Why Hosting & Domains
Standard on every plan
The zone at your fingertips
Subdomains, records and certificates managed in one panel, so a facet of the brand ships the hour you think of it.
Registrations made with eyes open
When a project earns its own name, the search shows every ending with renewal beside registration — the fate priced before it is chosen.
Mail isolation done properly
Separate sending domains with their own SPF, DKIM and DMARC, so volume mail never gambles the parent's deliverability.
Quick Start
Order placed to site online
- 1
Run the three tests
Obituary, transfer, introduction. Any yes points to a registration; three noes and the subdomain wins on every count.
- 2
Ship facets in the zone
Add the record, cover it with a certificate, and let the family name do the introducing it exists to do.
- 3
Register ventures at birth
Anything with its own possible future gets its own name now, in your details, while every ending is still available.
Built In
Fitted to every plan
- Every project sorted as facet or venture before naming
- Subdomains covered by valid certificates, not warnings
- Volume mail on a sending domain the parent need not vouch for
- New registrations in your details with renewals diarised
- The parent's renewal guarded — every subdomain dies with it
- Lookalike endings of a new venture's name considered early
Frequently Asked
The questions that come up most
Do subdomains hurt SEO compared to subdirectories?
For most sites the practical difference is small: search engines understand both, and the parent association carries either way. Subdirectories consolidate signals slightly more directly, which is why blogs and docs meant to feed the main site's authority often sit in paths. The comparison that actually changes outcomes is subdomain-or-path versus a separate domain, which starts from zero.
Is a subdomain free? Really?
Yes — it is a record in a zone you already pay for through the parent's registration, and you can create as many as the zone sensibly holds. What it is not is separable: no subdomain can ever be transferred, sold or given a registrant of its own. Free, instant, and permanently part of the family — that is the whole trade.
Should staging and test environments get their own domain?
A subdomain is standard and sensible — staging.yourname.com, kept out of search with noindex and, ideally, behind authentication. The exception is anything security-sensitive enough that you do not want it enumerable under the main name's certificate transparency logs, where a separate, unadvertised name adds a layer of obscurity.
Why do companies send marketing email from a slightly different domain?
Deliberate reputation isolation. Campaign mail lives with sharper spam scrutiny than correspondence, and a bad campaign can dent the sending domain's standing with receivers. Housing bulk sends on a related domain with its own SPF, DKIM and DMARC means the parent's invoices and replies never inherit that dent. It is the clearest everyday case of a project earning its own name.
Can I promote a subdomain project to its own domain later?
Yes, and it is routine: register the new name, serve the project there, and redirect the subdomain's URLs permanently to their new home. Expect the new name to spend a while building the standing the parent lent it for free — which is why the transfer test is worth running early. Projects likely to graduate are cheaper to register at birth than to migrate at fame.
Keep reading
Domain Names
When the project passes the tests — search every ending with the renewal in view.
Web Hosting
Zone, subdomains and certificates managed beside the sites they serve, in cPanel.
.com vs .net
The first question a newly independent project's name will face.
Jargon Buster
Zones, records, delegation, registrants — the vocabulary this decision is made in.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Facets in the zone. Ventures in the registry.
Create subdomains freely where the brand should vouch for the work, and register the projects that deserve a fate of their own.
View Domain Names plans