discuss GTLDs and Email Security - Agree or Disagree?

[WeSell-Domains]

As a business owner and a domainer, I have never been a fan of the new GTLDs because of the headache it gives me when I think about actually using them as a URL in the real world. Explaining them to people you meet in the normal course of a business day. The leakage of traffic when advertising and marketing. Just the whole confusion they create when explaining or navigating to the URL. However, that pales into insignificance when you take into account the business disruption and security risk of not receiving emails by them going to the dot com version.

Read the entire article

 

[adsorbable]

I work for a major spam filtering company and I can tell you from personal experience that I would never use a gtld for my business email. Not only does it cause confusion, but it also is starting to be an instant trigger for a large amount of spam filters. The low gtld price (and the opportunity to get great keywords) has been taken advantage of by a lot of spam campaigns, which forces filters to often add those kind of domain extensions on a global level.

 

[Kuffy]

I used @tail email addresses - you try explaining those to people. I've still got 3, but I'm not using them much. An example of an @tail address is

[email protected]

 

[Kate]

It's actually hard to spell an E-mail address over the phone and be sure it will be properly understood by the other party, even in .com. It's one more reason why you should get a name that is easy to spell and remember, preferably in .com or a familiar, relevant ccTLD. Otherwise expect a lot of frustration and confusion, and misdirected E-mail. If you turn on catchall on your domains, you could be surprised.

 

[Grego85]

the same could be said for .org and . net domains and even .com names with dashes or creative spelling.