As a user of Loxo's emailing features, we recommend updating your DNS settings to authenticate Loxo's domain to increase your email delivery rate and to ensure your email address does not get flagged for sending mass emails.
Your personal or work email account is not designed to send a high volume of emails without the risk of your provider marking them as spam or junk. Loxo's server was built for high volume emailing and can significantly reduce the risk of your emails being flagged. To use Loxo's server, simply select "Loxo" under the Send as... option for your bulk email or campaign.
If you are interested in setting this up please reach out to firstname.lastname@example.org so we can provide you your unique records.
How to Set Up Your Domain
Without properly setting up your domain to trust Loxo's, many of these emails can end up going to spam. Setting it up is a matter of adding a few TXT records in your domain registrar and usually goes pretty quick once you know where to make the change. Each domain registrar has its own website and interface to allow you to manage this information, but the actual records that need to change are the same.
- Go to Gear Icon > Settings > Custom Imports
- Click on Show DNS Records for loxo.co
3. Use the generated fields to enter in two TXT and a CNAME field in your domain host.
Adding Records to your Domain
1. Login to your Domain host. If you don't know where it hosted you can use the below steps to find where your DNS is hosted:
- Go to https://www.whois.net/
- Enter your domain
- Look for the "Registrar WHOIS Server" field. This domain is usually but not always where your DNS is hosted.
- If the previous is not where your DNS is hosted look at the "Registrar Abuse Contact Email" field.
- If the previous is not where your DNS is hosted look for the "Name Server" field. This is the most reliable field but also the most difficult to interpret.
2. Login to your Domain Host and look for where you can update or manage your DNS settings (common domain hosts examples and instructions listed at the end of this article!)
3. Update or add an SPF record.
- A domain can only have one SPF record, if one already exists you must combine the current record with the Loxo record.
- Search for "v=spf1", if there are multiple pages, ensure all pages are searched.
- If a SPF record exists then add
include:spf.loxo.coto the record. For example, if your record is
v=spf1 include:example.com ~all, the final record should be
v=spf1 include:spf.loxo.co include:example.com ~all
- If a SPF record doesn't already exists then add a brand new TXT record with the value:
v=spf1 include:spf.loxo.co ~all. The hostname will either be "@", your domain, or left blank depending on the registrar.
4. Add the DKIM key:
- Add a new TXT type record.
- The hostname will be
- Copy the value from the spreadsheet support provided you. It will start with
5. Add the CNAME record:
- While this is optional it is strongly recommended for open, click, and unsubscribe tracking.
- Create a new CNAME type record.
- The hostname will be
- The value will be
6. Reach out to support again letting us know you made these updates and we can verify on our end that everything was set up correctly!
Common Domain Host Instructions:
- Godaddy: https://www.godaddy.com/help/manage-dns-zone-files-680?locale=en
- Namecheap: https://www.namecheap.com/support/knowledgebase/article.aspx/579/2237/which-record-type-option-should-i-choose-for-the-information-im-about-to-enter
- Network Solutions: http://www.networksolutions.com/support/how-to-manage-advanced-dns-records/
- Rackspace Email & Apps: https://docs.rackspace.com/support/how-to/set-up-dns-records-for-cloud-office-email-and-skype-for-business/
- Rackspace Cloud: https://docs.rackspace.com/support/how-to
- AWS Route 53: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/setting-up-route-53.html
- DigitalOcean: https://code.krister.ee/mailgun-digitalocean/
- Cloudfare. If you have a Cloudfare account you will need to do an extra step of confirming a CNAME record temporarily. You will also want to make sure to change the CNAME record to "DNS Only" instead of "Proxy".