Live data from Hacker News

Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

news.ycombinator.com

51–60 of 94 posts

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#51

Do 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.

I had a similar issue with .dev tld and getting emails from Walmart.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#52

I 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?

Yeah I don't think TLD matching is included in any bounceback or header that I have seen, for either Exchange or SpamAssassin, unless you have a named mail flow rule for it.

But, here is a fun lil screenshot from the exchange online antispam policies: https://i.imgur.com/fuUWke4.png

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#53
post #26

I 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.

I agree with the .ch comment, I was really just highlighting that sharing it with people has never been an issue.

Regarding the validation point, not so much anymore but during 2015 - 2020 you'd be surprised.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#54
I've been using a catch-all xx.to domain as my email for over 15 years without any problems. I use a different email for each website, like amazon@xx.to, etc. It's great for fighting spam and catching companies that sell your email address or have had data breaches.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#55
My primary email uses a .ng domain, currently through Fastmail. I’ve had exactly one site reject it and zero spam filter issues that I know of. The only real issue has been that it’s a pain to tell people in person, so I usually end up just giving my old Gmail in those situations.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#56

It's fine. Moreso than the hypothetical social-stigma aspect, read up a bit into the ownership and management policies of the TLD before committing. Make sure you have a basic understanding of the expectations and requirements (both on you and them) and are fine with them. ICANNWiki is a good start. E.g. https://icannwiki.org/.party > but don't want to pay an enormous amount for a .com. what, where? .com is on the ch…

what do you mean by "expectations and requirements"? The URL you've provided only contains four sentences total, which just explain when .party was created as a domain. Is it the wrong link?

What are the terms (if any) you need to agree to as owner of the domain? What are the requirements (if any) on you? What rights do the registry offer you? Is your use allowed and if not: what happens? Is there a particular jurisdiction applying? How are ownership disputes handled (e.g. what would happen to a targeted disney.party)? Is there a transparent process for expired domains (what happens if you fail to renew)?

> Is it the wrong link?

No, I said it's usually a good start. You'll have to do the actual fishing yourself (:

BTW, I believe that lack of transparency and perceived predictability can explain why some TLDs don't seem to get significant legitimate adoption among informed users with a long-term perspective (that is: usage trends towards nefarious, ephemeral, or casual small-scale, contributing to the reputational factor. What are the main parts to the feedback loop(s) is anyone's guess, tho).

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#57

Do 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.

I think if you set your domain as custom domain with big provider and set DNS entries you will have much better results.

But for personal mail it feels like waste of money instead of just using one of big providers domain directly.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#58
post #7

I have used .us forever and it's never caused a problem.

I can’t recommend this for anyone. It’s a nightmare. One of the biggest regrets I have is buying a .us domain It is forbidden by law to obfuscate the domain holder on the Whois record, like you can with any other domain. A decade after it expired, I finally stopped getting calls from web developers on the other side of the world trying to build me a site.

The contact information policy is a pain, though I don't get any calls.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#59

I wouldn't do it. Many rarely used TLDs have flaky registrars and there are a lot of people who mistype their own email let alone someone else's.

+1

I just registered a .re domain at OVH, and the first thing they did was provide me an account I cannot log into and cannot password reset. When I contact their support, they can't help me unless I call an international number.

The whole ordeal gave me such a bad taste, I've postponed using the domain and am thinking of just letting it expire. Such a bad service, when you're used to Porkbun. Domain registrars, on average, are just glorified domain sharks. I really hate how poor the service is when you come from a country where the NIC has been trusted through decades and their CEO comes to schools to lecture about the history of the open Internet.

Re: Ask HN: Is it a bad idea to make an email domain with an uncommon TLD?

#60
I have an .org address that very rarely bites me, but usually works in large majority of cases.

You should be fine- of course doing business with a silly domain name ymmv:

Shypooper.party or valiumlover.me might give employers & recruiters pause to think.

Post reply on HN