5 ms·
> So it really depends on which ccTLD you're talking about. Indeed. ccTLD vanity domains are a bad idea in general, and using .af for such purposes is an extra
by nemetroid 3y ago
> So it really depends on which ccTLD you're talking about.
Indeed. ccTLD vanity domains are a bad idea in general, and using .af for such purposes is an extraordinarily bad idea. As another comment pointed out, the article's conclusion of "avoid all ccTLDs" rather than "do your due diligence" is weird.
- kijin 3y agoAgreed. I would generally not use a ccTLD unless 1) it's from a stable first-world democracy, and 2) I have either citizenship or a strong business presence in that country. Having said that, if OP is from the United States, I can sort of understand why the conclusion goes "avoid all ccTLDs." Americans have a tendency to treat the initial set of gTLDs as their own -- not only .gov, .mil, and .edu, but all the well-known ones, too.
- graemep 3y agoI would add, if it is the place where your business is located (or you live). Regardless of how good or bad a government it is, you are already subject to its jurisdiction.
- kijin 3y agoDepends on how permanent you think your current location is. Someone living and doing business in Canada might be eligible for .ca right now, but what if they decide to immigrate to the United States, and do business in the Bay Area instead? That's a fairly common situation for startup founders, but things can get really hairy unless they are a full Canadian citizen.