Warmerly
Checked every six hours per mailbox, with a written fix for each finding.
Warmerly
lemwarm
One-to-one · SPF, DKIM and DMARC checks
SPF, DKIM and DMARC checks
One row, in depth: what each tool does, the verified numbers, and who each suits.
Lemwarm details read from its pricing page, home page, blog and lemlist's help centre on 21 October 2026.
Warmerly
Checked every six hours per mailbox, with a written fix for each finding.
lemwarm
A technical setup check; it pauses warm-up when MX, SPF, DKIM or DMARC fail, with an error code and fix. Interval not stated.
The short answer
SPF, DKIM and DMARC checks, in one look.
Warmerly checks SPF, DKIM and DMARC every six hours for each mailbox, with a written fix for each finding. Lemwarm includes a technical setup check, and pauses a mailbox when MX, SPF, DKIM or DMARC fail, with an error code and fix. Neither is clearly ahead. Last checked 21 October 2026.
lemwarm
A technical setup check; it pauses warm-up when MX, SPF, DKIM or DMARC fail, with an error code and fix. Interval not stated.
The picture
Drawn side by side.
How the records get checked
SPF, DKIM, DMARC and MX
Warmerlylemwarm
WarmerlyEvery six hours, on its own
- SPFchecked, with a written fix
- DKIMchecked, with a written fix
- DMARCchecked, with a written fix
- MXchecked
lemwarmSetup check, and a pause on failure
- SPFpause, error code and fix
- DKIMpause, error code and fix
- DMARCpause, error code and fix
- MXpause, error code and fix
Lemwarm's pause guide says DNS changes can take up to 72 hours to propagate. It does not state how often its setup check runs.
On screen
What it looks like.
WarmerlySample data
How Warmerly does it
Warmerly, in detail.
Records checked every six hours, with a written fix.
01
Checked every six hours
The records sweep runs every six hours across every mailbox that is not dead or paused. A Re-check now option is on the mailbox Health tab.
Warmerly product, checked 21 October 2026
02
A written fix for each finding
Each finding has a title, an explanation and a fix. SPF is checked for the 10-lookup limit, DKIM for key length and test mode, DMARC for policy and reporting address.
Warmerly product, checked 21 October 2026
03
Unknown is never green
A check that could not run is shown as unknown, not as fine.
Warmerly product, checked 21 October 2026
04
Quality, not just presence
SPF is checked for its ending rule, the 10-lookup limit counted through includes and redirects, and malformed address terms. DKIM is checked for key length (1024 bits or fewer is flagged as weak) and test mode. DMARC is checked for policy, subdomain policy, percentage and a reporting address.
Warmerly product, checked 21 October 2026
05
Three severities
Each finding is a fail, a warn or an info note. Only fails can colour a domain red, and one hard failure is amber and two or more is red, so a working domain with a monitor-only DMARC policy is not painted as broken.
Warmerly product, checked 21 October 2026
06
Advisories never email you
The sweep alerts only on a hard failure, not on every domain that is less than perfect. Most healthy domains publish a monitor-only DMARC policy, and alerting on that would have mailed owners about something that is not broken.
Warmerly product, checked 21 October 2026
07
Two blocklist registries
Domains are looked up on Spamhaus DBL, SURBL, URIBL, NordSpam DBL, Spam Eating Monkey and s5h. The sending IP is looked up on Spamhaus ZEN, SpamCop, Barracuda, PSBL, Mailspike, NordSpam, Spam Eating Monkey, Lashback UBL, DroneBL and GBUdb Truncate.
Warmerly product, checked 21 October 2026
08
Refusals are not listings
If a list refuses our query, for example because of rate limits, the card shows an error and not a listing. A partial answer is shown amber with the count of lists that answered.
Warmerly product, checked 21 October 2026
09
The record to publish
Under a failing SPF or DMARC chip the card shows the exact record to add, merged into the SPF record that is live now, with a copy button. It is suggested for Google and Microsoft mailboxes, and never under a passing chip.
Warmerly product, checked 21 October 2026
10
Re-checks are rate limited
A Re-check now request is held to one per six hours per domain, the same as the sweep interval, so pressing it repeatedly cannot multiply lookups across the blocklist operators.
Warmerly product, checked 21 October 2026
11
Checked when you connect
Connecting a mailbox by the API starts a DNS pre-flight check for SPF, DKIM, DMARC and MX in the background, and the result is stored on the mailbox.
Warmerly product, checked 21 October 2026
12
Shared consumer domains are handled honestly
On gmail.com or outlook.com the records are the provider's, so Warmerly marks non-passing records unknown instead of telling you to fix something you cannot change.
Warmerly product, checked 21 October 2026
13
Free DMARC report monitoring
Any workspace can point its DMARC reporting address at Warmerly for up to 10 domains and see who sends as the domain and whether it passes, from the daily reports mailbox providers send.
Warmerly product, checked 21 October 2026
How Lemwarm does it
Lemwarm, in detail.
A setup check, plus automatic pauses with an error code and fix.
01
A technical setup check
The Essential plan includes a technical setup check, which a Lemwarm blog post says flags any DNS issues that could hurt deliverability.
lemwarm.com/blog/how-to-boost-your-email-deliverability · read 21 October 2026
02
Pauses on authentication failures
lemlist's help centre lists codes for SPF, DKIM, DMARC and MX failures that pause lemwarm, each with a suggested fix.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
03
Blacklist listings
The same guide covers listings on SpamRL and SpamCop, with steps to request delisting.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
04
A setup check on the dashboard
lemlist's help centre says the technical check flags DNS issues that could affect deliverability when you connect, and the Warmup Score gives email setup and DNS 40 of its 100 points.
help.lemlist.com/en/articles/14653207-how-to-set-up-and-use-lemwarm · read 21 October 2026
05
Setup errors by code
The pause guide lists codes for invalid or missing DMARC, a rejected DMARC, missing DKIM, SPF or DMARC, a receiver's misconfigured SPF, an incomplete SPF, failed DKIM or SPF checks and MX, SPF or DMARC errors that stop the provider verifying you.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
06
One fix for every authentication code
For all of them the guide says to validate SPF, DKIM and DMARC, confirm they point to the right sending servers, remove duplicate SPF TXT entries, fix formatting and wait for propagation. It adds that you should not add lemlist to your SPF record, because your own provider sends the mail.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
07
MX and DNS codes
Separate codes cover a missing, wrong or unreachable DNS record and no valid MX record, with the fix to check the zone for typos and repair MX, SPF and DMARC.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
08
An automatic toggle check
A further code says lemwarm paused automatically because MX, SPF, DMARC or CTD was not valid, and asks you to check every record before restarting.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
09
Blacklist codes
Codes for SpamRL and SpamCop listings come with steps: request delisting, warm a secondary domain meanwhile, use lemwarm's blacklist check, pause campaigns, and verify with MXToolbox or MultiRBL. The guide says review typically takes 24 to 72 hours.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
10
Different tools disagree
The guide notes that different blacklist tools can show different results and that a listing does not always mean a real deliverability problem.
help.lemlist.com/en/articles/12918125-why-was-lemwarm-paused-full-guide-to-all-pause-reasons-and-how-to-fix-them · read 21 October 2026
11
Low score if setup is broken
The setup article says a red score, below 65, is usually a DNS or configuration issue or a blacklist hit, and tells you to check SPF, DKIM, DMARC and blacklists before sending campaigns.
help.lemlist.com/en/articles/14653207-how-to-set-up-and-use-lemwarm · read 21 October 2026
What Lemwarm does not say
We looked, and found no statement on these. That is about its published pages only, not about the product.
- How often the setup check runs
- Which blacklists lemwarm's own check queries
- Whether the technical check suggests the exact record to publish
The numbers
Only what we could verify.
| Measure | Warmerly | lemwarm |
|---|---|---|
| SPF, DKIM and DMARC checks | Checked every six hours per mailbox, with a written fix for each finding. | A technical setup check; it pauses warm-up when MX, SPF, DKIM or DMARC fail, with an error code and fix. Interval not stated. |
| Check interval | Every six hours | Not stated |
| DNS delay noted | Not applicable | Up to 72 hours to propagate |
| Hard failure alerts | Only on a hard failure, never on advisories | Not stated |
| Re-check limit | Once per six hours per domain | Not stated |
| SPF lookup limit checked | 10 lookups | Not stated |
| DKIM weak key flagged at | 1024 bits or fewer | Not stated |
| Blocklist time to review a delisting | Set by each list | 24 to 72 hours per its pause guide |
| Weight of DNS in the score | Not a score input | 40 of 100 points |
| DMARC report monitoring | Free, up to 10 domains | Not stated |
In practice
What it means for you.
Our reading of the facts above. Not a promise, and not the only reasonable reading.
A pause is a safety net
Pausing a mailbox with broken records protects the sender, and a written fix shortens the repair. Both tools do this in some form.
A broken SPF record, step by step
Say a domain publishes two SPF records. Warmerly's check reports more than one SPF record as a failure with the fix. Lemwarm's pause guide covers duplicate SPF TXT entries under its authentication codes. Either way the repair is to merge them into one record and wait for DNS to propagate, which the pause guide says can take up to 72 hours.
An advisory is not an alarm
A domain with DMARC set to monitor only works. Warmerly shows it as an advisory and does not email you about it. If you want to move to a stricter policy, the card says so, and Lemwarm's guide warns against strict policies such as reject too early.
A listing found by one list only
If one blocklist shows your domain and others do not, both vendors say the same thing: check more than one tool before deciding it is a real problem. Warmerly shows how many lists answered, and Lemwarm's guide points to MXToolbox and MultiRBL for a second opinion.
Pausing versus warning
Lemwarm pauses warm-up when a record fails, which protects the mailbox but stops warming. Warmerly's sweep alerts on a hard failure and shows the fix, and a mailbox is paused on health, not on a record alone. Choose by whether you want the tool to stop for you or to tell you.
Who it suits
Pick the one that fits.
Warmerly
Warmerly is the better fit if
- You want the check interval published
- You want free DMARC report collection as well
- You want the check interval and the lookup rules written down
- You want the exact record to publish shown under a failing check
- You want free DMARC report monitoring for your domains
lemwarm
Lemwarm is the better fit if
- You want error codes for each pause reason in a guide
- You want a code for every pause reason in one guide
- You want warm-up to stop automatically when a record breaks
- You want DNS and blacklists counted inside the score
Questions
Does Lemwarm check SPF and DKIM?
Its Essential plan includes a technical setup check, and its pause guide covers SPF, DKIM, DMARC and MX failures. It does not state how often it checks.
How often does Warmerly check?
Every six hours per mailbox, with a Re-check now option.
Does Warmerly pause a mailbox when SPF fails?
No. A failing record raises an alert and shows the fix. A mailbox is paused when its health score stays below 60 for two days, or when its login keeps failing.
What does Lemwarm do when DNS is wrong?
Its pause guide lists codes for each failure and pauses warm-up until you fix the record and restart. It gives the fix for each code and says DNS changes can take up to 72 hours to propagate.
Which blocklists does Warmerly check?
Domain lists Spamhaus DBL, SURBL, URIBL, NordSpam DBL, Spam Eating Monkey and s5h, and IP lists Spamhaus ZEN, SpamCop, Barracuda, PSBL, Mailspike, NordSpam, Spam Eating Monkey, Lashback UBL, DroneBL and GBUdb Truncate.
Sources
- Lemwarm blog: how lemwarm works
- lemlist help: why lemwarm pauses
- lemlist help: how to set up and use lemwarm
Lemwarm pages were read on 21 October 2026. Plans and wording change, so check the vendor's own page before you decide. Warmerly details come from the product as it runs today.
See it on your own mailbox.
Connect a mailbox. Warmerly runs alongside whatever you send from now, so you can compare before you move anything.
Free plan, no card. Paid plans: 7-day trial, first charge on day 8.