DMARC only watches while in test mode
Your DMARC record says p=quarantine and t=y. The t=y tag marks the policy as a test, so receivers that follow the current standard apply one level less: none instead of quarantine. At those receivers, mail pretending to be you is still delivered, the same as with p=none. Older receivers don't know t=y and already send failing mail to spam. If the record has a rua= address, reports still arrive.
On the result:
DMARC only watches
t=y marks the policy as a test, so receivers apply one level less: mail pretending to be you is still delivered.
RFC 9989 section 4.7, the DMARC standard since May 2026, defines t: "if the policy is "quarantine" and the value of the "t" tag is "y", a policy of "none" will be applied to failing messages". The tag "does not affect the generation of DMARC reports". It replaces pct=0 from the old standard (appendix A.6). Receivers that still follow RFC 7489 ignore t and apply quarantine as written.
Test mode is a sound step on the way to enforcement: the reports show which services would fail before their mail goes to spam at receivers that follow RFC 9989, so the result marks it "Watch", not "Fix".
Look it up
Details → on your result shows the record. To read it yourself, put your domain in place of example.com:
dig +short TXT _dmarc.example.com
Leave test mode
- Read the reports. If the record has no
rua=address, add one first: Connect DMARC reports says how. For each service that sends as you, check that SPF or DKIM passes for your domain, and fix the ones that fail. DMARC only watches lists the checks, including senders the reports may miss. - Check mail from each subdomain that sends, such as
news.example.com. The test covers subdomains too: they followsp=, orp=when the record has nosp=, andt=ysoftens both. Then removet=y, and anypct=tag: older receivers readpct=0the way newer ones readt=y. Receivers then send failing mail to spam, or refuse it wheresp=ornp=saysreject. - If your own mail is caught, change
p=quarantinetop=nonewhile you fix that service. Puttingt=yback helps only at receivers that follow RFC 9989. - Run the check again. This finding is gone.
- A few weeks later, if none of your own mail is caught, you can test
p=rejectwithp=reject; t=y. First make sure every service signs with DKIM for your domain: receivers that don't knowt=yrefuse failing mail at once. DMARC is in test mode explains that step.
Last updated .