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

MailerLite domain authentication not working: DNS checks

Work through incorrect hosts, changed values, duplicate SPF records, lookup limits, propagation, and edits made at the wrong DNS provider.

Last reviewed October 6, 2026

Quick answerMailerLite 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.
Practical detail

Confirm the edit happened in the right place

Check the domain’s active nameservers and ensure the DNS editor belongs to that provider. A record added at the registrar will do nothing when another service hosts DNS. Use a public DNS lookup to confirm whether the new record is visible, but keep the MailerLite account as the source for the required value.

Record the host, type, value, TTL, provider, and change time before making another edit. After DNS changes propagate, verify the exact sending domain in MailerLite and inspect a real message header; a green dashboard status alone cannot prove every sending path is aligned.

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

Diagnose DKIM and verification names

DNS providers vary in whether they append the root domain to a host value. Compare the public record with the name MailerLite expects and avoid accidentally duplicating the domain. Check for missing characters, quotes, spaces, truncated targets, or a CNAME entered as TXT.

For root verification, the provider may require blank, @, or the domain. Follow the provider’s convention and current MailerLite instructions.

Practical detail

Repair SPF without creating a second policy

Search the root for existing SPF TXT records. Multiple SPF policies can make evaluation fail. Merge the authorized include mechanisms into one record, remove obsolete senders, and check the ten-lookup and record-length constraints.

Do not blindly paste a new value over an existing policy that authorizes other production services. Inventory those senders first or ask the person responsible for mail infrastructure.

Practical detail

Escalate with a complete evidence packet

If the record remains unapproved after reasonable propagation, collect the MailerLite-required values, public DNS results, nameservers, provider screenshots, timestamps, and the exact error. Redact account secrets. This lets MailerLite or the DNS provider distinguish propagation, formatting, delegation, and product-side issues.

After approval, send controlled tests and monitor authentication results. DNS approval alone does not validate consent, list quality, or inbox placement. Accounts in their 14-day trial can send before the domain is authenticated, so fix these records before the trial ends.

Continue when useful

Next: Authentication

MailerLite domain authentication adds DNS records for SPF and DKIM at your DNS host, and it is required once the 14-day trial ends.

Open Authentication →
Try MailerLite for 14 days →
Keep exploring

Related guides

AuthenticationMailerLite domain authentication adds DNS records for SPF and DKIM at your DNS host, and it is required once the 14-day trial ends.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.TroubleshootingWhen a subscriber gets nothing, check the status first: MailerLite sends campaigns only to Active subscribers, and automations do not start for Unconfirmed ones who have not confirmed double opt-in.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 troubleshooting — Merchant documentation · mailerlite.com · Merchant-controlled · read August 23, 2026
  2. MailerLite domain authentication guidance — Merchant documentation · mailerlite.com · Merchant-controlled · read August 23, 2026
  3. MailerLite SPF merge guidance — Merchant documentation · mailerlite.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
  6. MailerLite help: what the 14-day premium trial includes — Merchant documentation · mailerlite.com · Merchant-controlled · read October 6, 2026