Skip to content
SpoofKiller
Get started

Sending DMARC Reports to SpoofKiller

Add your unique reporting address to the rua tag and confirm that reports arrive.

Updated

A DMARC record can ask receiving mail servers to send a daily summary of the mail they saw claiming to be from your domain. The rua tag says where to send it. This page covers adding your SpoofKiller address to that tag, how the address is confirmed, and what the reports do and do not contain. The domain must be verified first; the reporting address is not issued before then.

Your reporting address

Every verified domain has its own address, shown on its setup page:

reports+<token>@reports.spoofkiller.com

The token ties incoming reports to one domain in one organization. Use the address for that domain only. A report is accepted when the domain it covers is the monitored domain or one of its subdomains; a report about some other domain sent to the address is rejected.

If you already have a DMARC record

Keep everything and append. The rua tag holds a comma-separated list of mailto: URIs, and receivers send to all of them. Given this record:

v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com; adkim=s

publish this one:

v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com,mailto:reports+<token>@reports.spoofkiller.com; adkim=s

Each address needs its own mailto: prefix, the separator is a comma, and the tag still ends with a semicolon. Your policy, alignment settings, and existing addresses are unchanged. If the record has no rua tag at all, add rua=mailto:reports+<token>@reports.spoofkiller.com as a new tag at the end. The setup page does this rewriting for you from the record it found in DNS and shows the result ready to copy.

Edit the record; do not add a second one

A domain must have exactly one DMARC record at _dmarc. Two records are treated by receivers as no record at all. Change the existing TXT value in place.

If you have no DMARC record

Publish this TXT record:

Type:   TXT
Host:   _dmarc                     (full name: _dmarc.example.com)
Value:  v=DMARC1; p=none; rua=mailto:reports+<token>@reports.spoofkiller.com

p=none is the monitoring policy. It asks receivers to send reports and leaves delivery exactly as it was. You tighten it later, when the reports show that your legitimate mail passes; enforcement readiness tells you when. For a record with other tags, use the DMARC record generator; for what each tag means, see How to Configure DMARC.

Steps by DNS provider

The record is the same everywhere; only the form differs. Menu names change from time to time, so treat these as directions rather than screenshots. In every case, if a TXT record named _dmarc already exists, edit it instead of adding one.

Cloudflare

  1. Select the domain, then open the DNS records page.
  2. Edit the TXT record named _dmarc, or add a record with Type TXT and Name _dmarc.
  3. Paste the full record into Content and save. TXT records are never proxied, so there is no proxy setting to worry about.

More detail is in the Cloudflare DNS guide.

GoDaddy

  1. Open the domain’s DNS management page.
  2. Edit the TXT record whose Name is _dmarc, or add a record with Type TXT and Name _dmarc.
  3. Paste the full record into Value and save.

Namecheap

  1. Open the domain’s Advanced DNS tab and find the host records.
  2. Edit the TXT record whose Host is _dmarc, or add a new TXT record with Host _dmarc.
  3. Paste the full record into Value and save.

Any other provider

  1. Find where DNS records for the domain are edited. If your nameservers point somewhere other than your registrar, that is where the record must go.
  2. Create or edit a TXT record. For the host, enter _dmarc; if the provider requires a full name, enter _dmarc.example.com. Do not enter the full name into a field that appends the domain, or you will publish _dmarc.example.com.example.com.
  3. Paste the record as the value, without adding quotation marks unless the provider’s instructions ask for them.
  4. Save, and leave the TTL at the default.

Afterward, the DMARC checker shows the record as receivers see it, and the DNS propagation checker shows whether the major public resolvers have picked it up.

External reporting authorization

Your reporting address is on a different domain from yours. DMARC (RFC 7489, section 7.1) anticipates this: before sending reports about example.com to an address at another domain, a receiver checks that the other domain has agreed to receive them. The agreement is a TXT record in the destination’s DNS:

<your-domain>._report._dmarc.reports.spoofkiller.com   TXT   "v=DMARC1"

SpoofKiller publishes this through a wildcard, *._report._dmarc.reports.spoofkiller.com, so it exists for every customer domain and there is nothing for you to add. To see it for yourself:

dig +short TXT example.com._report._dmarc.reports.spoofkiller.com
"v=DMARC1"

The SpoofKiller scan makes the same check for every external address in your rua tag and raises a finding when a destination has not authorized your domain, which is a common reason reports to a third party silently never arrive.

How the address is confirmed

SpoofKiller does not take your word, or its own, for the record having changed. Each DNS scan reads the published DMARC record, parses the rua tag, and looks for your domain’s exact reporting address in it. A scan runs when you press I have updated the record on the setup page and then every six hours.

  • When the address is found, the setup step is marked done and the status reads “Reporting address found in DNS.”
  • If a later scan retrieves the record and the address is no longer in it, the confirmation is withdrawn. A scan that could not retrieve the record changes nothing.
  • If reports had been arriving and none has been received for four days, a Missing DMARC reports alert is raised, with a reminder to check the tag. A domain that simply sent no mail produces the same silence and needs no action.

What reports contain, and what they do not

An aggregate report is an XML file from one receiving organization about one domain for one period, usually a day. SpoofKiller stores, per report:

In the reportNot in the report
The reporting organization, its contact address, the report ID, and the period coveredMessage subjects or bodies
The DMARC policy the receiver found published for your domainAttachments
For each sending IP address: the number of messages and what the receiver did with them (none, quarantine, reject)The addresses of individual senders or recipients (only domains appear)
Whether SPF and DKIM passed in alignment with your domain, and any reason the receiver overrode the policy, such as forwardingMessage IDs, timestamps of individual messages, or links
The From domain, the envelope domains, the domains that SPF and DKIM authenticated, and DKIM selectorsMail seen by receivers that do not send reports

That last row deserves emphasis. Reports come only from participating receivers, so they are a large sample, not a complete record of all mail sent as your domain. The field-by-field tour is in DMARC Aggregate Reports Explained.

Duplicates

Receivers sometimes send the same report twice, and people sometimes upload files that already arrived by email. A report is treated as a duplicate when it has the same reporting organization, report ID, and period as one already processed for the domain, or when its content is byte-for-byte identical. Duplicates are recorded as such and excluded from every total, chart, and source count.

Formats and limits

Reports arrive by email at your reporting address, by upload under Reports, or through the API. All three go through the same checks. The format is detected from the file’s content, not its name or declared type.

LimitValue
Accepted formatsXML, gzip (.gz), and zip
Maximum file size as received15 MB
Maximum size after decompression60 MB
Files inside one zip archive25; each XML file inside is processed as its own report
Records in one report100,000
SPF and DKIM results kept per record50 of each
Files per upload in the dashboard20

Archives nested inside archives are not opened. XML containing a DOCTYPE or ENTITY declaration is refused outright; no legitimate aggregate report needs one, and refusing them closes off a family of XML attacks. A file that cannot be processed raises a Report processing failure alert, and the original is kept for review.

Each plan also accepts a set number of report files per calendar month:

PlanReport files per month
Free300
Starter3,000
Pro15,000
Agency100,000

When the allowance is used up, further files are not accepted for the rest of the month and an Ingestion failure alert says so. An agency’s allowance is shared with its client workspaces. Plans are compared on the pricing page.

FAQ

Questions about reporting setup

Short answers. If yours is missing, write to us and a person will reply.

Ask a question