We may earn a commission if you buy through links on this page, at no extra cost to you.
Home / How-to guides / Domain authentication
Practical guide

MailerLite domain authentication: DKIM, SPF and DNS records

Add the records supplied by MailerLite, avoid duplicate SPF records, verify DNS ownership, understand propagation, and document the sending setup.

Last reviewed October 6, 2026

Quick answerUse the exact records shown in your MailerLite account and edit DNS only at the authoritative host. Preserve existing SPF mechanisms instead of publishing a second SPF record.
Practical detail

Prerequisites for MailerLite domain authentication

The website host, domain registrar, and DNS provider may be different companies. Identify the service whose nameservers currently answer for the domain, then open the MailerLite Domains area and use the automatic path where supported or the exact manually supplied records.

Do not copy values from a generic tutorial when the account displays different names or targets. Keep the MailerLite instructions and DNS editor open side by side.

We may earn a commission if you buy through links on this page, at no extra cost to you.

Start a 14-day MailerLite trial →
Practical detail

Set up MailerLite domain authentication step by step

MailerLite domain authentication uses DNS records (SPF, DKIM and DMARC alignment) that prove MailerLite may send for your domain, and it is needed once the trial ends. DNS interfaces may append the domain automatically or expect the root as blank or @. Enter the record exactly as the account and provider require.

A domain should have one SPF record. If another service already appears, merge approved mechanisms into the existing policy rather than publishing a second SPF TXT record. Respect SPF length and lookup limits and remove providers no longer authorized to send.

Practical detail

Verify and allow propagation

Return to MailerLite and check the records. Some changes appear quickly; others take longer to propagate. If approval fails, compare names and values character by character, confirm the edit occurred at the authoritative provider, and inspect whether the interface changed the host or target.

Avoid repeatedly deleting and re-adding correct records during normal propagation. Record the change time and previous values so an unrelated mail problem can be diagnosed.

Practical detail

Add DMARC and ongoing ownership

Authentication is not a one-time checkbox. Review DMARC guidance, align sending domains, remove obsolete services, keep account recovery current, and monitor failures or unexpected senders. Large-volume sender requirements from mailbox providers can change, so check current official policies.

Assign an owner for DNS and email infrastructure. Document every authorized sender and the business message it sends. During the 14-day trial a new account may send its first campaigns before the domain is authenticated; after it, authentication is required.

Continue when useful

Next: DNS troubleshooting

MailerLite domain authentication is a set of DNS records (SPF, DKIM and DMARC alignment); when it will not verify, check that the records sit at the DNS host your domain uses and that only one SPF record exists.

Open DNS troubleshooting →
Try MailerLite for 14 days →
Keep exploring

Related guides

DNS troubleshootingMailerLite domain authentication is a set of DNS records (SPF, DKIM and DMARC alignment); when it will not verify, check that the records sit at the DNS host your domain uses and that only one SPF record exists.DeliverabilityMailerLite allows mail only to people who consented, bans purchased, scraped and two-year-old lists, and needs your domain authenticated once the 14-day trial ends; no setting guarantees the inbox.MigrationA MailerLite migration works in stages: import only active, opted-in contacts, map fields to groups, test a small consented segment, then cut over.Import consentBefore you import subscribers into MailerLite, bring only active contacts who opted in, as MailerLite's migration page advises, and keep proof of consent.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labeled so you can separate product claims from independent evidence.

  1. MailerLite domain authentication guidance — Merchant documentation · mailerlite.com · Merchant-controlled · read August 23, 2026
  2. MailerLite domain authentication troubleshooting — Merchant documentation · mailerlite.com · Merchant-controlled · read August 23, 2026
  3. Google email sender guidelines — Platform documentation · support.google.com · Merchant-controlled · read August 23, 2026
  4. MailerLite plans and pricing — Merchant documentation · mailerlite.com · Merchant-controlled · read October 6, 2026
  5. MailerLite product overview — Merchant documentation · mailerlite.com · Merchant-controlled · read October 6, 2026