Short answer: When your domain has a DMARC record, Site AI Audit can report two more findings. “DMARC is in monitoring mode only (p=none)” is a warning: the record exists, but it tells receivers to deliver spoofed mail anyway. “DMARC reports are not collected” is a notice: the record has no rua address, so you cannot see who sends mail in your name. The way out is to add a report address, read the reports for a few weeks, fix your legitimate senders and then move the policy to quarantine and later to reject.
Where these findings come from
These two findings belong to the E-mail area and only appear when a DMARC record is found. If there is no record at all, the audit raises a different, critical finding, described in the article on how to fix a missing DMARC record. The two findings in this article describe the next stage: you have started, but you have not finished.
The audit reads the record published at _dmarc under your domain and looks at two tags. The p tag holds the policy, which can be none, quarantine or reject. The rua tag holds the address where receivers send aggregate reports. If p is none, you get the warning. If there is no rua, you get the notice. It is common to see both together, because a typical first record is “v=DMARC1; p=none” and nothing else.
What p=none really does
DMARC lets a domain owner say what receivers should do with a message that claims to come from the domain but fails authentication. There are three answers:
- none: do nothing special, just deliver the message as usual, and send me reports.
- quarantine: treat the message as suspicious, which usually means the spam folder.
- reject: refuse the message.
With p=none, a criminal who sends an e-mail in your name, with a fake From address, is still delivered, unless the receiver has its own rules. That is what the report means by “spoofed e-mails in your name are still delivered”. The record gives you information, but not protection. It is meant as a first step for a good reason: if you jump straight to reject while a legitimate system, such as your invoicing tool, is not set up properly, your own mail will be refused.
That is why the finding is a warning and not critical. A p=none record is much better than no record, and the report treats it as work in progress. It also explains why the advice in the report has two parts: check the reports first, then change the policy. The guide to DMARC policies and a safe rollout describes the whole process.
What the missing report address means
The rua tag tells receivers where to send aggregate reports. These are summaries, usually sent once a day by large mailbox providers, that list which servers sent mail claiming to be your domain, how many messages each sent and whether they passed SPF and DKIM. Without a rua address, the record may be valid, but you are flying blind: you cannot tell which services send as you, or whether someone is abusing your name.
The audit marks this as a notice and explains it in one sentence: without rua you cannot see who sends e-mail using your domain. The advice is to add an address such as rua=mailto:dmarc@yourdomain to the DMARC record. A complete starting record looks like this, with your own address in place of the example:
v=DMARC1; p=none; rua=mailto:[email protected]
Step 1: start collecting reports
- Create a mailbox or alias that is used only for DMARC reports, for example dmarc@yourdomain. Reports are machine-made and arrive in volume, so do not use your personal inbox.
- Add the rua tag to your existing DMARC record in DNS. Keep p=none for now.
- If the address is on another domain, that domain must give permission to receive your reports. The article on sending DMARC reports to another domain shows the record that is needed.
- Wait. Reports begin to arrive within a day or two. Give it two to four weeks, so that monthly senders and rare systems show up as well.
Step 2: read the reports
Raw reports are XML files, which are not pleasant to read by hand. Many people use a free or paid DMARC report tool that collects them and shows a table: which sending sources exist, how much mail each sends and whether it passes. The article on reading DMARC aggregate reports explains the fields, and the one on DMARC monitoring tools lists what to look for in a tool.
When you read the table, sort the sources into three groups:
- Legitimate and passing. Your mailbox provider, your newsletter service. Nothing to do.
- Legitimate but failing. A tool that sends for you but is not covered by SPF or has no DKIM signature set up. These must be fixed before you tighten the policy.
- Unknown. Sources that you do not recognise. Some will be forgotten tools, and some will be real abuse. Those are the ones that DMARC will block once you enforce the policy.
Step 3: fix your legitimate senders
For every legitimate source that fails, either add it to SPF or turn on DKIM signing with your domain in the service’s settings, and preferably both. Remember the limit of ten lookups in SPF, which is the subject of the article on the SPF lookup finding. DMARC passes when SPF or DKIM passes and aligns with the From domain, so one working method per sender is enough, but both is more robust. The guide to DMARC alignment explains what aligns.
Step 4: move to quarantine, then reject
- Switch to p=quarantine when the reports show that every legitimate source passes. A cautious way is to use the pct tag to apply the policy to a share of mail first, for example pct=25, and raise it over a few weeks.
- Watch the reports and your support inbox. If someone says that a message did not arrive, check whether that sender passed.
- Move to p=reject when quarantine has been quiet for a while. This is the setting that stops spoofed mail at the door.
- Check subdomains. The sp tag sets a separate policy for subdomains, as explained in the article about DMARC for subdomains.
The full process, with timing and traps, is covered in the article on moving from p=none to reject. For most small businesses, getting there takes weeks, not months.
Common mistakes
- Leaving p=none forever. Many domains publish the record, never read the reports and never move on. The finding will stay.
- Jumping to reject on day one. This can block your own invoices, newsletters and contact form mail.
- Sending reports to a personal inbox. A busy domain can receive hundreds of reports a day.
- Forgetting rarely used systems. A yearly mailing or a booking system that sends a few messages a month. The monitoring period should be long enough to see them.
- Editing the record without a check. A typo in the DMARC record can make it invalid. Always run the audit again afterwards.
Domains that send no mail at all
Not every domain sends e-mail. A parked domain, an old brand name or a domain used only for a landing page still can be used by criminals as a fake sender, because nobody watches it. For such a domain, you do not need a long monitoring period. Publish an SPF record that allows nobody, “v=spf1 -all”, and a DMARC record with p=reject. Because no legitimate mail exists, there is nothing to break. The audit’s advice for a domain without MX records, which is covered in the article on the no MX record finding, points in the same direction.
For domains that do send mail, remember that the policy is read for the exact domain in the From address. A subdomain can inherit your policy or have its own, so check the reports for subdomains as well.
A worked example
A dental clinic has the record “v=DMARC1; p=none” that its web agency added years ago. The audit shows a warning for monitoring mode and a notice for missing reports. The office manager adds a dmarc@ alias and the rua tag. After three weeks, a report tool shows five sources: the mailbox provider and the appointment reminder system pass, the newsletter service fails because DKIM was never turned on, and two unknown servers in another country send a few hundred messages. The clinic turns on DKIM in the newsletter service, moves the policy to quarantine with pct=50 and then, a month later, to reject. The next audit shows no DMARC findings.
To see how your own domain stands, run a Site AI Audit with a free account. The plans unlock the full report with the details of every finding.
Related reading
- DMARC Failure Reports (ruf): What They Show and Their Limits
- Site AI Audit Email Checks: SPF, DKIM, DMARC and MX
- SPF vs DKIM vs DMARC: What Each One Does and Why You Need All
- DMARC Passes but Email Still Goes to Spam: Why It Happens
The bottom line
A DMARC record with p=none and no reports is a start, not protection. Add a report address, read what arrives, fix your own senders and then move to quarantine and reject. Run the audit again to see both findings go away.
KKK
Is p=none bad?
It is a normal first step and better than no record, but it does not stop spoofed mail. That is why the audit shows a warning until you move on.
How long should I stay on p=none?
Long enough to see all your senders in the reports, usually two to four weeks, and longer if some systems send rarely.
Do I need the rua address?
You can publish a record without it, but you then cannot see who sends mail in your name. The audit marks that as a notice.
Can I use a free mailbox address for rua?
You can, but reports can be numerous. A dedicated address or a DMARC reporting tool keeps them manageable.
Will quarantine hide my own mail?
Only mail that fails both SPF and DKIM alignment, which is why you fix your legitimate senders first.



