Live data from Hacker News

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

news.ycombinator.com

41–50 of 94 posts

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

#41

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.

Why would you think it was a good idea to use a non professional email address when job hunting?

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

#46
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.

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

#47

Using a .uk domain would probably solve your problem. I was looking for a cheap domain last year and for some reason .uk domains were the cheapest. (I bought it on Cloudflare for $4 per year). I also wanted to avoid some weird TLD that looks like a scam, and this one seems like it should appear reputable to people. I'm curious if anyone knows why this domain would be selling for a fraction of the price of weird TLDs…

.uk is not the same as .co.uk, .uk is in fact one of those scummy TLDs.

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

#48
post #14

My usual email domain is a .us, and very ocassionally, I have trouble with it and need to use a .org. I would never use my .fun or .pictures domains for email; I imagine there are lots of places still using ancient regexes for domain checking.

A few years ago I bought a couple .us domains on Namecheap without realizing that Whois Privacy isn't supported and accidentally doxxed myself. My main phone number was basically unusable for a few months with constant spam calls. I quickly changed the Whois info to a burner number but the damage was already done.

Ended up setting up Google Voice to immediately go to voicemail for all non-contacts and used a generic "this phone number is not in service" message with that ascending tone. No idea if that actually had an effect but the number of spam calls plummeted after about a month of that and is basically back to normal now.

I'm still steering clear of .us after that experience...

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

#49

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?

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

#50
I have been using a ".capital" email domain for work for the last few years, and the only issue I've encountered is form validation regexes that believe that the TLD portion must be between 2 and 5 characters long (literally "{2,5}" every time---must be copy-pasted from some regex recipe). I feel like it might be becoming less of a problem, but still something to keep in mind.

I use Office365 to host email, and have had no issues whatever with delivery.

Post reply on HN