🧩 Subdomain Name Generator

Enter your root domain to get a ready-made list of subdomain names grouped by purpose — useful as a starting checklist when planning DNS records for a new project.

What you get back

Thirty-six conventional names in six groups, prefixed to whatever you type. It is a checklist held in the page, not a search - nothing is checked for availability, because subdomains are not registered. Any https:// and any trailing slash are stripped, so pasting a URL works.

The names are conventions worth following. Mail clients probe autoconfig and autodiscover automatically, and every engineer who joins expects staging and api to mean what they usually mean.

Turning a name into a working subdomain

Each one is a single record in your existing zone. Point it at an address for something you host, or at a provider's hostname for something you do not:

api      IN  A      203.0.113.10
www      IN  CNAME  example.com.
docs     IN  CNAME  d1a2b3c4.cloudfront.net.
mail     IN  A      203.0.113.20      ; the MX record then names mail.example.com
Delete the record when you retire the service. A CNAME left pointing at a SaaS account you have closed can be claimed by whoever registers that name next - a subdomain takeover, and abandoned staging and beta entries are where it usually happens.

Frequently asked questions

Do subdomains cost extra?

No. They are records inside the domain you already own, so you can create as many as you like at no charge. Hosting whatever sits behind them is the only cost, along with a TLS certificate - though a wildcard certificate covers every first-level subdomain at once.

How do I create a subdomain?

Add one DNS record. In your provider's panel, set the host or name field to just the label - api, not api.example.com - choose A for an IP address or CNAME for another hostname, and save. It works once the TTL on any previous answer has expired.

Is a subdomain better than a subfolder for SEO?

A subfolder is the safer default. Search engines treat a subdomain as a fairly separate site, so its authority builds on its own. Use subdomains for genuinely distinct systems - an app, an API, a status page - and folders for content that belongs with the main site.