Waiting for Data

The 'Waiting for data' item notifies that the indicated domain is visible in your account, but no DMARC reports have shown that any of the traffic with that domain in the From header has been reported as DKIM signed. (in alignment - see linked article below)

The most likely reasons you are seeing this are:

a) there is no reported DMARC traffic in the past 7 days - DMARC data is necessary to ascertain DKIM signing. This could occur either due to low/no message volume, or because DMARC data is not being directed to your account. You must have DMARC directed to dmarcian for at least a couple days, to have any chance of determining whether there is correct DKIM signing.

This will be the case if there is no volume bar present for the domain in the Domain Overview.

b) there is actually no DKIM signing on reported traffic (in other words, no DMARC-Capable traffic on the DKIM leg) - review entries via Detail Viewer. If any sending sources in use are capable of DKIM signing, that should be implemented. Work with each vendor to address that.

This may be the case if a volume bar is present for the domain in the Domain Overview.

c) there is DKIM signing taking place but not with the domain in the From header - review via Detail Viewer and see articles on Alignment to determine path forward.

This may be the case if a volume bar is present for the domain in the Domain Overview.

If you have recently made changes to authentication, traffic patterns, or reporting which you believe should alter the 'Waiting for Data' message being seen in the dmarcian UI, you may have to wait: the message will only update after the application sees DMARC reporting which verifies that correct signing has taken place. Also bear in mind that DMARC reporting is usually only for the prior complete day (24 hour period on the UTC day timeframe), and larger reporters can take up to 1/2 of a day or longer to generate and send those reports.