If you get your own domain, get one on a well-known TLD (e.g. .com, .org or your own country code). If you get a gTLD that's not well-known, there are some endpoints that will block you because your email is "not valid".
> It's not a big deal. I've had a .so domain for a decade and have only had to use a different email a couple times
That is exactly the point krageon is making. If you have a .so domain (or .earth like me), you need to have a backup at least, so you can still access things like a normal human. My @gmail.com address have been used for this, but seems I'm gonna have to get yet another domain with a normal tld so I can stop using the gmail one for when .earth is not correctly accepted.
Price changes are a concern indeed. But I think if you get something form your country, or a .org, it should be mostly fine.
I've had the same .org domain for around 15 years now. Except for the coup we've seen last year where somebody tried to buy it privately (thankfully averted, I believe), I've see no price hike over time.
That part is probably not a good bet, as life can go in unexpected directions.
Some country providers (eg .eu) only provide service to their citizens, so if you move country or otherwise become "not a citizen" they'll terminate your domain. As happened recently to the UK holders of .eu domains. :/
Probably better to pick a .net/.com/.org domain, for (hopefully) longer term stability.
.eu is not a country. .co.uk holders were unaffected by Brexit. meanwhile .org had price caps removed and was nearly sold off to private capital on the promise of "we promise that for the first decade we will only raise prices by 10%/yr". I'm not so sure that a legacy TLD is a better bet than a ccTLD with a similar record of stability when we get into these long term long tail events.
Also .org falls under US influence, which may not have worked out so well had you been making this decision in Ukraine a decade ago
.eu is classified as a ccTLD [0], not gTLD by IANA, so for the purpose of this discussion it is one - and the registrar for it (EURid) requires ciitzenship of one of the member states to hold .eu domain. EU citizens living the UK can have .eu names, but no-longer-EU-citizens of UK do not.
Things like .rocks, .guru, .club, and all those other recent gold-rush gTLDs have been a disaster from the spam standpoint*. It doesn't help that some registrars are complicit via allowing massive bulk name purchases, so I see zillions of somebody@{random-word-1}{random-word-2}.goldrush addresses, all with valid DKIM/DMARC.
* Not to mention phishing. Is that link going to foobank dot com or foobank dot club?
Wow, didn't know this story. Imperialism at its finest from the Anglo-saxon world (well, actually started by the French with slavery but that was >200 years ago, I found way worse the decisions took 50 years ago).
.io isn't a gTLD at all, it's a ccTLD belonging to British Indian Ocean Territory (which I find to be bullshit, since those islands have no permanent inhabitants).
That said, there are ccTLDs which behave more like gTLDs (like .io, .me, .fm, .gg, .cd) and are treated as such across much of what you do online, but whether that'll impact your email delivery depends on who you communicate with and how they treat spam.
> .io isn't a gTLD at all, it's a ccTLD belonging to British Indian Ocean Territory (which I find to be bullshit, since those islands have no permanent inhabitants).
That's not strictly true - British Indian Ocean Territory has permanent inhabitants, just not any native ones (never had had them, really - it was uninhabited until 1793). US military Diego Garcia base is there...
It's bullshit for other reasons, and expulsion of Chagossians to build the base is a tragedy - but not due it being empty territory (it's not).
Well they did until the British exiled them all to build a US naval base on Diego Garcia. And they would very much like to return home. The UK courts have ruled in favour of the Chagossians, but they are consistently ignored by the UK and US governments.
The sysadmins at these companies must be laid off right now. Same with Windows admins using .local for their AD domain name, now you shot yourself in the foot never being able to sign some services with globally trusted certificates.
This doesn't mean you've ever been able to get signed certificates for nonexistent TLDs. If a TLD were to stop existing i would excuse the administrators who set up their systems under that domain, but if you're setting anything up that isn't under an available TLD you're doing it wrong.
