{
  "id": 20644676,
  "title": "Company Email Evidence: How to Budget SPF, DKIM, and DMARC Records",
  "url": "https://urgent.news/2026/11/18/company-email-evidence-how-to-budget-spf-dkim-and-dmarc-records",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T19:32:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ethanbrooks1647/company-email-evidence-how-to-budget-spf-dkim-and-dmarc-records-4glo"
  },
  "original_language": "en",
  "account": "When a developer-tools company migrates its email service, it incurs three main costs: publishing SPF, DKIM, and DMARC configuration records, verifying that the mail provider accepts them, and retaining evidence to explain any future delivery issues. In the example provided, checking 100 domains 24 times each generates 2,400 observations; a single check per domain results in 100 observations. These observations, rather than measured charges, dominate the workload before any actual email is sent. To address this, the recommended approach is to publish the SPF, DKIM, and DMARC records as TXT records in the DNS, start with a monitoring policy on DMARC, and verify the sending domain through the mail service after updating the DNS. While configuring the provider's MX records for incoming mail is a separate requirement, an MX change alone does not establish outbound authentication, and authentication does not guarantee inbox placement. The observed deliverability evidence should consist of the sending service's verification result along with a record of what was intended, such as password resets or OTP messages. It's important to distinguish between these pieces of information. A successful DNS write is an intermediate step, not the final result.",
  "summary": "The operating bill for SPF, DKIM, and DMARC records during a developer-tools company's email cutover has three parts: publishing the configuration, checking whether the mail provider accepts it, and keeping enough evidence to explain a later delivery complaint. In the illustrative workload below, 100 domains checked 24 times each produce 2,400 observations; one deliberate check per domain…",
  "key_points": [
    "Publishing SPF, DKIM, and DMARC records incurs three main costs.",
    "Monitoring policy on DMARC recommended for budgeting.",
    "Verification result and intended record distinction crucial."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}