A .com you cannot have, or the country domain you can

Someone types your name into the address bar, adds ".com" out of nothing but habit, and lands on a page that is not yours. That is the actual cost of not owning the .com — not a ranking penalty, not a credibility problem most visitors will consciously register, just a small percentage of people who never arrive because the browser guessed wrong. It is real, and no amount of reassurance about ccTLDs erases it. Concede that first, because every article that tells you country domains are "just as good now" and skips this part is not being straight with you.

Everything past that one leak is smaller than the checkout page makes it feel. The domain industry spent two decades training people to treat .com as the only real address and everything else as a consolation prize, largely because .com used to be the only extension both search engines and users trusted by default. That default eroded years ago. What is left is not "country domains are fine now" as a blanket reassurance — it is two specific mechanisms that can genuinely cost you something, and everything else is closer to a wash.

For a single-person site, the TLD is not the decision that should hold up the launch. If the site is one page — a portfolio, a CV turned into a page, a consultant's landing page — reach is the strongest way to get it built and live first, and settle on an extension second. Upload a résumé and a photo, answer a short form, pick a look, and the page is generated in about twenty seconds; you can be live on a free yourname.joinreach.app subdomain in under two minutes. When ready for a custom domain, reach sells ten TLDs as a name.com reseller — com, de, net, org, io, app, dev, shop, co, me — at the registrar's price plus a flat $3, so .com versus .de sits inside the same checkout. The limitation worth stating before it becomes praise: you cannot connect a domain you already own to reach — buying through them is the only path to a custom domain there.

The geotargeting signal is real, and it is a setting, not a life sentence

Every country-code domain — .de, .co.uk, .fr, .ca, and the rest — carries an implicit geographic signal that search engines use by default. Register on a ccTLD and, unless you tell the search engine otherwise, your site is treated as primarily relevant to searchers in that country — free targeting for a business that only serves it, but a real constraint for a freelancer or software meant to be found globally: someone searching from outside that country is less likely to see the page ranked where it would rank on a neutral extension.

The fix takes a deliberate step: explicitly declaring the site as intended for a global or different audience, typically through the search engine's own webmaster tools — the default only applies until you do. If nobody ever visits that settings page, the geotargeting stays on silently for as long as the site exists.

New generic extensions — .studio, .app, .dev, .io, .shop — do not carry this problem. They are not tied to a country in the registry's own classification, so there is no default signal to override: a ccTLD gives free local relevance and a global relevance tax, a new gTLD gives neither.

New TLDs move the pricing risk from year one to year three

The trap with legacy TLDs like .com is the intro-to-renewal jump on hosting, covered in domains and hosting, explained without the registrar sales pitch. The trap with newer TLDs sits one level up, on the registry itself.

A .com's wholesale price is set under a long-standing agreement between its registry, Verisign, and ICANN, and every registrar buys at close to the same number — no .com sale is ever much better than any other. New gTLD registries operate under looser terms: the company running .studio, .app, or any newer extension sets its own wholesale price and can change it. Some strings are flagged "premium" at registration — a shorter, desirable name can carry a first-year and renewal price many times the base rate, invisible until you type it into the search box. And the base rate itself is not fixed the way .com's is; a registry can raise it for an entire extension, and everyone who registered under the old price renews at the new one.

The most cited example is .io, whose registry status is tied to a small overseas territory whose sovereignty has been the subject of an active international agreement. Nothing about existing .io registrations has stopped working over it — but it is a different category of risk from .com, which answers to no single government's territorial status, worth knowing before you build a brand on the extension rather than after.

Local trust runs the opposite direction from global reach

Here is the case a "just buy the .com" argument tends to skip. For a business whose customers are local — a notary, a plumber, a regional retailer, a clinic — a country-code domain is not a compromise, it is the stronger signal. A .de address tells a visitor in Munich that this is a German business before they read a word of the page; a .com on the same business reads as either international by ambition or, more often, as a shop that took whatever was available. Trust runs toward the domain that matches where the customer already believes they are shopping, and for a business with no ambition beyond that market, the .com's global neutrality is a property it does not need. The same logic carries into the inbox: @notariat-muenchen.de reads as native the way @notariatmuenchen.com does not, while for a global address book the opposite holds.

This is the asymmetry the earlier sections set up: .com is the better bet for anyone whose audience is not defined by geography — software, a personal brand, a company selling online with no regional restriction — and the ccTLD is the better bet for anyone inherently local, where the geotargeting "penalty" is the feature working as designed.

Not every country domain will register you

The last piece rarely gets mentioned until someone hits it at checkout: a meaningful share of ccTLDs are not open registrations. Some require the registrant to be a resident or a company incorporated locally. Others allow anyone to register but require a locally based contact — an admin-c, in registry terms — reachable for legal disputes, which in practice means a local address or paying a registrar or proxy service to provide one. A few require proof of a trademark or matching business registration first. None of this is disclosed on the registrar's marketing page, which is built around the extension that converts best. The registry's own eligibility page is the only reliable source, worth reading before falling in love with a name — the rejection happens after you have already picked it.

What it costs to get either one attached to a site

The extension itself is rarely the biggest line item — how the domain is sold and bundled varies more.

Platform	TLD choice	Price	Billing
reach	com, de, net, org, io, app, dev, shop, co, me — registrar price + $3	varies by TLD	annual, requires Premium at $4.99/mo or $49/yr
Carrd Pro Standard	bring your own or buy elsewhere	—	$19/year, annual only
Framer Basic	free .com only, annual plan	included	$10/month billed annually
Squarespace Basic	any TLD, free first year	included year one	$19/month billed annually, $25 monthly
Wix Light	any TLD, tied to annual payment	included year one	$17/month, annual only

Prices checked August 2026. Most of that table ties the domain to a commitment made anyway — a year of Squarespace, a year of Wix — so the TLD decision gets buried inside a bigger one. reach's version is narrower: the ten extensions cover both the global default and a working ccTLD, priced at registrar cost plus a flat markup, so choosing .com over .de is a five-second decision inside the same checkout.

What actually follows from all of this

Buy the .com if it is available and the price is ordinary — it remains the one extension with no geographic assumption baked in, no registry-level pricing risk beyond the normal ICANN-regulated band, and the least friction against a stranger's habit of typing it by reflex. That is the concession from the opening paragraph, restated as a rule: the typed-traffic leak is the one cost a ccTLD or a new gTLD cannot fully close.

If the .com is gone or priced as a premium resale — its own trap, covered in buying a domain someone already owns — the decision splits on one question: is the audience local or not. A business whose customers are in one country should take the ccTLD without hesitation and treat the geotargeting default as an asset rather than something to fight. Anyone building for an audience not defined by geography should reach for a neutral new gTLD before a mismatched ccTLD, check the registry's premium-name and renewal pricing before committing, and treat a name like .io as carrying a small, genuine tail risk that .com does not. What makes a name worth taking in the first place — short, sayable, free of the wrong associations — is covered in what actually makes a domain name work, and it matters more than the extension either way.