# 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](https://www.rfc-editor.org/rfc/rfc9989.html#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](https://www.rfc-editor.org/rfc/rfc9989.html#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

1. Read the reports. If the record has no `rua=` address, add one first: [Connect DMARC reports](/docs/connect-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](/docs/findings/dmarc-monitoring-only/#moving-to-enforcement) lists the checks, including senders the reports may miss.
2. Check mail from each subdomain that sends, such as `news.example.com`. The test covers subdomains too: they follow `sp=`, or `p=` when the record has no `sp=`, and `t=y` softens both. Then remove `t=y`, and any `pct=` tag: older receivers read `pct=0` the way newer ones read `t=y`. Receivers then send failing mail to spam, or refuse it where `sp=` or `np=` says `reject`.
3. If your own mail is caught, change `p=quarantine` to `p=none` while you fix that service. Putting `t=y` back helps only at receivers that follow RFC 9989.
4. Run the check again. This finding is gone.
5. A few weeks later, if none of your own mail is caught, you can test `p=reject` with `p=reject; t=y`. First make sure every service signs with DKIM for your domain: receivers that don't know `t=y` refuse failing mail at once. [DMARC is in test mode](/docs/findings/dmarc-testing-reject/) explains that step.
