The honest answer is that the extension matters less than founders fear and more than domain-hack enthusiasts admit. A great name on a slightly awkward TLD beats a mediocre name on a perfect .com almost every time. But the extension is not neutral: it sets a quiet expectation about what kind of company you are before anyone reads a word of your copy. The job is to pick one that fits the name, the market, and the person you need to trust you.
So treat this as a shortlist of defensible choices rather than a ranking. Below is how each realistic option actually behaves once your name is out in the world.
When .com genuinely still matters
For a lot of software companies, .com is a habit rather than a requirement, and they'd survive fine on something else. But three situations make it a real advantage. The first is paid acquisition: if you're buying traffic, a bare .com in the ad and the address bar leaks fewer clicks to competitors and misremembered typos, and that compounds across a budget. The second is who you're selling to. Enterprise buyers and older audiences still read .com as the default and anything else as a small question mark; when the deal is six figures and the buyer is fifty-five, you don't want your domain to be the thing they pause on.
The third is email. Deliverability itself doesn't care about your TLD, but recipients and their spam filters carry soft associations, and a cold sales email from a brand-new .xyz gets a fractionally warier reception than the same note from a .com. None of this makes .com mandatory. It makes it the safe default you should have a specific reason to leave.
The credible modern set
If the .com is gone or absurdly priced, several extensions are now legible enough to use without an explanation. They are not interchangeable, though, and each carries baggage worth knowing.
The tech default of the last decade, .io, is showing fatigue. It still reads as "startup," but that's the problem: it now reads as a certain kind of 2016 startup, and it sits under a country-code registry whose political status has periodically made people nervous. Usable, no longer distinctive. Meanwhile .ai has become the fashionable choice, and if you're actually an AI company it signals cleanly. Two caveats. It's an Anguillan country code administered on that island's behalf, renewals run expensive and are billed in two-year blocks, and the registry has had its own operational quirks; you're renting a trend at a premium. Name a company Verently.ai today and in three years the .ai may date it the way .io now dates its cohort.
The friendly fallback, .co, works and reads as a real company, but accept the typo tax: a meaningful share of people will type .com out of muscle memory and land on whoever owns your .com. If that owner is a parked page or a rival, you're funneling them traffic. The developer-facing pair, .dev and .app, are clean and modern with one hard technical fact attached: both are on the HSTS preload list, so they require HTTPS to load at all. That's fine for anyone competent, but it rules out any half-configured setup. Then there's the novelty tier, .so and .sh and similar, which make cute domain hacks but ask the reader to remember an unusual ending; fun for a side project, a real friction for a company you want said aloud in a meeting.
Country codes when your market is one country
If you serve a single country, its country-code domain is often the strongest choice, not a compromise. A German buyer trusts a .de more than a .com, because .de says "this business is here, subject to our rules, reachable in our language." The same holds for .co.uk in Britain, .com.au in Australia, .nl in the Netherlands. Trust is local, and the extension that reads most credible genuinely differs by country. An American founder's instinct that .com is universally safest is itself a local instinct.
The corollary matters if you're multi-market. There is no single TLD that reads best everywhere, so a company selling into Germany, France, and the US may want the country codes for the first two and a .com anchoring the group. Deciding that mix is exactly the kind of thing worth checking deliberately rather than guessing, which is why the domain name generator checks availability across the extensions that fit the markets you name rather than defaulting everyone to .com.
New gTLDs, and where they earn their keep
The descriptive new extensions, .studio, .agency, .design, .kitchen, tend to work best for exactly what they say: local and services businesses whose category is the point. A design studio on northfell.studio or a small firm on bram.agency reads as deliberate and self-aware, and the category word in the TLD does real work. Where these fall down is ambition. A company that wants to be a platform, not a studio, boxes itself in with a TLD that names a small category. Use them when the label is an asset, not when you'll outgrow it in a year.
What to avoid
Some extensions carry a discount-bin association earned over years. The legacy pair .biz and .info were sold cheap and heavily to spammers and thin-content sites, and enough people learned to distrust them that you inherit the reputation for free. Unless you have a specific reason, skip them. The other trap is the hyphenated compromise: rather than register get-northfell.com or northfellapp.com because the clean domain is taken, most companies are better off changing the name. A hyphen or a bolted-on word is the kind of thing people mistype, forget, and misquote, and it quietly signals that you took second choice. A different, cleaner name on a good TLD beats a contorted spelling of the name you wanted.
How to actually decide
Start from the buyer and the market, not the trend. If you sell to enterprises or run paid acquisition, fight for the .com. If you serve one country, look hard at its country code. If your category is your identity and you'll stay in it, a descriptive gTLD can be a feature. Reach for .ai or .io only if you're comfortable renting a trend, and treat .co's typo leak as a real cost. Above all, don't let a taken .com push you into a hyphen when the better move is a better name.
The extension is a constraint on the name and the name is a constraint on the extension; they're worth choosing together.