Help Center · Sending Domains

Authenticate Your Domain

Authenticate your domain to send emails from your own email addresses and improve deliverability.

Why Authentication is Required

Required before sending any campaign emails
Prevent your emails from being marked as spam
Better email deliverability
Prevent spoofing of your domain
Verify domain ownership
Important

Until your domain is authenticated, emails sent from your custom domain will fail with:

550 The from address does not match a verified Sender Identity.

Before You Begin

Make sure you have the following before starting the setup.

Access to DNS Management

You'll need to add DNS records to your domain's zone.

Domain Registrar Login

Login credentials for wherever your domain is registered.

Administrator Permission

Permission to edit DNS records for your organization.

Commonly used DNS providers

Cloudflare GoDaddy Namecheap Hostinger Bluehost AWS Route53 DigitalOcean Squarespace cPanel Plesk

Step-by-Step Guide

1

Open DNS Management

Log in to your domain registrar or DNS host and find the DNS settings for your domain. Depending on the provider, this may be labeled differently:

DNS Management DNS Zone Advanced DNS Zone Editor
2

Add the DNS Records

To authenticate your domain, you must add the DNS records provided in platform domain authentication page to your domain's DNS settings.

Your DNS records are generated specifically for your domain and are displayed in platform domain authentication page. Create all of the records exactly as they appear.

Important

Do not modify the record type, host/name, or value. Even a small change may cause domain verification to fail.

DNS record fields

Field Description
Type The DNS record type (such as CNAME or TXT).
Host / Name The hostname where the DNS record should be created.
Value / Points To The destination or value that the DNS record should point to.

Before Saving

  • Copy each record exactly as displayed.
  • Add every required DNS record to your DNS provider.
  • Do not remove or alter any existing DNS records unless you are certain they should be replaced.
  • If a record with the same Host/Name already exists, update it only if instructed, or remove any conflicting duplicate.
  • Save your DNS changes after adding all required records.
Note

The DNS records shown in website are unique to your domain. They will be different for every customer.

3

Save DNS Records

Save your changes. DNS records need time to propagate across the internet before they can be verified.

Usually
5–30 min
Sometimes
Up to 24 hrs
Rarely
Up to 48 hrs
4

Verify Domain

Click Verify Domain from our website in the domain Authentication page.

DNS Provider Tips

Cloudflare

Cloudflare proxies records by default, which breaks email authentication.

Disable Proxy

Set every record added above to DNS Only (gray cloud), not Proxied (orange cloud).

GoDaddy

GoDaddy automatically appends your domain to the Host field.

Host field

Enter only em2514, not em2514.yourdomain.com.

Namecheap

In Advanced DNS, add a new CNAME record and use the Host exactly as given, for example:

Host: s1._domainkey

Route53

When adding the records above in Route53:

Do not create Alias records

Create a standard CNAME/TXT record type instead of an Alias record.

Troubleshooting

Verification Failed

If verification fails, it's usually one of the following:

DNS hasn't finished propagating yet
Wrong values entered
Records added at the wrong DNS provider
Existing conflicting records
Proxy enabled (Cloudflare)
Small typos in Host or Value
DNS Taking Too Long?

DNS propagation can take up to 48 hours in rare cases, even though most changes apply within 30 minutes. If it's been longer than 48 hours, double-check the records were saved at the correct DNS provider.

Frequently Asked Questions

Yes. You can use any email provider, but to ensure high deliverability, we recommend authenticating a custom domain.
Yes. Each sending domain must be authenticated separately, even if they belong to the same account.
Yes, you can add and authenticate multiple domains as you need from the Domain authentication tab.
No. The DNS records used for authentication are separate from the records that power your website, as long as you don't modify existing A, MX, or website CNAME records.
You can, but doing so will break authentication and your ability to send from that domain until the records are re-added and re-verified.
Yes. If you move your domain to a new DNS provider, simply re-add the same records at the new provider and re-verify.