Pillar

Free domains, read honestly

Free domain offers are not all the same thing. Some are useful for testing. Some hide migration headaches. These notes draw the line between a sensible short-term choice and a long-term mess.

Green paper card labelled free domains on a research desk.

Free is not a single offer. It is at least three different offers wearing the same word. Treating them as one product is the source of most of the trouble around free domains. The W3C’s short note on cool URIs is a useful reference for why the address you choose now matters far more later.

Three kinds of free domain

  • Free subdomains. A platform gives you a hostname under its own domain (for example, a project on a hosting platform). You do not own the name; you rent visibility on someone else’s domain.
  • Bundled domain promotions. A registrar or host throws in a domain for the first year. You do own the name. The cost moves into renewal.
  • Truly-free TLDs. A small set of TLDs offer no-cost registration on specific terms. You technically own the name, but ownership is conditional and can be revoked.

Where free goes wrong

The common failure mode is investing time on a name you do not really control. A subdomain is fine for a side project, but it cannot move with you to another platform without redoing the work. A bundled domain is fine if the renewal price is reasonable; it becomes a problem when the renewal arrives at five times the introductory rate. A truly-free TLD is fine for testing; it becomes a problem when the registry policy changes and the name is suddenly someone else’s.

When free is fine

  • Throwaway prototypes, demos and time-limited tests.
  • Internal tools that do not need a public brand identity.
  • Learning projects where the goal is the project, not the name.

Exiting cleanly

The simplest way to keep options open is to assume from day one that the free name is temporary. Keep content portable, keep internal links relative, keep analytics configurable, and avoid printing the name on anything physical. None of that takes extra work. It just takes the decision being made early.

Where this fits next

For ownership context, see the domain profile notes. For hosting that survives a domain change, see the hosting notes. For setup checks before launch, see the checklists page.