I want to make a lifelong email domain, but don't want to pay an enormous amount for a .com.<p>If I do a ".party" or something, will that ruin my life? Will web forms still reject it and will people always be adding ".com" whenever I tell it to them?
I regret using firstnamelastname.dev as my main personal account<p>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<p>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.
I have a .me address and I've been totally happy with it. My domain is my initials (same as my HN username - nlh) and I love that my email is just nlh @ nlh . me -- it's actually shorter and better than any .com I could reasonably come up with or purchase.<p>There is confusion maybe 10% of the time - it's fine. Most of the confused people think I mean "me.com", but it hasn't been a real issue.<p>Honestly the more confusing thing for most people is that my initials are "nlh" and they are used to the National Hockey League (nhl) and that often ends up getting confused.<p>But again, all of these are minor. I love my .me domain and email address and am very happy to keep it for life.<p>(PS / side story: The .com I wanted for many years was "noah.com" because that was my tongue-in-cheek nickname among friends since I was an early internet adopter tech nerd. The domain was owned by a guy who had a 1990s-style single page homepage with no content other than a single link to a photo album -- that lived in stasis for years - easily throgh the mid/late 2010s. I would ping him every few years and ask if he was ready to sell it yet and he always demurred. Then recently I checked and it appears to have been sold to a fintech company. I guess they made him an offer he couldn't refuse!)
There's definitely some risk, I wouldn't personally do it. Non popular TLDs can also change owners and things can get weirder.<p>Even with an .com domain you might face some problems from time to time. I've had a few sites outright ban any address that doesn't end with popular providers (gmail.com, live.com, etc). I have a burner gmail address just for these cases.
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 have a firstname.email address and it works pretty well 99.99% of time.<p>Very few forms have rejected it because their regex accepts only 2 or 3 characters.<p>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.<p>I'm using Proton with a catch all inbox, and have less spam than on my Gmail !
My 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.<p>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.
I registered a .email address for my surname when I saw it was available. However, I never ended up using it. I just imagined if I ever told anyone my email address was "first name at last name dot email", they'd probably think I didn't really understand how email worked or was trying to give them a fake address.
I have a .rodeo domain that I use for account emails. It is accepted 99% of the time, but I do fall back on a more common domain for a few websites that won't accept it as a valid TLD, including at least one Fortune 50 company.<p>I don't use it for outbound email very often, though. It's set up properly with DKIM/DMARC/SPF, but when I have used it for outbound email, it has failed to get through a couple of times.<p>That said, I do use a number of silly domains for web projects, and have never had an issue with any of them. I've heard it can be a negative signal for search inclusion on the major search engines, but honestly I couldn't possibly care less about that.
I’ve used .ME in the past, but then I settled on just using a .COM. The cost difference was negligible and nobody ever queries a .COM – I had people thinking my .ME was a mistake.<p>Unless you desperately want COMMONNAME.TLD, I’d go with the .COM for the lack of headaches. They’re ~$20 a year, which doesn’t seem like much money for the simplicity.
I know people who've used strange ones like .club or .wtf and gotten by and others who due to the groups they interact with have to switch back to dotcom or something more recognizable etc. If you fall in the latter where someone might not "get it" and maybe even append .com (hello@hb.party.com) thinking it's missing then that answers your question. In my country companies end with Ltd (Limited) so got one for my "company.limited" and it's pretty cool, no issues there and makes for some interesting convo when I give people, also my primary email is hosted at fastmail and my email is me@"my full name".com so I can also when some asks say email me @ ... as a sentence.
I’ve used first@last.name for the last 10 years or so. There have been probably a half dozen web forms where a regex expected 2-3 characters and I input an old gmail account that forwards to this address. Over the phone, the first@last part is easier to communicate since customer rep generally has the name info already. The .name throws them for a moment, but I’ve had one or two even tell me “oh, that’s cool, how did you do that?” which feels nice. It wasn’t my first choice, lastname.com was taken, but I like the precision of .name, arguably the most accurate TLD for a personal email address.
I've got an info domain and apart from one form giving me a warning ("make sure the domain is correct"), I've never had an issue over the last 15 years.<p>The only realistic risk I can think of is the whole TLD going under / changing like the .io - but that's still extremely unlikely.<p>There's a lot of ideas about different TLDs that are really hard to verify, but ended up somehow in the cargo cult knowledge area. Especially the search / spam ranking. I'm sure there's some edge case somewhere out there, but in general I've yet to see hard data that it's got any meaningful effect.
I got the vanity email address of (almost) my dreams: first@flastna.me (not actual tld, and the reason I had to add the first initial to my last name was because some jerk off squatter has lastna.me).<p>It looks so cool, and I kinda hate it. Why? Because people I need to give my email to (contractors, HR, doctors, insurance, bank, etc.) are completely baffled by the TLD and just enter it as flastname.com. To a lesser extent, I do still have sites reject the TLD (some surprising ones, for example office 365). I ended up creating an alias for first@firstlastname.com and mostly use that.
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.<p>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.<p>E.g. <a href="https://icannwiki.org/.party" rel="nofollow">https://icannwiki.org/.party</a><p>> but don't want to pay an enormous amount for a .com.<p>what, where? .com is on the cheaper end unless you buy it on the second-hand market.
You might want to consult Spamhaus's TLD spam reputation ranking:<p><a href="https://www.spamhaus.org/reputation-statistics/cctlds/domains" rel="nofollow">https://www.spamhaus.org/reputation-statistics/cctlds/domain...</a><p>God only knows how much weight it has on spam filtering policies of the many providers we have, but you'll at least know whether your TLD is considered a particularly bad offender with all that might entail.
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.<p>I use Office365 to host email, and have had no issues whatever with delivery.
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 like .club, .app, .today, etc.
Once 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.
We did a fintech startup and used the ever-so-hip-at-the-time .co TLD and several of our client banks would drop inbound emails from us by default, even as a reply-to email. It created some havoc with our sales process until we figured it out and did a quick name pivot.<p>"never again" -- are .com TLD registrations "enormous" amounts? I think mine are all in the 15 dollar/yr range. You make me think I should go look :)
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.
I use surname.id for my domain. A main concern for me (and apparently others in this thread) was making sure that when I had to dictate the email over the phone that it wasn't confusing to the person on the other end.<p>Beyond that, I just host my email with Proton which has been a really pleasant experience.
All anti-spam systems have false positives (some less, some more). Unusual things like an uncommon TLD make it more likely that you’ll be affected by an FP (and less likely that someone else would report it). You don’t need to stick to .com but I would avoid a TLD which has a low volume of legitimate emails.
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.<p>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.
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.
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.
It’s possible that you’ll lose some basic conveniences not using one of the original TLDs, and there may be some software out there somewhere that assigns implicit higher risk scores to non-conventional domain names, but you should be fine.
My usual email domain is a .us, and very ocassionally, I have trouble with it and need to use a .org.<p>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.
I have an .org address that very rarely bites me, but usually works in large majority of cases.<p>You should be fine- of course doing business with a silly domain name ymmv:<p>Shypooper.party or valiumlover.me might give employers & recruiters pause to think.
"ruin my life" sounds a bit drastic.<p>The only drawback I can think of is some sites not recognizing the TLD like you already suggested.<p>What cost do you consider enormous?<p>Yes, they're not the cheapest, but they're still cheaper than many other types.
I spent $900 on a clean dotcom domain name last year primarily for email purposes. I had a lot of doubts, but in hindsight I am happy I did it - now I can host my email anywhere while keeping the same address.
I thought it was good idea at the time, so I picked up a tld that allowed me to do first letter @remainingname.com so it looked something like j@coblast.com.<p>It ends up being overly confusing when communicating it.
One of my clients has a .us and recently purchased the equivalent of "exampleus[.]com" to make things a little easier for their customers.<p>it depends on the kind of people you you are networking with, I suppose.
i've been using a rather 'rare' two letter tld for my e-mail address since forever. besides the typical autocomplete in forms to suggest to change it to a more common tld, it seems to work quite well for me. People also don't seem to have an issue remembering the tld as it seems to match closely with the common tld used within my country, but distinctive enough to not forget. .party as tld might not be the best idea of course, considering you might want to be taken seriously in your future e-mailing endeavors.
I'd suggest on going with common and well known TLD if this is a long term commitment. Depending upon nature of email you're trying to send some mailboxes might reject or delay delivery.
One thing to consider is that cheaper/less common the TLD, the lower the spam reputation.<p>Also, check the renewal price - some of those newer TLDs have much higher fees for renewal than initial registration.
For under 10 people, it’s really not worth all the pain.<p>Biggest issue is trust, everybody will assume you’re a spam domain. Never mind the numerous number of forms that won’t allow it.
I've known a several admins who just flat out block all the new TLDs, because the ratio of spam and phishing to legitimate email is so high for them.<p>So as well as the issues with trying to explain a TLD to people and bad validation, you're also going to find that your emails are more likely to get flagged as spam out outright blocked.