What we learned getting domains to enforcement
Patterns emerge when you watch many domains travel from p=none to p=reject. Here are the ones that shorten the journey, and the ones that stall it.
When we started, we assumed the hard part of DMARC was technical. It isn’t. The hard part is visibility and confidence: knowing what’s sending as you, and trusting that the next policy change won’t break anything.
Lesson 1: The blocker is almost never the policy
Teams don’t stall at p=none because changing a record is hard. They stall because they can’t tell which of the forty IPs in their reports are legitimate. Once every source has a name and an alignment status, the rest moves quickly.
Lesson 2: Shadow IT is everywhere
Nearly every domain we onboard turns up at least one sending service nobody remembered: an old marketing tool, a support desk, a contractor’s mailer. The source list is often the first time a security team sees their real email footprint.
The fastest path to p=reject isn’t a simpler DMARC. It’s a visible one.
Lesson 3: Quarantine is underused
The jump from monitoring to p=quarantine in test mode (t=y) is the safest move in the whole journey, and the most skipped. Mail is delivered as before while the reports show what quarantine would catch, so surprises turn up before they hit anyone’s inbox.
Lesson 4: Enforcement isn’t the finish line
New sources appear, providers rotate IPs, keys age out. The domains that stay protected are the ones that keep watching after they hit reject. That’s why alerting matters as much as the initial rollout.