Everything we watch, so you can stop squinting at XML.
Your domain's email reputation lives in a handful of DNS records and a daily pile of machine-written reports. SpoofKiller reads both and tells you four things: who is sending as you, what looks wrong, what to do next, and when something changes.
Free scan of DMARC, SPF, DKIM, MX, DNSSEC, MTA-STS, and BIMI. No account.
First, the guest list.
Most companies cannot name every service that sends mail under their domain. There is the mail host, the invoicing tool, the newsletter platform, and the thing marketing signed up for in the spring. DMARC reports name them all. Nobody reads the reports, because they arrive as compressed XML.
DMARC analytics
Aggregate reports are parsed, deduplicated, and totaled into pass and fail counts by day, by source, and by reporting organization. You see SPF alignment and DKIM alignment separately, because a message needs only one of them to pass DMARC and it matters which.
Messages
5,168
DMARC pass
93.8%
Reporters
4
Sender identification, with a confidence score
An IP address alone never proves which application sent a message. SpoofKiller weighs reverse DNS, the network that announces the address, and the domains that authenticated, then names the likely provider and says how sure it is.
Illustrative values from documentation IP ranges.
One table, every sender
Each source gets a row: who it probably is, how much it sent, how much passed. You classify it as Approved, Unknown, Under Investigation, Unauthorized, or Ignored, and everything downstream uses that decision. Sender identification starts on the Starter plan; see pricing for the rest.
| Source | Confidence | Messages | DMARC pass | Status |
|---|---|---|---|---|
| Google Workspace192.0.2.14 | 96% | 4,210 | 100% | Approved |
| Invoicing service198.51.100.7 | 82% | 640 | 71% | Needs DKIM |
| Not identified203.0.113.45 | n/a | 318 | 0% | Unknown |
Then, the things that should not be there.
Two kinds of trouble. Somebody sending as you who is not you, and somebody on your own side quietly breaking a record. The second is considerably more embarrassing.
Spoofing detection rules
A DMARC failure is not proof of forgery. Forwarders and mailing lists fail too. The rules weigh the evidence for impersonation against the evidence for an innocent explanation and give you a confidence score with both lists attached.
Potential Domain Spoofing Detected
203.0.113.45 · provider not identified
Why it was flagged
- 318 messages failed both SPF and DKIM alignment
- The source had not been seen before
- It matches no recognized email provider
- No DKIM signature was present at all
Reasons for doubt
- No forwarding override was reported
- Seen by one reporting organization so far
DNS change monitoring, every 6 hours
DMARC, SPF, DKIM, MX, NS, DS, and CAA records are compared against the last known state. A policy that drops from reject to none is flagged critical. A failed lookup is never mistaken for a deleted record.
- TXT _dmarcCriticalp=rejectp=none
- MX @High10 mx1.example.com10 mx.other-host.example
- TXT google._domainkeyMediumk=rsa; p=MIIBIjAN…k=rsa; p=MIIBIjQx…
Blacklist monitoring, daily
Your approved and self-hosted sending IPs, and the domain itself, are checked against SpamCop and Spamhaus once a day. IP listings and domain listings are reported separately, since they have different causes and different cures.
How blacklist monitoring worksLookalike domain discovery, daily
Typosquats, homoglyphs, and TLD swaps of your name are generated and checked for registration. A match that also accepts email scores higher. This is detection only. Nobody can stop a stranger from registering a domain.
Spoofing versus lookalikesDomain expiration
A lapsed registration hands every record you publish to whoever buys the name next. Expiration dates are read over RDAP, where the registry publishes them, and warnings begin 30 days out.
- DNS record scan
- every 6 hours
- Blacklist check
- every 24 hours
- Lookalike discovery
- every 24 hours
- Registration expiration
- every 24 hours
Then, an opinion you can check.
Data without a verdict is homework. SpoofKiller gives two verdicts and shows the arithmetic behind each, so you can disagree with it intelligently.
Protection Score
One number from 0 to 100, built from seven weighted categories. The weights are published. A category with no data yet is left out and the score is scaled over the rest, so a new domain is not punished for reports that have not arrived.
- DMARC configuration20 pts
- DMARC enforcement20 pts
- SPF configuration15 pts
- DKIM authentication15 pts
- Authentication performance15 pts
- DNS security10 pts
- Monitoring coverage5 pts
Weights are the real ones. The fill levels are an example. A score of 100 does not mean immune.
How the score is calculatedEnforcement Readiness
Green, yellow, or red: should this domain move to a stricter policy? Green needs at least 14 days of reports before quarantine and 30 before reject, at least 98% of observed mail passing, and no legitimate sender failing. It recommends exactly one step, never a leap.
- Nowp=none
- Nextp=quarantine
- Laterp=reject
The route itself is explained in how to reach p=reject.
What green, yellow, and red meanThe reason most domains stall at p=none
Publishing p=none is easy and changes nothing. It asks receivers to report and otherwise carry on. The protection begins at quarantine and reject, and that is where people stop, because nobody wants to be the person who blocked payroll.
The fear is reasonable. The cure is evidence. Once every legitimate sender is identified and passing, the step up is uneventful. The three policies are a staircase, and the readiness status tells you when the next stair will hold. If you would rather start with the basics, what DMARC is takes five minutes.

Finally, the part where someone is told.
A finding nobody hears about is a diary entry. Alerts, reports, client workspaces, and an API get the right fact to the right person without burying them.
Alerts that do not repeat themselves
The same underlying problem updates one finding instead of creating forty. An email goes out when a finding is new, reopened, or has grown more severe. Each alert type can be sent immediately or held for a daily or weekly digest.
DMARC policy weakened
example.com · sent immediately
Newly observed sending IP
example.com · held for daily digest
Weekly Domain Health Report
PDF · scheduled, Mondays
PDF and CSV reports, on a schedule
Seven report types, from a Daily Security Summary to a Monthly Executive Report, a Suspicious Sender Report, and a DNS Change Report. Export as PDF or CSV, or schedule delivery by email. PDF and scheduled reports start on Pro.
Agency workspaces
Each client gets a separate workspace with its own domains, members, and reports. Five roles, from Organization Owner to Client Viewer. Reports carry your agency's name and contact details.
SpoofKiller for agenciesREST API
Read domains, health, sources, findings, and reports with an API key. Pro includes 2,000 requests a day; Agency includes 20,000.
API referenceSix features, each with its own page and its own caveats.
Every one of them ends with a list of what it cannot do. We find that customers who know the limits complain less than customers who discover them.
- DMARC MonitoringTurn raw DMARC aggregate reports into a plain account of who sends mail as your domain, what passes, what fails, and what to fix first.Read more
- SPF MonitoringScheduled SPF checks that count DNS lookups the way receivers do, walk every include, and warn you when a record breaks.Read more
- DKIM MonitoringMonitor DKIM selectors for missing, weak, or revoked keys, and see from real reports whether your signatures align.Read more
- Email Spoofing DetectionRules that separate likely impersonation from forwarding and misconfiguration, with a confidence score and the evidence behind it.Read more
- Email Blacklist MonitoringDaily checks of your sending IPs and domain against reputable blocklists, with alerts the day a listing appears.Read more
- Domain Security MonitoringScheduled monitoring of the DNS records your email depends on, with change history, lookalike-domain discovery, and expiration warnings.Read more
Not sure which of this you need?
Send us your domain. We will look at its DMARC, SPF, and DKIM records and tell you in plain English what is missing and which plan, if any, covers it.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
Questions about what it does and does not do
Straight answers. If yours is not here, ask us and a person will reply.
Find out who is sending mail in your name.
The check is free and takes about as long as reading this sentence. No account, no card, no sales call.
Keep reading
- GuideDMARC Alignment ExplainedWhy mail can pass SPF and DKIM and still fail DMARC, and what relaxed and strict alignment each require.Read
- GuideEmail Authentication Best PracticesThe habits that keep SPF, DKIM, and DMARC working after the day you set them up.Read
- GuideHow DMARC WorksFollow one email from send to inbox and see where SPF, DKIM, alignment, and policy each make their decision.Read
- Free toolDomain Health CheckerRun a full email security scan on any domain. DMARC, SPF, DKIM, MX, DNSSEC, MTA-STS, and BIMI, scored and explained. No signup.Read
- SpoofKillerKnowledge BasePlain-English guides to DMARC, SPF, DKIM, spoofing, and deliverability.Read
- SpoofKillerFree ToolsTwelve free tools for checking and building DMARC, SPF, DKIM, MX, BIMI, and DNS records. No signup for lookups.Read
