The DNS records that decide whether client email lands in spam
SPF and DMARC don’t fail loudly. Nobody gets an error message when a record disappears — mail just starts landing in spam, or getting rejected outright, at receiving servers you’ll never see a log from. Lapsewatch checks both every day alongside the rest of your DNS, and treats a disappearing one exactly as seriously as a disappearing MX record — because it’s the same category of silent failure.
No signup. Real results in about four seconds.
Nothing bounces back to you
When a client’s SPF record vanishes — a registrar UI change, a DNS cleanup, a migration to a new email provider that forgot to update the old record — nothing breaks on your end. The domain still resolves, the website is still up, and the sender never gets an error. The mail just quietly stops arriving.
The first sign is usually a client asking “did you get my email? I never heard back” — days or weeks after the record disappeared, with no way to tell how much correspondence went missing in between.
What gets checked, and what doesn’t
This runs as part of the same daily DNS check already covering A, MX and NS records — nothing extra to configure.
SPF, checked daily
Read straight from the domain’s TXT records. If the SPF entry disappears while the rest of your DNS stays put, that’s flagged with the same urgency as a vanished MX record — not lumped in as “DNS changed” and easy to miss.
DMARC, watched for silent removal
Queried at the domain’s DMARC record daily. Losing it doesn’t stop mail from sending, but it removes the policy that tells receiving servers what to do with mail that fails authentication — quietly making spoofing easier.
DKIM, checked honestly
There’s no standard way to discover which DKIM selector a domain uses, so Lapsewatch tries a handful of common ones and says so plainly. Not found under those names never means DKIM is broken — only that it isn’t where we looked. It’s shown as a bonus signal, never something that can trigger an alert.
Email deliverability monitoring, answered
Do you test whether email actually gets delivered?
No — this checks whether the SPF and DMARC records exist and are well-formed, the same way the rest of Lapsewatch reads public DNS data. It won’t catch a delivery problem with no DNS cause, like a sending IP on a blocklist.
Why would a working SPF or DMARC record just disappear?
Almost always something unrelated: a registrar panel redesign, a bulk DNS cleanup that removed an “unused-looking” TXT record, or a switch to a new email provider where nobody thought to check the old SPF entry was still needed.
Do I need to set anything up for this?
No. It’s part of the same daily DNS check already running on every domain you add — nothing new to enable.