Skip to main content
DMARC aggregate reports are daily summaries that mailbox providers such as Google and Microsoft send about mail that claims to come from your domain: how much of it passed SPF and DKIM in alignment with your from address. InstantCampaign collects these reports for you and shows the result in the DMARC alignment column on the Deliverability page.

​
How it works

You don’t have to change your MX records or your mail hosting. Receivers send the reports to an address on our domain, and that address is unique to your domain:
You change exactly one DNS record, the _dmarc TXT record, which you’d be editing anyway to turn on DMARC reporting.
Normally a mailbox provider only sends reports to another domain if that domain explicitly agrees to receive them. We publish that authorization on our side for every customer domain, so there’s nothing extra for you to add.

​
Set it up

1

Add and verify your domain

Go to Settings → Domain Authentication and add your sending domain. See Sender identity and domain authentication.
2

Copy the DMARC record

Expand the domain and copy the DMARC Record value exactly as shown. It includes your domain’s unique rua= address.
3

Publish it at _dmarc

At your DNS provider, create or update the TXT record at _dmarc.<your-domain> with that value.
4

Wait for the first reports

Receivers usually send reports once a day, so it can take a day or two after you start sending for data to appear.

​
If you already have a DMARC record

A domain can only have one _dmarc TXT record. Don’t create a second one. Instead:
  • Keep your existing policy (p=) if it’s already quarantine or reject. The p=none in our suggested record is only a safe starting point.
  • Add our address to your rua= tag. You can list several mailboxes separated by commas, so an agency or monitoring tool can keep its own address alongside ours. For example:

​
Reading the DMARC alignment column

The hint under the percentage shows how many days in the window had a report. The percentage is averaged only over days that were reported. Open the domain’s row to see DMARC coverage: reported days out of the total.

​
When DMARC reporting blocks sending

If your _dmarc record stops pointing at our reporting address (for example, someone edits the record and removes our rua= mailbox), the Check DNS drift check flags it. The pre-send check then blocks campaign sends from that domain with a DMARC reporting finding. Your authentication is unaffected, but alignment can no longer be verified. Put our address back in the rua= tag, then click Check DNS on the Deliverability page.
Domains added before per-domain reporting addresses existed may still point rua= at a mailbox on your own domain. The drift check names the exact address to add. Copy the current DMARC Record from Domain Authentication and republish it.

​
Troubleshooting

Check that the TXT record is at _dmarc.<your-domain> (not at the root), that there’s only one DMARC record, and that the rua= address matches the one shown under Domain Authentication exactly. Also make sure you’ve actually sent mail from the domain to providers that send reports, such as Gmail or Outlook.
Look for services that send as your domain without being authenticated for it, such as a CRM, helpdesk or invoicing tool. Set up DKIM for each one on your domain, or send them from a subdomain.