The reason so many domains sit on p=none forever is that moving past it feels risky, and the risk is real: anything sending as your domain that you have forgotten about starts failing the moment you enforce. An old invoicing tool, a CRM someone set up years ago, a server nobody owns any more.

Aggregate reports exist to remove that uncertainty. They tell you every source sending as your domain and whether each one aligns, which turns enforcement from a gamble into a checklist. A workable sequence:

  1. Publish p=none with a rua address

    No enforcement, full visibility. Give it a few weeks so weekly and monthly senders show up in the data.

  2. Fix every legitimate sender

    Get each one passing SPF or DKIM and aligning with your From domain. This is the actual work, and it is where the time goes.

  3. Move to quarantine, then reject

    Optionally with pct as a ramp. Watch the reports at each step rather than moving on a schedule.

Both underlying checks need to be sound first. Confirm the sending side with the SPF checker and the DKIM checker, and if you are diagnosing a specific message that failed, the header analyzer shows you the receiver's own verdict.