Skip to main content
Enterprise|Email Administrator / Security Engineer

DMARC Enforcement Rollout Planning

Plan, review, and validate staged email authentication changes

Plan, review, and validate staged email authentication changes. Follow the request examples below and review the observation limits before adding the workflow to your release or audit process.

Implementation example by the EdgeDNS team · Updated

The Challenge

Moving directly to a strict DMARC policy can disrupt legitimate senders whose authentication and alignment have not been verified.

The Workflow

Use fix-plan to prioritize findings, rollout-plan with target=dmarc_reject to produce a suggested sequence, and validate-fix with type=dmarc to recheck publication. Planning requires Pro access; validation requires Developer access. EdgeDNS does not publish records or process DMARC aggregate reports. Inventory legitimate senders, inspect your report-provider data, and approve each policy change before applying it through your DNS provider.

Endpoints Used

Combine these EdgeDNS endpoints to build this solution.

GET
/v1/reports/fix-planAPI reference

Fix Plan: Prioritized remediation action list from scan findings

GET
/v1/reports/rollout-planAPI reference

Rollout Plan: Phased timeline for hardening email-auth posture safely

GET
/v1/reports/validate-fixAPI reference

Validate Fix: Re-run a specific check and report whether the fix applied

What this workflow helps you do

Review prerequisites

Prioritize SPF, DKIM, and DMARC findings before increasing enforcement.

Approve a staged plan

Review suggested phases, monitoring signals, and rollback criteria with mail owners.

Recheck the published policy

Inspect fix_status and handle indeterminate or partial results before proceeding.

Code Example

Plan, review, and validate staged email authentication changes

javascript
const headers = { Authorization: 'Bearer YOUR_API_KEY' };

async function request(path, params) {
  const url = new URL(path, 'https://api.edgedns.dev');
  url.search = new URLSearchParams(params).toString();
  const response = await fetch(url, { headers });
  const result = await response.json();
  if (!response.ok) throw new Error(result.error?.message ?? 'Request failed');
  return result;
}

const domain = 'example.com';
const findings = await request('/v1/reports/fix-plan', { domain });
const plan = await request('/v1/reports/rollout-plan', { domain, target: 'dmarc_reject' });
console.log({ findings, plan });

// Review the plan, verify legitimate senders using your DMARC reports,
// and publish an approved change through your DNS provider first.
// Call this function separately after propagation and the relevant cache window.
async function validatePublishedDmarc() {
  return request('/v1/reports/validate-fix', { domain, type: 'dmarc' });
}

Learn More

Explore industry standards and best practices related to this use case.

Ready to build DMARC Enforcement Rollout Planning?

Get started with 200 free API requests per month. No credit card required.

Other Use Cases

DMARC Enforcement Rollout Planning | EdgeDNS