Configure SPF, DKIM, and DMARC DNS records to prevent your emails from landing in spam. Add TXT records to your domain provider's DNS settings, one for each record type. These configurations, combined with lemwarm's warm-up process, will significantly improve your deliverability. Takes about 15–20 minutes.

Additionally, focus on email content optimization, recipient list hygiene, and proper sending practices to further improve deliverability.

💡 If you use Gmail (@gmail.com) or Outlook (@outlook.com) personal accounts: These are already configured. This guide is for custom domains (e.g., you@yourcompany.com).

If your DNS records aren't configured correctly:

Setting up SPF, DKIM, and DMARC:

DNS (Domain Name System) records are settings that tell the internet how your domain works.

For email, DNS records tell providers like Gmail and Outlook:

Without these, email providers assume your emails are spam — and lemwarm can't fully protect a domain that isn't properly authenticated.

You must set up SPF, DKIM, and DMARC for proper email deliverability.

The steps below show you what records to create. If you need a walkthrough of where to add them in your specific domain provider, jump to the guide for your provider:

What SPF does: SPF tells email servers which services are allowed to send emails from your domain.

v=spf1 a mx include:_spf.yourprovider.com ~all

Replace _spf.yourprovider.com with your email provider:

💡 Important: Only include your actual email provider. Do NOT include lemwarm. lemwarm doesn't send emails directly — your provider does.

What DKIM does: DKIM adds a digital signature to your emails to confirm they were really sent by you.

⚠ Note: DKIM keys are long. Make sure you copy the entire string without truncating it.

Core recommendation: Always set DMARC to at least p=quarantine — never p=none.

What DMARC does: DMARC tells email providers what to do if SPF and/or DKIM fail.

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

✓ SPF, DKIM, and DMARC pass validation when checked with online tools (MXToolbox, DKIM Core, DMARC Inspector)

✓ Test emails land in inbox, not spam (send test emails to Gmail, Outlook, etc.)

✓ Email headers show authentication passed (check email source/headers for "PASS" status)

✓ Deliverability improves within 24–48 hours after DNS propagation

✓ lemwarm's warm-up results improve — a properly authenticated domain lets lemwarm build your sender reputation faster

While not needed for deliverability, here's a quick overview:

A Record – Points your domain to a website IP address

AAAA Record – Same as A, but for IPv6

CNAME Record – Redirects one subdomain to another

NS Record – Shows who manages your DNS settings (auto-set by domain provider)

MX Record – Defines where incoming mail is delivered (needed to receive replies)

Root cause: Wrong SPF syntax or missing provider include.

Root cause: DKIM key not added correctly or DNS hasn't propagated yet.

Root cause: DMARC record syntax error or wrong Name/Host field.

Root cause: DNS propagation takes time.

Root cause: DNS is only one factor. Other issues may include domain reputation, email content, or sending volume.

A: No. lemwarm doesn't send emails directly. Only include your actual email provider (Google, Outlook, Zoho, etc.) in your SPF record.

A: Usually 1–24 hours, sometimes up to 72 hours. You can check the propagation status with DNS Checker.

A: Yes, if they're all on the same domain (e.g., john@company.com, sarah@company.com). These records apply to the entire domain.

A: Yes. DNS authentication is a prerequisite for effective warm-up. lemwarm works by building your sender reputation through real email interactions — but if SPF, DKIM, or DMARC are missing, those emails are far more likely to land in spam, which undermines the warm-up process.