Your DMARC record is still marked as testing

What it means

The published policy carries t=y, which tells receivers you are experimenting and that they may treat example.com more gently than your policy asks. Enforcement you have announced is not enforcement anyone is obliged to apply.

How to fix it

Remove t=y from the record once you trust your reports. Leaving it in place is the quietest way to have a strict policy that does nothing.

Check your own domain

This page describes the condition. To find out whether your domain has it, run the RUA test or the full checkup, which examines every record at once.

Understand it properly

This page covers one condition. For the whole picture, The DMARC guide, including how reporting works, or start at the Health Library.

Where this comes from

We judge this against RFC 9989 section 4.7. Every finding on this site cites the specification behind it so you can check the work rather than take our word for it.

Other RUA conditions

• You are ready to turn enforcement on
• Some of this is forwarded mail, not an attack
• Somebody is sending as you, and it is being delivered
• Unauthenticated mail is getting past your policy
• Your policy stopped forged mail
• Your own mail is failing authentication