LiveChat 
Support 
Subdomain Names: How to Choose and Name Subdomains Well
A subdomain name is the prefix you place before your registered domain, separated by a dot: `blog.example.com`, `shop.example.com`, or `app.example.com`. Choosing that prefix well is a small decision with an outsized impact. A clear, conventional subdomain name tells visitors and developers exactly what they will find before they even load the page, while a cryptic one quietly adds friction to every link, bookmark, and support ticket.
This guide is about naming subdomains, not the underlying DNS plumbing. We will cover the most common subdomain conventions, the ideas worth borrowing, the best practices for picking names, when a subdomain is the right tool, and the two standard ways to create one. If you want the deeper mechanics of how subdomains stack in the DNS tree, see our companion guide on .
Key Takeaways
• A subdomain name is the label before your domain (`blog.example.com`); you create it yourself at no extra registration cost.
• Stick to conventional names like `blog`, `shop`, `app`, `api`, `docs`, and `status` — users and developers already expect them.
• Good subdomain names are short, lowercase, descriptive of the section’s purpose, and consistent across your sites.
• Use a subdomain when a section is genuinely distinct in function, environment, or region.
• Create one in seconds through cPanel’s Subdomains tool or by adding a DNS A or CNAME record.
What is a subdomain name?
A subdomain is an extension of your main domain, created by adding a label to the left of an added dot. In `blog.example.com`, the word `blog` is the subdomain name, `example.com` is your registered domain, and `.com` is the top-level domain.
The important practical point is ownership: you buy `example.com` once, but you can create `blog.example.com`, `shop.example.com`, `api.example.com`, and dozens more yourself, for free, whenever you need them. Each subdomain can point to a different application, server, or section of your site. That flexibility is exactly why naming them deliberately matters — nothing stops you from creating `xq7.example.com`, but nothing recommends it either.
What are the most common subdomain conventions?
Over decades of web use, a set of conventional subdomain names has become an unofficial standard. These names are valuable precisely because they are predictable: when a developer sees `api.`, they know it serves an API; when a customer sees `support.`, they know where to find help. Borrowing these conventions means your structure is self-documenting.
| Subdomain | Typical use |
|---|---|
| `www` | The canonical public website (the historical default prefix) |
| `blog` | Articles, news, and editorial content |
| `shop` / `store` | E-commerce storefront, separate from the marketing site |
| `app` | A web application or product dashboard |
| `api` | A programmatic API endpoint for developers |
| `mail` | Webmail access or mail server hostname |
| `support` / `help` | Help desk, knowledge base, or ticketing portal |
| `docs` | Product or developer documentation |
| `dev` / `staging` / `test` | Non-production environments for building and QA |
| `admin` / `dashboard` | Internal administration or control panel |
| `cdn` / `static` / `assets` | Content delivery and static file hosting |
| `eu` / `de` / `us` | Regional or country-specific versions of a site |
| `m` | A legacy mobile-only site (less common with responsive design) |
| `status` | A public uptime and incident status page |
You do not need all of these, and most sites use only a handful. The table is a menu of established patterns, not a checklist. Pick the ones that map to real, distinct parts of your project.
What are the best practices for naming subdomains?
Once you know the conventions, naming becomes a matter of discipline. A few consistent rules will keep your structure clean as your site grows.
Keep names short and lowercase
Subdomain names should be short and easy to type from memory. `docs.example.com` beats `documentation.example.com`; `app.example.com` beats `application-portal.example.com`. Always use lowercase — while DNS treats subdomains case-insensitively, mixed case in marketing materials and links only invites confusion and typos.
Be descriptive of the section’s purpose
The name should describe what lives there, not who built it or when. `shop.` clearly signals commerce; `status.` clearly signals uptime. A visitor should be able to guess the purpose of a subdomain from its name alone. This is also where conventional names pay off: they carry built-in meaning that custom names have to earn.
Stay consistent across your properties
If you run several sites, use the same names for the same functions everywhere. When `api.` always means the API and `staging.` always means the pre-production environment, your whole team — and your automation — can rely on that pattern. Inconsistency (one site using `dev.`, another using `test.`, a third using `sandbox.`) is a recurring source of mistakes.
Avoid cryptic or clever names
Resist the urge to be creative with infrastructure naming. A subdomain like `portal2.example.com` or `nexus.example.com` forces everyone to learn and remember what it means, with no payoff. Save creativity for your brand and content; keep your subdomain names boring, literal, and instantly legible.
The single most useful naming rule is also the least glamorous: use the conventional name. Names like `blog.`, `shop.`, `app.`, `api.`, `docs.`, and `status.` are not just common — they are *expected*. A developer guesses `api.yourcompany.com` before reading your docs; a customer types `support.yourcompany.com` before searching your menu. A clever or cryptic subdomain throws that intuition away and replaces it with a lookup. Unless you have a strong, specific reason to deviate, defaulting to the established convention means your structure works the way people already assume it does — which is the whole point of a name.
When should you actually use a subdomain?
A subdomain is the right tool when a section of your project is genuinely distinct. The clearest signals are:
- A separate application — `app.example.com` or `dashboard.example.com` for a product that is functionally different from your marketing site.
- A different environment — `staging.example.com` or `dev.example.com` to isolate work-in-progress from production.
- A regional or language edition — `de.example.com` or `eu.example.com` to segment audiences by geography.
- A standalone service — `api.example.com` or `status.example.com` that runs on its own infrastructure.
If a section is really just more content on the same site — such as a blog whose job is to strengthen your main domain — a subdirectory (`example.com/blog`) is often the better choice. We cover that subdomain-versus-subdirectory trade-off in detail in the . The short version: reach for a subdomain when there is a concrete reason, not by reflex.
How do you create a subdomain?
Creating a subdomain takes seconds and costs nothing beyond your existing domain and hosting. There are two standard routes.
Option 1: cPanel Subdomains tool
If your hosting uses cPanel, this is the fastest path:
- Log in to cPanel and open the Subdomains tool (under the Domains section).
- Type the subdomain name you want in the Subdomain field — for example, `blog`.
- Select your parent domain from the dropdown (`example.com`).
- cPanel auto-fills a document root folder (such as `public_html/blog`) where that subdomain’s files will live. Adjust it if needed.
- Click Create.
cPanel handles the DNS record and the web server configuration for you, and the subdomain is usually live within minutes. This is the simplest way to spin up `blog.`, `shop.`, `staging.`, or `app.` without touching raw DNS.
Option 2: A DNS A or CNAME record
If you manage DNS directly (or your subdomain points to a different server or service), add a record in your DNS zone:
- An A record maps the subdomain name to an IP address — for example, `app` → `203.0.113.10`.
- A CNAME record maps the subdomain name to another hostname — for example, `shop` → `stores.yourplatform.com`. CNAMEs are common when pointing a subdomain at a third-party platform or CDN.
After saving the record, allow time for DNS propagation before the subdomain resolves everywhere. Either method produces the same result; cPanel is friendlier for hosting on the same account, while manual records give you precise control for external services. For the record types themselves, see .
Spin up clean subdomains with DarazHost
DarazHost hosting makes naming and creating subdomains effortless. With the built-in cPanel Subdomains tool, you can launch `blog.`, `shop.`, `staging.`, or `app.` on your domain in seconds — no DNS expertise required. Need finer control? Our full DNS management interface lets you add A and CNAME records by hand for external apps, CDNs, and regional editions. Reliable, fast-resolving DNS keeps every subdomain you create pointing exactly where it should, so you can structure your domain cleanly from day one. And whenever you want a second opinion on how to organize your subdomains, our 24/7 support team is ready to help.
Frequently asked questions
What is a good name for a subdomain? A good subdomain name is short, lowercase, and descriptive of the section’s purpose, and it follows an established convention wherever possible. For a blog use `blog.`, for a store use `shop.` or `store.`, for an API use `api.`. Conventional names are instantly understood by both visitors and developers.
Can I use any word as a subdomain name? Technically yes — you can create almost any subdomain name you like. But just because you can use `nexus.` or `portal9.` does not mean you should. Cryptic names force people to memorize what they mean, so stick to clear, conventional names unless you have a strong reason to deviate.
Do subdomain names affect SEO? The choice of subdomain *name* matters less for SEO than the choice between a subdomain and a subdirectory. A clear name helps users and crawlers understand a section’s purpose, but for content meant to build your main domain’s authority, a subdirectory is often preferred. See our nested-domains guide for the full trade-off.
How many subdomains can I create? You can create as many subdomains as you need at no additional registration cost, since you only pay for the parent domain. Most control panels, including cPanel, let you add them freely. Just keep the set small and meaningful rather than sprawling.
Should the www in www.example.com count as a subdomain? Yes. `www` is technically a subdomain — historically the conventional prefix for the public website. Many modern sites serve the same content with or without it, but it remains the most established subdomain name of all.
