I have used .us forever and it's never caused a problem.
Country one's are generally ok. Depends on wars, but generally ok :)
Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
21–30 of 94 posts
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#22I have a firstname.email address and it works pretty well 99.99% of time.
Very few forms have rejected it because their regex accepts only 2 or 3 characters.
And one e-commerce company called my phone after passing an order because I broke their billing system even though everything worked fine on the customer side.
I'm using Proton with a catch all inbox, and have less spam than on my Gmail !
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#23Once in a while I like to play word games with 2LD and TLD that make an interesting conjunection (d.boreh.am and such). I've encountered weirdness here and there with these over the years (not just email -- some DNS hosting providers will act oddly too). For that reason I'd stick with well trodden territory for my main email. Also as others have said, the fringe TLDs can carry some future risk of either censorship or price hikes.
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#24Do NOT use an uncommon TLD. I was using .lol recently and missed a job interview because the employer wasn't receiving any of my emails -- they kept getting rejected by their email servers! And I was only informed by Thunderbird weeks later when it was too late. Ever since then, I've just been using gmail for everything.
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#25My primary email domain is a .me. Never have problems with web forms. It can be more difficult to communicate verbally, so when saying it to non-technical folks I preface it with “my email is a bit weird” and then spell it out slowly. Young people seem to get it more easily. I also have an email on a .email domain, I have seen it occasionally get rejected by web forms. .party would likely have similar issues.
> It can be more difficult to communicate verbally
Together with a catch all email user part, it's a fun way to find out which companies offer employee discount. "My email is foo@my-domain", "oh, are you a Foo employee?"
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#26I brought a .ch (swiss, worked for my name) domain and have only ever had a small handful of bad sites that "validate" via checking for .com. I would say if you're going to make it a lifetime domain then perhaps something that works in a personal and professional setting might be worth considering.
I would say that .ch is not an uncommon tld at all, it is the national tld of a country and it has existed for decades. I also think that the issue you had with forms requiring .com must have been an amateur made website because I can't imagine someone who develops for a living doing that type of mistake.
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#27I bought .store and regretted it, ended up switching to .com Combination of spam classification and form fill regex issues
How do you know the spam classification happened due to the TLD?
You never really know the cause for things like that, otherwise you're just handing out instructions to spammers on how to circumvent restrictions. You can only double check the basics, idly guess about everything else, and try a new approach while crossing your fingers.
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#28"ruin my life" sounds a bit drastic. The only drawback I can think of is some sites not recognizing the TLD like you already suggested. What cost do you consider enormous? Yes, they're not the cheapest, but they're still cheaper than many other types.
> "ruin my life" sounds a bit drastic.
Not necessarily. Say you apply to a job advert and use an email address from your personal email domain as your contact. Say email exchanges between you and your potential future employer are silently dropped because their email provider deems your domain non-kosher. Your application is ultimately dropped as a result. Does this classify as "ruin my life"?
Before this scenario is brushed off as hypothetical, this happened to me on a couple of occasions albeit by using a not-so-popular email provider (i.e., not Gmail).
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#29I regret using firstnamelastname.dev as my main personal account
It’s uncommon, and causes confusion if I have to dictate it out over the phone. You have to optimize for the non-technical people scheduling appointments that don’t realize there are options other than .com
I’ve started the process of migrating over to a .com with my middle initial added, and it’s so much easier knowing that everyone will understand the TLD. I imagine .net would be similar.
Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?
#30What do you plan to use the email for? If it’s for serious stuff I would stick with one of the OGs. Not worth getting a “unique” TLD.
> Not worth What's the "worth" part mean here?
Your email may get rejected if it’s not one of the usual ones. May have issues receiving mail. My company for example blocks over 100 different TLDs. Don’t even look at reputation of domain, just automatic block. Not worth dealing with that imo.