Choose a policy and where reports go, and get a DMARC record that meets the Gmail and Yahoo sender requirements — ready to paste in your DNS.
Policy for email that fails
Deliver as usual and only send reports. The safe first step.
Email that receives the daily reports.
Subdomain policy (sp)
DKIM alignment (adkim)
SPF alignment (aspf)
Use less than 100 to roll out quarantine or reject gradually.
Publish p=none with a rua address. Nothing changes for your email, and the reports show every service sending as your domain.
Once your real senders pass SPF or DKIM (check with the SPF generator), move to quarantine — spoofed mail goes to spam.
p=reject blocks anyone pretending to be your domain. It is the strongest protection against phishing with your name.
DMARC is a TXT record at _dmarc.yourdomain.com that tells receivers what to do when an email claiming to be from your domain fails SPF and DKIM: deliver it anyway (p=none), send it to spam (p=quarantine) or reject it (p=reject). It also asks them to send you reports.
Yes. Since 2024 Gmail and Yahoo require every bulk sender to publish a DMARC record (p=none is enough to start), together with SPF and DKIM. Without it, bulk email is throttled or rejected.
Start with p=none and a reporting address. Read the reports for a few weeks to make sure every service that sends for you passes SPF or DKIM, then move to p=quarantine and finally p=reject.
At your DNS provider, create a TXT record with the host _dmarc (some providers want _dmarc.yourdomain.com) and paste the generated value. A domain should have only one DMARC record.
rua is where receivers send daily aggregate reports (who sent email as your domain and whether it passed). ruf is for forensic reports about individual failures; few providers still send them. If the address is on another domain, that domain must authorize it.
Sendcorex sets up SPF, DKIM and DMARC for you, warms up your IPs automatically and watches the blocklists — free up to 3,000 emails a month.