Your email security is a dozen DNS records. Anyone with the login can edit them.
SpoofKiller rescans the records your mail depends on every 6 hours and keeps a history of every change. Once a day it also looks for registered lookalikes of your name and checks that the domain itself is not about to expire.
DNSSEC, nameservers, CAA, MTA-STS, and TLS-RPT in one pass. Free.
Nobody attacks the record. They wait for someone to tidy it.
Reaching an enforced DMARC policy takes weeks of care. Undoing it takes one person, one afternoon, and one well-meant edit. A web agency migrates the site and replaces the zone. A contractor cannot get a newsletter delivered and sets the policy back to none “for now.” A registrar's interface helpfully collapses two TXT records into one.
None of these produces an error. DNS accepts whatever it is given. The mail keeps flowing, slightly less protected or slightly less delivered, until somebody notices a symptom and begins the archaeology. The first question is always the same: what changed, and when? Without a history, the answer is a shrug.
Two further risks sit outside your zone altogether. Someone can register a name one keystroke away from yours, which your DMARC policy does nothing about. And the registration itself can lapse, at which point the next owner inherits your mail and every record that authenticated it. Domain Impersonation Protection sets out which defense applies to which.
Three watches, three schedules.
DNS change detection, with a memory.
Each scan is compared with the last known state of every monitored record. A difference is stored as a change event: the record, the old value, the new value, and a severity chosen by what the change means. A policy moved from reject to none is critical. A policy strengthened is noted as information, because good news should not page anyone.
The DNSSEC chain is evaluated on each scan as signed, unsigned, or broken. Broken is the one that matters: validating resolvers will refuse to answer for the domain at all. If the lookup for a record fails outright, it is treated as unknown and not as a deletion.
- TXT _dmarcCriticalp=rejectp=none
- MX @High10 mx1.example.com10 mx.other-host.example
- TXT google._domainkeyMediumk=rsa; p=MIIBIjAN…k=rsa; p=MIIBIjQx…
What is compared on every scan
- DMARC
- Policy weakened or record deleted is critical. A lowered pct or a removed rua address is high.
- SPF
- Removal is high; any other edit is medium, with before and after.
- DKIM
- Each monitored selector. A removed key is high; a changed key is medium.
- MX
- Where your inbound mail goes. Changed is high; removed is critical.
- NS
- Your nameservers. Whoever controls these controls every other record.
- DS
- The DNSSEC link to your parent zone. Removal means DNSSEC was switched off.
- CAA
- Which certificate authorities may issue for the domain.
- MTA-STS, TLS-RPT, BIMI
- The transport-security and brand-indicator records, tracked for any change.
Lookalike discovery: the names next door.
Candidates are generated from your domain by the methods a forger would use: character substitutions such as rn for m, homoglyphs from other alphabets, omitted, repeated, and transposed letters, added hyphens and keywords, and alternate top-level domains.
Each candidate is checked for nameservers. A registered one is then checked for MX records, which mean it can send and receive email, and for a web address. Registration date is looked up for newly found names. The result is a 0 to 100 risk score with its evidence listed. A name that later gains MX records is raised again, since that is the moment a parked domain becomes a working one.
- risk 85/100
examp1e.com
character substitution · accepts email (MX)
- risk 50/100
exampel.com
transposition · no MX
- risk 35/100
example.co
alternate TLD · no MX
Resemblance is not intent. A match may belong to an unrelated business.
Expiration: the failure that needs no attacker.
The expiration date is read from the registry over RDAP. At 30 days out a finding is raised. It becomes high severity at 14 days and critical at 7. Renew the domain and the finding resolves itself at the next check.
It is a dull check. It is also the only one on this page that guards against losing the entire domain, which is why it runs every day for a date that changes once a year.
example.com expires in 21 days
Source: registry RDAP
- 30 daysMedium
- 14 daysHigh
- 7 daysCritical
A baseline, then a comparison, forever.
There is nothing to install and no access to grant. Every check reads public DNS and public registry data, the same information any receiving mail server can see. Setup is covered in Verifying Domain Ownership, and how findings reach you is in Alerts and Notifications.

- 1
Verify the domain
Change detection runs only for domains you have proven you own, with a TXT record. The first scan after that becomes the baseline.
- 2
Scan every 6 hours
The full set of records is fetched and compared with the stored snapshot. Anything different is logged with its previous and new value and given a severity.
- 3
Search for lookalikes daily
Candidate names are generated from your domain and checked in batches for nameservers. Registered ones are checked for MX and web records and scored.
- 4
Read the registry daily
The registration expiration date is read over RDAP. Inside 30 days, a finding is raised and its severity climbs as the date approaches.
What this cannot prevent.
It is a watch, not a wall. The distinction matters most on the day something happens.
It detects changes; it cannot stop them
SpoofKiller has no access to your DNS. It cannot block an edit or roll one back. It tells you what changed so that you can.
Up to 6 hours between scans
A record changed and changed back between two scans leaves no trace. Monitoring is scheduled, not continuous.
Lookalike discovery is detection only
It cannot prevent registration, and it cannot remove a domain. Takedowns go through the registrar and hosting provider.
It checks generated candidates, not every possible name
Candidates are checked in rotating daily batches within your plan's monthly allowance. A creative variant outside the generated set will not be found.
DKIM selectors must be known
Only selectors you have added or that match a common provider selector are tracked. See DKIM monitoring for why.
Expiration depends on the registry
Where a registry publishes no expiration data over RDAP, no date is shown and no warning is sent.
See what your DNS says about you today.
The free DNS security checker reads DNSSEC validation, nameservers, CAA, MTA-STS, and TLS-RPT for any domain in one pass. It is the same scan the monitor repeats every 6 hours, run once.
Free. No account. The lookup runs against live DNS.
Found a lookalike of your domain?
Send us your domain and the name you found. We will check whether it is registered, whether it can send mail, and tell you what your options are.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
Questions about domain security monitoring
Straight answers. If yours is not here, ask us and a person will reply.
Know what changed, and when.
DNS change alerts, lookalike discovery, and expiration warnings are included with Pro at $19 a month for 10 domains.
Keep reading
- DocsDomain VerificationHow DNS TXT verification works and why reports stay locked until it passes.Read
- GuideDMARC for Cloudflare DNSHow to add and verify email authentication records in Cloudflare DNS, including the proxy and CNAME pitfalls.Read
- GuideDomain Impersonation ProtectionExact-domain spoofing, lookalike domains, and display-name tricks: what each is and which defenses apply.Read
- SpoofKillerFree ToolsTwelve free tools for checking and building DMARC, SPF, DKIM, MX, BIMI, and DNS records. No signup for lookups.Read
- Free toolDNS Propagation CheckerQuery several major public DNS resolvers at once and see whether your new record has reached all of them.Read
- Free toolDNS Security CheckerCheck DNSSEC validation, nameservers, CAA, MTA-STS, and TLS-RPT for any domain in one pass.Read
