Why DMARC reports stopped arriving

If reports were arriving and then stopped, or there's a multi-day gap where you expected data, work through these checks. A gap in reports doesn't always mean something is broken.

Check that your DNS record is still published

The most common cause of a sudden stop is that the DMARC record was removed or modified, either accidentally or as part of a DNS migration.

Use the DMARC check tool to look up your domain's current record. If the record is missing, it was deleted. If it looks different from what you remember, it was modified.

Recreate or restore the record at _dmarc.yourdomain.com. After propagation, reports should resume within 24-48 hours once receivers see the updated record and collect a full reporting period.

Check that your rua= address is still correct

If the DMARC record exists but your DMARCdrift address isn't in the rua= tag, reports are going elsewhere or nowhere. This happens if someone edited the record and removed the DMARCdrift address.

Verify the record contains your assigned address (shown in DMARCdrift's domain settings) in the correct format:

rua=mailto:d-abc123@in.dmarcdrift.com

If there are multiple rua= addresses, verify the comma-separated list doesn't have spaces and all addresses are intact.

Consider whether email volume dropped

Receivers only send DMARC aggregate reports for domains they received mail from during the reporting period. If your domain sent very little or no email during a period, some reporters won't generate a report for that period.

This is normal and expected for low-volume senders. A gap in reports on days with no outbound email isn't a misconfiguration.

Understand reporter behavior

Not all receivers send reports consistently. A few specific patterns:

Major reporters are the baseline. Google, Microsoft, Yahoo, and Apple send reports regularly for active domains. If you're not seeing reports from any of these, that's a meaningful signal.

Smaller reporters are intermittent. Regional mail providers, corporate mail systems, and smaller ISPs may send reports sporadically or only when they see significant volume from your domain.

Reports can arrive late. Most receivers send reports within 24-48 hours of the end of the reporting period, but some take longer. A gap of 48-72 hours from a specific reporter isn't always a problem.

Receivers may stop reporting for low-volume domains. Some reporters only generate reports for domains above a volume threshold. If your sending volume decreased significantly, you may see fewer reporters.

Check if a DNS migration caused the gap

If you recently moved your domain's DNS to a new provider, DMARC records at the new provider need to be created explicitly. A DNS migration that carries over most records may miss the _dmarc TXT record if it wasn't in the zone export. Verify the record exists at the new provider.

Check for a DNS propagation gap

After a DNS change, there's a propagation window where some resolvers still see the old record and others see the new one. During this window, some receivers may not find your rua= address and won't send reports. This is transient and resolves as the TTL expires across all resolvers. A gap of 24-48 hours after a DNS change is normal.

What to do if none of these apply

If your record is correct, your domain is actively sending email, and reports still aren't arriving after 72 hours from any major reporter, check whether your assigned rua= address is listed in DMARCdrift's domain settings and matches exactly what's in your DNS record. A mismatch as small as one character means reports are being sent to a nonexistent address.

See also: When reports start arriving: timing expectations for first reports. Troubleshooting setup: DNS detection and rua= formatting checks.