Choosing between endings

The registration fee is the smallest cost of a domain ending. The real costs are paid in typing errors, in what people assume when they see it, and in a renewal price you do not control.

The four things an ending actually costs you

1. The traffic you hand to whoever owns the .com

A share of people typing your name will append .com regardless of what you printed. If someone else holds it, you are sending them customers permanently and for free. The size of that share depends on your audience, but it is never zero and it never goes away.

This is the strongest argument for the generic ending, and it is a practical argument rather than a prestige one. If you cannot have it, find out what is on it. A parked page is survivable. A competitor is not.

2. The spelling tax

Every ending outside the handful people expect has to be said explicitly, every time, forever. “Dot io” needs clarifying to anyone outside technology. “Dot co” gets heard as “dot com” and loses the visitor entirely — which is exactly why the owner of the matching .com benefits from your marketing.

3. Renewal risk

Generic TLDs operate under ICANN registry agreements that constrain how fast prices can rise. Country codes do not. Several popular ones have raised renewal prices sharply, and a registry with a captive base of brands has both the ability and the incentive to do it again. If your whole brand sits on a ccTLD, you are a price-taker indefinitely.

4. What the ending signals

Endings carry meaning whether you intend it or not. Some read as technical, some as regional, some as cheap. None of this is fair and all of it is real. The test is not whether you like the ending but whether your customer, seeing it in a browser bar or an email address, hesitates.

Two endings with a technical condition

.app and .dev are on the HSTS preload list at the TLD level. Every site under them must be served over HTTPS — a plain-HTTP fallback is not available, and a visitor cannot click through a certificate error. This is a good property, and it is a hard requirement rather than a recommendation. If any part of your stack cannot do TLS, these endings are not options.

A workable order of preference

The generic ending for your market, if you can get it at a sane price.
Your national ending, if you serve one country and expect to keep doing so. A local ending often outperforms a generic one for local trust.
A modified name on the generic ending — a prefix or suffix — in preference to the exact name on an obscure one. getnorthwind.com beats northwind.example for most businesses, because the ending is the part people get wrong.
An alternative ending, accepting the spelling tax, if the name is worth it and the audience will cope.

What is not on this list is buying eight endings defensively. For a business without a trademark to protect, that is an annual bill for names nobody would have typed.

Questions

Should I buy the .com as well as the one I use?

If you can afford it and it is available, yes — and redirect it to your real site rather than leaving it parked. It costs a registration a year and removes the single largest source of misdirected traffic. If it is taken and expensive, that is a real mark against the name, and worth weighing while the name is still a candidate.

Do search engines favour one ending over another?

Not by prestige. Country-code endings can carry a geographic association that helps in that country and does nothing elsewhere, which is a targeting consideration rather than a ranking bonus. Beyond that, the ending is not the lever — and any advice that treats it as one is usually selling domains.

Is a hyphenated domain a bad idea?

It is a working one with a permanent cost. The hyphen is dropped by people typing from memory and cannot be conveyed in speech without saying it, so you will spell the domain aloud for as long as the business exists. If you take a hyphenated name, check who holds the unhyphenated version first.

Reviewed 2026-09-20.