Subdomain Example: What a Subdomain Is, With Real Examples

01 July 2026
by: Anaya Kapoor
in: Web hosting
Tags: domains, subdomain example, subdomain vs subdirectory, what is a subdomain
note: no comments

If you have ever visited a site like blog.example.com, shop.example.com, or support.example.com, you have already used a subdomain without thinking about it. A subdomain is simply a prefix added in front of your main domain name, separated by a dot. It lets you carve out a distinct section of your website that can live on its own, point to a different server, or run completely different software, all while staying under your one registered domain.

Table of Contents

The clearest subdomain example is blog.example.com. Here example.com is the domain you registered, and blog is the subdomain, the part sitting out front. In this guide I will walk you through exactly what a subdomain is, take apart the anatomy of a full domain name, show you a table of the most common real-world subdomains and what they are usually for, compare a subdomain against a subdirectory and against the root domain, and then show you how to create one yourself with DNS records. By the end, the dots in any web address will make complete sense.

Key Takeaways
• A subdomain is a prefix placed before your main domain, like the blog in blog.example.com, used to organize or separate a part of your site.
• The anatomy of a web address is subdomain.domain.tld, read right to left, with the subdomain being the most specific, left-most label.
• Common subdomain examples include blog., shop., app., mail., support., dev., and m., each conventionally tied to a purpose.
• Subdomain vs subdirectory: a subdomain (blog.example.com) is treated as a separate site, while a subdirectory (example.com/blog) is a folder within the same site.
• You create a subdomain with a DNS record (usually a CNAME or A record), and most hosting control panels let you add unlimited subdomains in a few clicks.

Here is the detail that surprises almost everyone: the www you type at the start of countless web addresses is itself a subdomain. www.example.com is technically the www subdomain of example.com, exactly the same kind of label as blog or shop. It became the universal convention in the early web to signal “this is the World Wide Web service of this domain,” but there is nothing magic about it. Many modern sites drop it entirely and serve everything from the bare root domain, while others redirect the root to www or the other way around. Once you realize www is just a subdomain that happened to win a popularity contest, the whole naming system stops feeling arbitrary and starts looking like what it really is: a flexible tree of labels you control.

What is a subdomain?

A subdomain is a subdivision of your main domain, created by adding a label and a dot in front of it. If your registered domain is example.com, then blog.example.com, shop.example.com, and app.example.com are all subdomains of it. You do not buy them separately and you do not register them anywhere. Because you already own the parent domain, you can create as many subdomains as you like, for free, through DNS.

Think of your domain as a property you own and subdomains as separate rooms or buildings on that property. They all share the same address book entry (example.com), but each one can be furnished completely differently. Your blog subdomain might run WordPress, your shop subdomain might run a dedicated ecommerce platform, and your app subdomain might point to an entirely separate server in a different country. To a visitor they feel like one connected brand; behind the scenes they can be wildly different setups.

The Domain Name System treats each subdomain as its own entry that can point wherever you want. That is the real power here. A subdomain gives you a clean, memorable address for a distinct service without the cost or hassle of registering a brand-new domain name. If you want the full picture of how domains are structured, bought, and owned, see the pillar guide below; this article zooms in on the subdomain layer specifically.

For the complete context on domains as a whole, read Domain Names: The Complete Guide to How They Work, Choosing One, and Owning Your Address.

What is the anatomy of a domain name?

A web address reads as a sequence of labels separated by dots, and a subdomain occupies the left-most, most specific position. The canonical structure is subdomain.domain.tld, and the trick to reading it is to go from right to left, from the most general part to the most specific.

blog . example . com
  |       |       |
sub-    domain   top-level
domain  (you      domain
        own it)   (TLD)

Let’s break down blog.example.com piece by piece, reading right to left the way DNS actually resolves it:

com (the TLD) is the top-level domain, the broadest category, sitting just below the invisible DNS root.
example (the domain) is the second-level domain, the part you actually registered and own.
blog (the subdomain) is the prefix you added, the most specific label, identifying a particular section or service.

Together, example.com is your registered domain, and everything you place in front of it with a dot becomes a subdomain. You can even nest them. In api.staging.example.com, the label staging is a subdomain of example.com, and api is a subdomain of staging.example.com. There is a practical limit (a domain name can hold up to 127 levels and 253 characters total), but in real life you will rarely go beyond two or three labels deep.

One thing worth noticing: the dot is doing all the work. Adding blog plus a dot in front of example.com does not create a new domain you have to pay for. It creates a child within the domain you already control. That is why subdomains are effectively free and unlimited, while every additional bare domain name costs another registration fee.

What are some common subdomain examples?

The most useful way to understand subdomains is to see the real-world ones you bump into every day, along with what each is conventionally used for. None of these names are required by any rule. They are simply strong conventions that have built up over decades, so visitors and developers instantly recognize them. Here is a table of the most common subdomain examples and their typical purpose.

Subdomain	Example	Typical use
`www.`	`www.example.com`	The main website (technically itself a subdomain)
`blog.`	`blog.example.com`	A blog or content section, often on separate software
`shop.`	`shop.example.com`	An online store or ecommerce platform
`store.`	`store.example.com`	An alternate name for an ecommerce section
`app.`	`app.example.com`	A web application or logged-in dashboard
`mail.`	`mail.example.com`	Webmail access or the mail server
`support.`	`support.example.com`	A help center, knowledge base, or ticket system
`help.`	`help.example.com`	Documentation or customer support content
`dev.`	`dev.example.com`	A development or testing environment
`staging.`	`staging.example.com`	A pre-production staging site
`api.`	`api.example.com`	A programmatic interface for developers
`m.`	`m.example.com`	A dedicated mobile version of the site
`cdn.`	`cdn.example.com`	A content delivery endpoint for static files
`status.`	`status.example.com`	A service uptime and incident status page

Notice the pattern. Each subdomain signals a purpose at a glance. When you see support., you expect help. When you see api., you expect something machine-readable. This predictability is part of why subdomains are so handy: they communicate intent before the page even loads. You are free to invent your own (events., careers., learn.), but leaning on the familiar conventions makes your site easier for everyone to navigate.

To put any of these subdomains to work, you will eventually be editing DNS entries.

What is the difference between a subdomain and a subdirectory?

This is the comparison that confuses people most, and it genuinely matters when you are planning a site. A subdomain lives in front of the domain (blog.example.com), while a subdirectory lives after it as a path (example.com/blog). They can both organize a blog section, but search engines, servers, and software often treat them quite differently.

A subdirectory is just a folder inside your existing website. example.com/blog is served by the same server, runs as part of the same site, and shares the main site’s setup. A subdomain, by contrast, is treated as a more independent entity: it can sit on a different server, run different software, and be managed almost like a separate website. That independence is the key trade-off.

Aspect	Subdomain (`blog.example.com`)	Subdirectory (`example.com/blog`)
Position	A prefix in front of the domain	A folder path after the domain
Treated as	A largely separate site	Part of the same site
Hosting	Can point to a different server or platform	Same server as the main site
Setup	Requires a DNS record	Just a folder; no DNS change
Common use	Distinct apps, stores, dev environments	Blog posts, sections within one site
Software	Can run completely different software	Usually shares the main site’s software

So which should you pick? As a rough rule of thumb, use a subdirectory when the content is part of the same site and the same software (most blogs and content sections fit here). Use a subdomain when the section is genuinely separate: a different application, a store on a dedicated platform, a help center on third-party software, or a testing environment you want walled off from production. There is a meaningful SEO angle to this choice too, and rather than repeat it here, I will point you to the dedicated article that covers it in depth.

What is the difference between a subdomain and the root domain?

The root domain is the bare registered name with nothing in front of it, like example.com, while a subdomain is anything you place before it, like blog.example.com. The root domain is what you actually buy from a registrar. Subdomains are children you create under it for free, as many as you need.

In everyday language, people use “domain” loosely, but precision helps here. example.com is your apex or root domain, the thing you own. www.example.com is a subdomain of it, and so is every blog., shop., or app. you add. The root domain is configured at the DNS level with what is often called an apex or root record, while subdomains are typically configured with CNAME records that point to a target. This distinction matters because some DNS features behave differently at the apex than they do for subdomains.

A handy way to keep it straight: you register exactly one root domain, and from that single purchase you can spin up an unlimited tree of subdomains beneath it. The root is the trunk; the subdomains are the branches. They share an identity but can each grow in their own direction.

How do you create a subdomain?

You create a subdomain by adding a DNS record that tells the internet where that new prefix should point. There are two common ways to do it: through your hosting control panel (the easy, beginner-friendly route) or directly in your DNS zone with an A record or a CNAME record (the manual route). Both end with the same result: blog.example.com resolves to a server you choose.

Creating a subdomain in a control panel

For most people, the simplest path is the hosting control panel. In cPanel, for example, you open the Subdomains tool, type the prefix you want (say, blog), choose the parent domain, and click create. The panel automatically generates the matching DNS record and a document root folder for the new subdomain. There is no need to touch raw DNS at all. This is how the vast majority of subdomains get made, and it takes under a minute.

Creating a subdomain with DNS records

If you are managing DNS directly, you have two main record types to choose from:

A record: points the subdomain straight at an IP address. Use this when the subdomain lives on a specific server you know the IP of. Example: blog → 203.0.113.10.
CNAME record: points the subdomain at another domain name rather than an IP. Use this when the subdomain should follow some other host, such as a third-party platform. Example: shop → stores.someplatform.com.

A useful trick worth knowing is the wildcard subdomain, written as *.example.com. A wildcard record catches every subdomain that does not have its own specific record, so any prefix a visitor types resolves to one place. This is essential for software that creates subdomains on the fly, like a service that gives each customer their own customer.example.com. After you save any DNS change, it needs to propagate, which can take anywhere from a few minutes to a couple of hours.

When should you use a subdomain?

You should reach for a subdomain when a section of your online presence is distinct enough to deserve its own space, its own software, or its own server. Around 7 in 10 of the subdomain decisions I help people with come down to one question: is this thing genuinely separate, or is it just another page on the same site? When it is genuinely separate, a subdomain is the clean answer.

Good reasons to use a subdomain include running a web app or dashboard apart from your marketing site (app.example.com), hosting a store on a dedicated ecommerce platform (shop.example.com), keeping a development or staging environment isolated from production (dev.example.com), serving a help center built on third-party support software (support.example.com), or pointing a section to a completely different server or region. In each case the subdomain gives you isolation: you can change, break, or rebuild that part without touching the rest.

When the content is simply part of the same site, running the same software, a subdirectory is usually the simpler and tidier choice. The decision is rarely about right and wrong. It is about whether you want one connected site or a family of related but independent ones. Match the structure to how the pieces actually behave, and the naming will take care of itself.

How DarazHost makes subdomains effortless

With DarazHost, creating subdomains is genuinely a few clicks rather than a DNS headache. Every hosting plan includes the ability to create unlimited subdomains directly from cPanel: you type the prefix, pick the parent domain, and the panel handles the DNS record and the folder for you automatically, so blog., shop., app., or any prefix you dream up goes live without you ever touching a raw zone file. DNS is managed for you with a clear, beginner-friendly editor for the times you do want A, CNAME, or wildcard records, and free SSL issues for your subdomains so they load securely from day one. If anything ever does not resolve the way you expect, 24/7 support is there to get your subdomain pointing exactly where it should.

Frequently asked questions

What is a subdomain example? The clearest subdomain example is blog.example.com, where example.com is the registered domain and blog is the subdomain in front of it. Other everyday examples include shop.example.com for a store, mail.example.com for webmail, and support.example.com for a help center. Each prefix marks a distinct section.

Is www a subdomain? Yes. www.example.com is technically the www subdomain of example.com, exactly the same kind of label as blog or shop. It became the early-web convention for the main website, but there is nothing special about it. Many modern sites drop www entirely and serve the site from the bare root domain.

What is the difference between a subdomain and a subdirectory? A subdomain sits in front of the domain (blog.example.com) and is treated as a largely separate site that can use a different server or software. A subdirectory sits after it as a folder (example.com/blog) and is part of the same site. Use subdomains for genuinely separate sections, subdirectories for content within one site.

Do subdomains cost extra money? No. Because you already own the parent domain, subdomains are free to create, and most hosting plans let you make as many as you want. You only pay again if you register a separate, brand-new domain name. A subdomain reuses the domain you already have, which is exactly why they are so popular.

What is a wildcard subdomain? A wildcard subdomain, written *.example.com, is a single DNS record that catches every subdomain without its own specific entry. Any prefix a visitor types resolves to one destination. It is essential for software that generates subdomains automatically, such as a platform that gives each customer their own personalized address.