Many things can improve your email marketing, but the number one thing you should never do is use a public domain as your sending email address. Using a public domain may cause distrust in your recipients, send you to the Spam folder, and in some cases even have your emails quarantined completely! In this article, we’ll list the different reasons why using a public domain to send marketing emails is not a good idea.
A private domain is the email address provided by your website. For example, if your BUSINESS name is Shoe Store, then your website name would most likely be www.Shoestore.com. And your private domain email address would be email@example.com whereas a public domain would have @yahoo, @gmail, @aol in the domain part. If you want to keep your email and website reputations separate, then you can create sub-domains to maintain the distinction.
Using a private domain provides easy identification to your subscribers/customers. Your subscribers are more likely to open an email from someone they recognize than a personal email. Your sending domain is what your recipients see as the FROM in their inbox. A private domain adds professionalism to the emails. Based on the amount of spam out there, brand recognition builds up confidence and automatically increases the likelihood of email engagement.
Compared to using a public domain like AOL, Yahoo, or Gmail, etc. Using a private domain for sending emails provides you total control over maintaining the reputation of the domain and content. ISP’s tend to accept bulk emails coming from a legitimate and reputed domain compared to public domains. Owning a private domain also allows you to update the authentication records which are of the utmost importance when using an Email marketing platform
Owning a private domain enables you to update the following authentication records.
Although we have policies in place that allow you to send from a public domain, we do not recommend it. We highly suggest you send all your email marketing communication via a private domain with the SPF and CNAME updated.