Getting Started with SpoofKiller
Create an account, add a domain, verify it, and receive your first DMARC reports.
Updated
Setup has seven steps. Two of them happen at your DNS provider and one of them is waiting. Allow fifteen minutes of your own time and a day or two of the mailbox providers’. If you only want to look before committing to anything, the free domain health check runs the same DNS scan without an account.
1. Create an account
Register with an email address and confirm it using the link we send. Confirmation matters for more than tidiness: alert email is only sent to addresses that have been confirmed, so that security findings about your domain never go to an inbox nobody has claimed.
2. Set up your organization
Everything in SpoofKiller belongs to an organization: domains, reports, findings, members, API keys, and the subscription. You name one during onboarding and become its Organization Owner. New organizations start on the Free plan (1 domain, 7-day history); the other plans and their limits are on the pricing page. If you manage domains for clients, read Agency Workspaces, Clients, and Roles before adding them all to one organization.
3. Add a domain
Under Domains, enter the domain you send mail from, for example example.com. Owners and Administrators can add domains. A DNS scan runs immediately, before ownership is verified, because everything it reads is public. It checks:
- the DMARC record, its tags, and whether its reporting destinations are authorized;
- the SPF record, every include it pulls in, and the number of DNS lookups against the limit of ten;
- DKIM keys at the selectors you supply plus a list of common provider selectors (selectors cannot be enumerated from DNS, so an unlisted one will not be found until you add it);
- MX records, DNSSEC, nameservers and CAA, MTA-STS, TLS-RPT, and BIMI.
The result is a first Protection Score, marked as based on DNS only until reports arrive, and a list of configuration findings ordered by severity. We also email you the verification instructions for the next step.
4. Verify ownership
Until you prove the domain is yours, its reports, sender data, and alerts stay locked. Otherwise anyone could add a competitor’s domain and read its mail traffic. Verification is one TXT record:
Type: TXT
Host: _verification (full name: _verification.example.com)
Value: spoofkiller-verification=<your token>Copy the value from the domain’s setup page; the token is unique to the domain. Most DNS providers append the domain to the host for you, so enter only _verification. Then press Verify. When the record is found, scheduled monitoring starts and a baseline of your DNS records is stored for later change detection. The details, and the usual mistakes, are in Verifying Domain Ownership.
5. Add your reporting address
Each verified domain gets its own reporting address:
reports+<token>@reports.spoofkiller.comAdd it, as a mailto: URI, to the rua tag of the DMARC record at _dmarc. The setup page builds the exact record for you. If you already publish DMARC, it keeps your policy and your existing reporting addresses and appends ours; if you do not, it offers this starting record:
v=DMARC1; p=none; rua=mailto:reports+<token>@reports.spoofkiller.comEdit the existing record rather than adding a second one: two DMARC records at _dmarc count as none. After saving, press I have updated the record. A fresh scan looks for the address in DNS and marks the step done when it is there. Provider-by-provider instructions are in Sending DMARC Reports to SpoofKiller, and the DMARC record generator will build a record from scratch.
6. Wait for the first reports
Mailbox providers that send DMARC aggregate reports do so about once a day, covering the previous day’s mail. The first report therefore usually arrives within 24 to 48 hours of the address appearing in DNS. Nothing needs to be running on your side.
If you already have report files, from another service or from a mailbox you pointed rua at years ago, upload them under Reports and skip the wait. Accepted formats are XML, ZIP, and GZ, up to 15 MB per file and twenty files at a time. Files are queued and processed in the background; results normally appear within a minute, and a report that has already been received is recognized as a duplicate and not counted twice. To inspect a single file without an account, use the DMARC report analyzer.
7. Read the dashboard
Once reports are in, a domain’s page answers five questions, roughly in the order you should ask them.
| Question | Where to look | Reference |
|---|---|---|
| How well protected is the domain overall? | Protection Score, 0 to 100, with a breakdown by category and the fixes worth the most points | Protection Score |
| Is my legitimate mail authenticating? | DMARC pass rate, SPF and DKIM alignment, and the daily volume chart for the selected period | Alignment explained |
| Who is sending as me? | Sending Sources: each IP address, the provider it most likely belongs to, and a classification you set | Sending Sources |
| Is anything wrong right now? | Findings and the alert feed | Alerts and Notifications |
| Can I tighten my policy yet? | Enforcement readiness: green, yellow, or red, with the reasons | Enforcement Readiness |
The first useful thing to do is classify. Mark the sources you recognize as Approved and anything you are sure is not yours as Unauthorized. Readiness, risk levels, and detection all sharpen once SpoofKiller knows which senders are meant to be there.
Two cautions that apply to every number on the dashboard. Aggregate reports come from participating receivers and are not a complete record of all mail sent as your domain. And a DMARC failure is not proof of spoofing: forwarded mail and mailing lists fail too. The guide to understanding DMARC reports covers both.
