Skip to main content

Authenticate your sending domain

Authenticating your sending domain proves to mailbox providers that your Broadcasts genuinely come from you. It improves inbox placement, protects your brand from spoofing, and is required before you can send from your own domain (for example, news@yourcompany.com). Authentication is set up once per domain by publishing a small set of DNS records.

Before you begin​

  • Access to your domain's DNS host (or a colleague who can add DNS records for you).
  • The exact sending domain or subdomain you want to authenticate (for example, email.yourcompany.com).
  • Admin access to the platform, where the required record values are generated for your account (confirm the exact steps in your account).
  • Allow time for DNS to propagate — changes can take from a few minutes up to 24–48 hours.

Steps​

  1. In the platform's admin or deliverability settings, add the sending domain you want to authenticate. The platform generates the DNS records specific to your account.
  2. Copy the generated SPF record and add it to your domain's DNS. SPF lists the servers allowed to send on your behalf.
  3. Add the generated DKIM record(s) — usually one or more CNAME or TXT entries — which let mailbox providers verify each message's signature.
  4. Optionally add a DMARC record (a TXT entry) to tell mailbox providers how to handle messages that fail SPF or DKIM, and where to send reports. Start with a monitoring policy such as p=none.
  5. Save the records at your DNS host, then return to the platform and run the verification/check action.

Result​

The platform shows each record as verified (green/checkmark). Once all required records pass, the domain is authenticated and available to select as the From address when you build and send a Broadcast. If verification fails, confirm the record values match exactly and allow more time for propagation before rechecking.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.