← Back to Check a domain

DMARC is in test mode

Your domain is protected, but forged mail still reaches the spam folder, where a reader can find it. Your DMARC record says p=reject with t=y, which asks receivers that follow the current standard to treat reject as a test: they send failing mail to spam instead of refusing it.

On the result:

DMARC is in test mode
t=y marks p=reject as a test, so receivers send mail pretending to be you to spam instead of refusing it.

RFC 9989 section 4.7, the DMARC standard since May 2026, defines t: "if the policy is "reject" and the value of the "t" tag is "y", a policy of "quarantine" will be applied to failing messages". Receivers that still follow RFC 7489 don't know t and refuse failing mail as p=reject asks.

The test softens reject only at receivers that follow RFC 9989. Older ones already refuse failing mail, so every service that sends as you needs DKIM now, not only when you leave test mode (step 2).

Look it up

Details → on your result shows the record. To read it yourself, run dig +short TXT _dmarc.example.com with your domain in place of example.com.

Leave test mode

  1. Read the reports. If the record has no rua= address, add one first: Connect DMARC reports says how. Check that every service that sends as you passes DMARC, and fix any that don't. A service that sends rarely, such as invoicing, may not show up for weeks.
  2. Check that every service signs with DKIM for your domain, not only passes SPF. Forwarded mail loses its SPF pass, and with p=reject it is then refused. RFC 9989 section 8: domain owners "MUST NOT rely solely on SPF for a DMARC pass if the DMARC policy for the Author Domain is "p=reject"". DKIM says how to turn it on. Until every service signs, change p=reject; t=y to p=quarantine, because older receivers already refuse. Lower sp=reject and np=reject the same way if the record has them. Remove t=y in the same change, or newer receivers drop to none.
  3. If people at your domain post to mailing lists, read p=reject and mailing lists first: RFC 9989 advises those domains against p=reject, and a list can unsubscribe them when their mail is refused. Those domains change p=reject to p=quarantine, as in step 2, and stay there.
  4. 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. If a subdomain's mail fails, fix that service before step 5.
  5. Remove t=y, and any pct= tag: older receivers read pct=0 the way newer ones read t=y. If you lowered the policy in step 2 and step 3 doesn't apply to you, set p=reject again once every service signs, and sp= and np= if you lowered them.
  6. Run the check again. This finding is gone.

If your own mail is refused after that, change p=reject to p=quarantine while you fix the service. Putting t=y back helps only at receivers that follow RFC 9989.

Last updated .