yourproduct.com · 12 November 2026
Your record exists, but it tells inbox providers to take no action on email that fails authentication. Your policy does not block email that fakes your domain.
Without a rua address you can't see who is sending email as your domain, which makes it risky to move to a stricter policy.
Gmail, Yahoo and Microsoft now reject or filter email from senders without proper SPF, DKIM and DMARC. For your business that means order confirmations, password resets, invoices and welcome emails that quietly never reach the inbox. A weak DMARC policy also lets anyone send phishing email that looks like it comes from your domain.
Most fixes take one to two weeks and need no downtime: list every tool that sends email as your domain, align SPF and DKIM for each one, then move DMARC from monitoring to enforcement in steps while watching the reports.
| SPF | v=spf1 include:_spf.google.com include:mail.zendesk.com -all |
| SPF lookups | 2 of 10 allowed |
| DMARC | v=DMARC1; p=none |
| DKIM | s1 |
| Sending tools | Google Workspace, Zendesk |