Subdomains explained: a home for each function under your own name

A subdomain gives a function its own home under your name, and every one must be remembered and kept alive, or it becomes the forgotten corner that embarrasses the brand.

Your domain is a street address, and a subdomain is a building you put on your own street: shop.yourcompany and support.yourcompany behave like addresses of their own, with their own doors and their own rules, while staying under the name you own. That is the whole idea, and it is a good one. The trouble is that a building needs someone to keep the lights on, and subdomains are where companies quietly accumulate buildings.

The honest framing: a subdomain is a way to give a function its own home without buying another domain. And like every addressing decision, its cost is not technical but attentional: each subdomain is another place that must be remembered, secured, and kept alive, or it becomes the forgotten corner that embarrasses the brand. The old campaign site still up. The test page that leaked into search. Both live on subdomains exactly because subdomains are easy to make and easier to forget.

The failure versions repeat. The subdomain created for one event two years ago, still running the old software nobody patches: an unattended door with your name on it. The company with so many subdomains that nobody can list them, which is the inventory problem under a different name, because you cannot secure, renew, or retire what you cannot enumerate. And the subdomain that held customer data and was forgotten in the security review, because the main domain got all the attention and the forgotten corner kept the secrets.

The last one deserves its own sentence: people who look for weaknesses enumerate subdomains precisely because owners forget them. The review that covers the main site and stops there is a guard posted at the front gate of a property with several gates. Attention follows the name; risk follows the doors.

The practice starts at the moment of creation. A subdomain earns its place when the function has its own life: a shop system, a support portal, a dashboard the team logs into. A page that belongs in the main site's navigation does not earn one, because giving it an address of its own splits the visitor's attention and doubles your maintenance for no benefit. Ask the function whether it will outlive the campaign or the quarter, and let the answer decide.

Then the upkeep, which is what separates an address from an asset. Keep the inventory alongside the domain's other addresses, so the list of what is live is written down and not remembered. Put every subdomain inside the certificate coverage and the security review, not just the ones someone recalls. And when a function ends, take the subdomain down deliberately: retire it, redirect it if the old links matter, and remove it from the inventory the same day. A retired subdomain left answering for itself is not neutral; it is running your name on software you stopped looking at.

Guidance, not guarantees: we help owners keep their addressing deliberate, one inventory, one review, one standard for what earns an address under the brand. The mechanics of creating and pointing a subdomain belong to your registrar's documentation and your host, and the watching side, alerting you when one of them stops answering, is its own discipline. The rule travels: every address under your name is your name, whoever forgot it.