The .com you wanted is gone. It usually is. The question is what you take instead, and the alternatives are not equivalent to each other in ways that matter more than price.
What .com still buys
Not status. Two practical things: it is what people type by default when they half-remember a name, and it is what an email client will autocomplete. If someone hears your name and guesses, they guess .com. Whoever owns it collects that traffic, and if that isn't you, it is often a competitor or a parking page carrying ads.
That is the entire case, and it is a real one. It is also not decisive on its own, because plenty of well-known companies run happily on something else.
The common alternatives
Briefly, and honestly.
- .co — reads closest to .com, which is both its strength and its problem: you will lose some typed traffic to the .com forever. Fine if the .com isn't a direct competitor.
- .io — established in tech, unremarkable to that audience, meaningless to everyone else. See the warning below.
- .ai — currently expensive and currently fashionable. Fashion is a poor foundation for something you cannot cheaply change later.
- .app and .dev — require HTTPS, which is a small operational fact rather than a burden. Clear meaning, no ambiguity.
- Your country's code — .co.uk, .de, .com.au. Excellent if you serve one country. A constraint if you later don't.
The risk that isn't obvious
Country-code domains belong to countries, and countries change. A ccTLD is administered under a national policy that can be revised without reference to you, and the extension's continued existence is tied to the territory's status. This is not theoretical — .io's future has been the subject of active public discussion following the agreement over the Chagos Archipelago, and the eventual outcome is a matter for the registry and the governments involved rather than for the people using the domain.
Some ccTLDs also carry local presence requirements — a registered address or entity in the country — either at registration or on renewal. Check before buying, not after.
None of this makes them unusable. It means a ccTLD is a domain with a landlord, and you should know that before you build a business on top of it.
The choice most people should actually make
Given a .com you can't have, the options in rough order of how well they tend to work out:
- Change the name so a .com is available. Unpopular, usually correct. You are at the cheapest possible moment to do it.
- Add a short word to the name and take that .com — get, try, the, or your category. One word, applied identically to your handles.
- Take a good alternative extension and accept losing some typed traffic.
- Buy the .com from its owner, if it is genuinely for sale and the number is one you can live with.
Option two is underrated and the mechanics of it — which word, and how to keep it consistent — are worth reading about separately before you pick one.
Whatever you choose, check the handles against it
The domain is one decision and the handles are eleven more. A .co you love with no matching handles anywhere is a worse position than a .app with a clean sweep, because the handles are where people actually find you day to day.
Check the whole set at once. That is the only view that tells you what you are really choosing between.