What it means
Your DMARC record enforces a policy for the domain itself but sets sp=none for its subdomains. Mail claiming to come from any subdomain, real or invented, such as billing.example.com, is only monitored.
Why it matters
Attackers know this gap: a convincing made-up subdomain of your domain passes straight through when the subdomain policy is none. Unless a subdomain really needs a weaker policy while you set up its senders, it should be covered like the main domain.
How to fix it
- List the subdomains that send mail, for example from DMARC reports.
- Make sure each one has working SPF or DKIM.
- Remove
sp=noneso subdomains follow the main policy, or setsp=quarantineorsp=reject. - A subdomain that needs its own rules can publish its own
_dmarcrecord, which takes precedence. - Update the TXT record at
_dmarc; the DMARC builder can rebuild it.
Cloudflare
Open the domain, go to DNS then Records, and add or edit a TXT record with the name _dmarc. Cloudflare's own DMARC management page can write the record too.
Other DNS hosts
Add a TXT record whose name (host) is _dmarc. Some hosts want the full name, _dmarc.example.com; others add your domain for you, so type only _dmarc.
Check it worked
Run the DMARC checker or the full email check. DMARC records are read fresh once the old record's TTL has passed, usually within an hour. The DMARC section should show the new policy and the finding should be gone.