FAQ

I published my DMARC record but I'm not seeing any reports

If your inbound ingest address is in DNS but no aggregate reports are arriving, check propagation, exact record syntax, the right hostname, and registrar quirks.

2 min readLast updated 14 June 2026

Jump to section

1. Give it time
2. Confirm you're using your unique ingest address
3. Check the record is on the right hostname
4. Check the exact syntax
5. Registrar quirks
6. Cross-domain authorisation (different report domain)
Still nothing?

It's normal to wait a little before your first reports appear. Mailbox providers send DMARC aggregate (RUA) reports on their own schedule, so allow up to 24-48 hours after publishing before you worry. If reports still aren't showing on the Reports page, work through the checks below.

1. Give it time

Aggregate reports are generated roughly once a day by each receiver, so even a perfect record won't produce instant results. You need to be sending (or receiving) some mail to the wider world for receivers to have anything to report on.

2. Confirm you're using your unique ingest address

Every tenant has a unique inbound address of the form <token>@rua.blankitt.com, shown on the Settings page. Make sure the address in your DNS record matches it exactly - copy and paste it rather than retyping. A generic or mistyped address means reports never reach us.

3. Check the record is on the right hostname

The DMARC record must live at the _dmarc subdomain of the domain you want to monitor - not the bare domain.

Domain you monitor	Record hostname
`example.com`	`_dmarc.example.com`
`mail.example.com`	`_dmarc.mail.example.com`

A common mistake is publishing the TXT record on example.com itself, or on the wrong subdomain. Some registrars only ask for the host portion (_dmarc) and append the domain automatically - others want the full _dmarc.example.com. Putting the full hostname when the registrar already appends the domain produces _dmarc.example.com.example.com, which won't be found.

4. Check the exact syntax

The record must be a single TXT record beginning with v=DMARC1:

v=DMARC1; p=none; rua=mailto:<token>@rua.blankitt.com

Watch out for:

mailto: prefix - the rua= value must be mailto:<token>@rua.blankitt.com, not just the address.
Smart quotes - curly quotes pasted from a document break the record. Use plain text.
Tag order - v=DMARC1 must come first, followed by p=.
Duplicate records - only one _dmarc TXT record may exist. Two records is treated as no valid policy.

You can sanity-check any domain with our free public checker at https://blankitt.com/dmarc/check.

5. Registrar quirks

Some DNS hosts auto-wrap or split long TXT values, strip the mailto: colon, or require the value in quotes. After saving, re-open the record in your registrar's control panel and confirm it reads back exactly as you entered it.

6. Cross-domain authorisation (different report domain)

Because your reports go to rua.blankitt.com - a different domain from yours - the receiving side already has the standard authorisation in place on our end, so you don't need to add anything extra. Just publish the rua=mailto: target as shown above.

Still nothing?

If 48 hours have passed and the record verifies cleanly, you can also import reports that may already be sitting in a mailbox by connecting Microsoft 365 or Google Workspace under Settings -> Mailbox sync, or manually upload report files (.xml/.gz/.zip) on the Reports page.