---
title: "DMARC Compliance: Why a Published Record Is Just the Start | DMARC Report"
description: "Learn why DMARC publication does not guarantee enforcement and how organizations can move from monitoring-only policies to stronger email authentication."
image: "https://dmarcreport.com/og/blog/dmarc-compliance-why-a-published-record-is-just-the-start.png"
canonical: "https://dmarcreport.com/blog/dmarc-compliance-why-a-published-record-is-just-the-start/"
---

Quick Answer

It occurs when organizations publish a DMARC record but remain at p=none without progressing toward enforcement. Effective DMARC protection requires monitoring reports, identifying legitimate senders, fixing authentication alignment, and moving toward quarantine or reject policies.

Share 

[ ](https://www.linkedin.com/sharing/share-offsite/?url=undefined%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=DMARC%20Compliance%3A%20Why%20a%20Published%20Record%20Is%20Just%20the%20Start&url=undefined%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=undefined%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F "Share on Facebook") [ ](https://reddit.com/submit?url=undefined%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F&title=DMARC%20Compliance%3A%20Why%20a%20Published%20Record%20Is%20Just%20the%20Start "Share on Reddit") [ ](mailto:?subject=DMARC%20Compliance%3A%20Why%20a%20Published%20Record%20Is%20Just%20the%20Start&body=Check out this article: undefined%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F "Share via Email") 

![DMARC Compliance and Enforcement Challenges](https://media.mailhop.org/dmarcreport/dmarc-record-6408-1794828515559.jpg) 

## Try Our Free DMARC Checker

Validate your DMARC policy, check alignment settings, and verify reporting configuration.

[ Check DMARC Record → ](/tools/dmarc-checker/) 

## Executive takeaway

Publishing DMARC does not necessarily request enforcement against domain spoofing. In one February 2026 scan, 30.4% of domains published DMARC, but only 12.8% requested **quarantine or rejection**. Monitoring-only policies can help teams investigate legitimate senders before enforcing. They become a compliance trap when publication counts as completion and nobody owns the next step. _Measure publication, enforcement, and reporting separately. Inventory senders, repair alignment, and introduce stricter policies through controlled changes._ Treat enforcement as a maintained control, not proof that every spoofed message will be blocked.

## The record is there. The enforcement may not be.

Publishing a DMARC record does not necessarily ask receiving [mail servers](https://www.cloudflare.com/learning/email-security/what-is-a-mail-server/) to restrict messages that fail authentication. Record presence and enforcement are different milestones, although a compliance checkbox can treat them as equivalent.

[DMARCguard’s February 2026 scan](https://dmarcguard.io/research/email-authentication/) illustrates that distinction across **5,499,028 domains**. It found DMARC records on 30.4% of domains, while only 12.8% published enforcement policies. Both percentages use the full scanned population as their denominator.

Among **DMARC adopters**, approximately 42% requested enforcement: 12.8 divided by 30.4, multiplied by 100\. This calculation uses rounded percentages, not exact underlying counts. Most adopters in this sample therefore did not request enforcement.

These findings do not establish that most organizations publish DMARC. Domains are not organizations, and the sample includes properties beyond active email operations. As [DMARC Report’s comparison of adoption measurements](https://dmarcreport.com/blog/why-2026-email-authentication-numbers-don-t-agree/) explains, population selection changes the interpretation.

A policy ladder makes the distinction clearer than an on-or-off indicator:

- **No record:** The domain publishes no DMARC policy.
- `p=none`: The owner requests no DMARC-specific disposition for failing messages.
- `p=quarantine`: The owner asks receivers to treat failing messages as suspicious, such as placing them in spam.
- `p=reject`: The owner asks receivers to reject failing messages.

These settings describe requested handling, not guaranteed outcomes. A `p=none` policy does not disable other spam or security checks. An enforcement policy does not prove that every receiver rejected every failing message.

Monitoring can support deployment, but publishing `p=none` alone does not establish a monitoring process. Reporting, review, and responsibility must accompany it to inform the next policy decision.

The **February snapshot** establishes an enforcement gap, not a growth rate or an explanation for that gap. _This paper examines what the measurements show, why organizations may stop at publication, and how they can progress safely._ The central question is not simply whether DMARC exists, but whether someone maintains it as an operational control.

![What Is Dmarc 3784](https://media.mailhop.org/dmarcreport/what-is-dmarc-3784-1794828581395.jpg)

Source: DMARCguard, 2026 Tranco domain scan

## What SPF, DKIM, and DMARC actually do

SPF, DKIM, and DMARC answer related but different questions about an email’s identity. Their differences explain why publishing a **DMARC record** does not automatically prevent impersonation.

Sender Policy Framework (SPF) authorizes servers to send email for a domain. Receivers check the sending server against that authorization. The domain checked by SPF is not necessarily the domain displayed in the message’s From field.

DomainKeys Identified Mail (DKIM) adds a [cryptographic signature](https://myequals.org/blog/cryptographic-signatures-explained/) that receivers can verify. It connects a message to a signing domain and helps detect changes to signed content. DMARC Report’s authentication overview describes SPF and DKIM as the authentication mechanisms on which DMARC builds.

Neither mechanism alone necessarily authenticates the identity displayed to the reader. A message can authenticate using one domain while displaying another. DMARC addresses that gap through alignment: the authenticated domain must match the visible From domain under the applicable rules.

_DMARC stands for Domain-based Message Authentication, Reporting and Conformance. One passing, aligned SPF or DKIM result is enough to pass DMARC_. Both mechanisms need not pass for every message. The supplied technical account distinguishes strict alignment from relaxed alignment, which **permits domains** sharing the same organizational domain.

For example, a message with a passing, aligned [DKIM signature](https://docs.mapp.com/docs/dkim-signature) can pass DMARC even if SPF fails. Conversely, successful authentication using only unrelated domains does not satisfy alignment.

The p tag specifies requested handling when DMARC fails. [Mailgun’s authentication guidance](https://www.mailgun.com/state-of-email-deliverability/chapter/email-authentication-requirements/) describes the three policies introduced above: _no special disposition, quarantine, or rejection. Receiving systems make the final handling decision; published policy is not evidence of actual disposition._

Reporting is a separate function. The rua tag specifies destinations for **aggregate reports**, which summarize authentication outcomes across messages. [DMARC Report’s adoption analysis](https://dmarcreport.com/blog/the-dmarc-adoption-2026-domains-records-only-9-percent-protected/) distinguishes reporting configuration from enforcement because they provide different capabilities.

Calling `p=none` “monitoring mode” therefore requires qualification. Useful monitoring requires reports to arrive and someone to interpret them. Those reports reflect participating receivers’ observations, not a complete census of every message.

Finally, **DMARC authenticates** a domain relationship; it does not establish a message’s truthfulness or safety. It is not a universal [phishing filter](https://www.malwarebytes.com/blog/news/2025/11/phishing-emails-disguised-as-spam-filter-alerts-are-stealing-logins). Keeping that boundary explicit avoids promising protection beyond what the mechanism checks.

## Why the adoption numbers disagree

Adoption percentages depend on which domains researchers count. _A broad ranked-domain scan and a study of mail-receiving domains measure different populations._ Their results can differ substantially without contradicting each other.

Before comparing headlines, inspect four features:

- **Population:** Are researchers counting ranked websites, mail-receiving domains, or selected companies?
- **Denominator:** Does the percentage cover all sampled domains, only resolvable domains, or only DMARC adopters?
- **Observation date:** When were configurations measured, rather than when was the report published?
- **Enforcement definition:** Does the measure include quarantine, rejection, and limited rollout, or only full rejection?

[DMARCguard’s February 2026 Tranco scan](https://dmarcguard.io/research/email-authentication/) provides the broadest sample among the three measurements considered here. Its 5,499,028 [domains included parked](https://www.urllo.com/resources/learn/what-are-parked-domains), brochure-only, and infrastructure properties. _The reported 30.4% publication and 12.8% enforcement rates describe that full sample, not just domains known to send mail._

[SpamCipher’s 2026 measurement](https://spamcipher.com/insights/email-authentication-spf-dmarc-2026) reports 47.2% DMARC publication among resolvable top-million domains. Its ranking scope and **DNS-resolution** filter differ from DMARCguard’s. The gap between their percentages therefore does not establish growth or disagreement about a universal adoption rate.

[Shipmail’s 2026 study](https://shipmail.to/research/email-authentication-adoption/2026) selects 10,000 mail-receiving domains and reports 82.9% publication and 60.9% enforcement. Those results describe a more mail-focused population, not the internet as a whole. Receiving mail also does not establish that a domain actively sends mail.

A domain percentage differs from an organization percentage, as DMARC Report’s comparison emphasizes. Neither directly measures the share of email traffic protected. Without comparable sampling, we cannot isolate how much each selection rule contributes to the observed differences.

Enforcement definitions create another source of variation. Counting quarantine alongside rejection answers a broader question than counting only full rejection. Researchers’ treatment of limited rollout and **subdomain policies** also matters when comparing results.

Trend claims require observations over time, not a line connecting unrelated surveys. The [longitudinal account attributed to SpamCipher](https://spamcipher.com/insights/email-authentication-spf-dmarc-2026) supplies these publication rates:

- **Historical baseline before February 2024:** approximately 25–27%.
- **July 2024 comparison:** 34.7%.
- **July 2026 snapshot:** 45.9%.

The separate 47.2% headline should not replace that series’ July endpoint. _The supplied account also reports that roughly half of adopters enforced in 2023, remaining near half through 2026._ Publication growth therefore does not demonstrate an increasing enforcement share among adopters.

The reported acceleration followed the February 2024 bulk-sender requirements, but timing alone does not establish causation. The supplied account does not isolate those requirements from other influences, and its methods were not independently inspected. Read the studies as **complementary measurements**, while reserving trend claims for genuinely comparable observations.

![Dmarc Lookup 3788](https://media.mailhop.org/dmarcreport/dmarc-lookup-3788-1794828621407.jpg)

Key headline percentages show DMARC publication outpacing enforcement across broad and selected populations. Method: Values combine DMARCguard’s adoption and enforcement rates across the Tranco 5.5M sample with EasyDMARC’s global adoption and enforcement policy shares for the top 1.8M domains; figures are used to illustrate how enforcement trails publication.

## How `p=none` becomes a permanent stopping point

Most valid records in EasyDMARC’s reported 2026 dataset did not request enforcement. [Duocircle’s secondary summary](https://www.duocircle.com/blog/dmarc-spf-dkim-2026-email-authentication-regulatory-requirement-best-practice/) reports 937,931 valid records across the top **1.8 million domains**. Of these, 525,996 used `p=none`, while 411,935 enforced. Calculated from those counts, approximately 56.1% were non-enforcing and 43.9% requested quarantine or rejection.

That majority applies to valid records in this dataset, not all domains or businesses. The counts also cannot establish how long individual domains remained at `p=none`. They demonstrate an enforcement gap, not that every non-enforcing deployment has stalled.

Monitoring has a legitimate discovery role before organizations tighten their policies. With reporting configured, `p=none` provides authentication visibility without requesting quarantine or rejection. [DMARC Report’s adoption synthesis](https://dmarcreport.com/blog/the-dmarc-adoption-2026-domains-records-only-9-percent-protected/) emphasizes this distinction between publication and enforcement.

A deliberate staging period lets teams investigate legitimate mail that stricter handling could affect. _Its value depends on whether monitoring produces decisions: identifying authorized senders, investigating failures, and correcting configurations._ Temporary non-enforcement can therefore represent risk management rather than implementation failure.

Reporting-only and no-reporting policies are different operational states. [Valimail’s 2026 report preview](https://www.valimail.com/dmarc-report-2026-preview/) separates `p=none` with aggregate reporting from `p=none` without it. Neither requests enforcement, but only the former establishes that **DMARC reporting channel**. Other monitoring tools may exist in either case.

Even a reporting destination does not prove that anyone reviews the data. [DNS settings](https://www.ntchosting.com/encyclopedia/dns/settings/) cannot reveal whether teams investigate failures, assign repairs, or assess enforcement readiness. Equating reporting configuration with **active monitoring** would repeat the mistake of equating publication with protection.

The compliance trap begins when satisfying the initial requirement removes the incentive to continue. If success means “record published,” monitoring may persist without an accountable owner or decision point. This is a governance interpretation, not a measured explanation for every non-enforcing domain.

The useful distinction is therefore purposeful monitoring versus indefinite monitoring. Purposeful monitoring has an owner, unresolved questions, and explicit decision criteria. _Legitimate-mail uncertainty may justify waiting, but that uncertainty should remain a documented, reviewed risk._

![Dmarc Generator 6377](https://media.mailhop.org/dmarcreport/dmarc-generator-6377-1794828720085.jpg)

Among domains with valid DMARC records in EasyDMARC’s 2026 dataset, a majority publish `p=none` instead of an enforcing policy. Method: Counts of DMARC records at `p=none` (525,996) and enforcement policies (411,935) among 937,931 adopters are taken from Duocircle’s summary of EasyDMARC’s report; percentages are calculated to show the relative weight of monitoring-only versus enforcing configurations.

## Big brands enforce more, but they are not the whole internet

**Large-company benchmarks** show stronger enforcement than broad domain scans, but they measure a different population. Enterprise adoption is not an estimate of internet-wide protection.

[SimpleDMARC’s 2026 Fortune Global 500 study](https://simpledmarc.com/research/state-of-email-authentication-2026) reports DMARC publication at 397 companies, or 79.4% of the cohort. It finds 315 companies, or 63%, requesting quarantine or rejection. 48% of all 500 companies publish `p=reject`, not merely 48% of those enforcing.

The broad-domain baseline differs sharply. [DMARCguard’s Tranco scan](https://dmarcguard.io/research/email-authentication/) reports 30.4% publication and 12.8% enforcement. The calculated enforcement gap is 50.2 percentage points, but it compares different populations and units of analysis.

A company-level result does not establish coverage of every domain that company owns. Nor does either study measure the share of traffic protected or [impersonation attempts](https://www.bbc.com/news/articles/c394v84z9lko) stopped. The comparison demonstrates different published policy distributions, not a quantified difference in **security outcomes**.

The enterprise cohort also contains substantial non-enforcement. SimpleDMARC reports 16.4% at `p=none` and 20.6% without DMARC, representing 82 and 103 companies respectively. Together, these categories account for 37% of the cohort without a published enforcement policy.

![Dmarc Report 6798](https://media.mailhop.org/dmarcreport/dmarc-report-6798-1794828775312.jpg)

Source: SimpleDMARC, 2026 Fortune Global 500 study

Those categories should not be treated as operationally identical. A `p=none` record may support managed monitoring, although its presence does not establish review. An absent record indicates non-adoption in the measurement, not the absence of every other **security control**.

A separate enterprise benchmark must remain separate. [Duocircle’s summary of EasyDMARC’s findings](https://www.duocircle.com/blog/dmarc-spf-dkim-2026-email-authentication-regulatory-requirement-best-practice/) reports 95% adoption and 62.7% at `p=reject` for the Fortune 500, not the Fortune Global 500\. These figures cannot replace SimpleDMARC’s results or establish improvement over them.

_Resources, regulation, and brand exposure offer plausible explanations for stronger enterprise enforcement._ Dedicated staff may ease sender coordination, while compliance obligations may increase its priority. _However, the snapshots do not isolate these factors._ Industry composition and domain selection offer alternative explanations.

**Stricter configurations** also do not establish disruption-free deployment. The supplied studies contain no delivery measurements showing whether every legitimate sender passed authentication. Enterprise benchmarks support treating enforcement as an achievable objective, but organizations still need evidence about their own [legitimate-mail](https://www.usatoday.com/story/tech/2021/08/23/gmail-spam-filter-email-inbox-google/8242847002/) performance.

![Dmarc Check 3977](https://media.mailhop.org/dmarcreport/dmarc-check-3977-1794828859568.jpg)

Contrasts DMARC adoption and enforcement shares between broad ranked-domain samples, Fortune Global 500 companies, and global protection dashboards. Method: Values are taken from DMARCguard’s Tranco scan for broad domains, SimpleDMARC’s Fortune Global 500 study for large enterprises, and DmarcDkim’s global protection snapshot as summarized by DMARC Report; the share with no effective protection in the global snapshot is used to highlight `p=none` and absent records.

## Why the minimum requirement becomes the goal

Meeting a sender requirement is not the same as completing an enforcement project. Gmail and Yahoo’s 2024 bulk-sender requirements accepted `p=none` as the minimum **DMARC policy**, according to [Mailgun’s authentication discussion](https://www.mailgun.com/state-of-email-deliverability/chapter/email-authentication-requirements/). These were mailbox-provider requirements, not legislation. The minimum did not require senders to request quarantine or rejection.

That entry point reduces the immediate risk of DMARC-driven disruption during initial deployment. With reporting configured, teams can investigate failures before introducing stricter handling. The incentive mismatch arises when this starting point becomes the organization’s definition of completion.

Mailgun’s [survey findings](https://www.mailgun.com/state-of-email-deliverability/chapter/email-authentication-requirements/) provide evidence about stated intentions: more than 61% of surveyed `p=none` users would tighten enforcement only if required. This suggests that external requirements influence willingness to progress. _It does not establish subsequent behavior, and the supplied summary lacks sampling details and a clear fieldwork date._

Delivery concerns offer a credible reason for caution. DMARC Report’s deliverability discussion describes how misalignment can make legitimate third-party mail fail DMARC. A service may be authorized by the business while its authentication fails to align with the visible From domain.

Procurement checklists and competing priorities offer additional explanations, although their causal effects are not measured here. If procurement asks only whether DMARC exists, publication can satisfy the requirement without demonstrating enforcement. _If nobody owns the remaining work, other projects may displace it after the deadline passes._

These incentives can conflict without anyone deliberately choosing permanent non-enforcement. Security teams may favor stricter policies while business teams seek assurance that legitimate messages will survive. The task is to resolve that uncertainty through evidence and accountable decisions, not merely edit a **DNS tag**.

Market growth does not show whether organizations are resolving it. The [DMARC market report](https://dataintelo.com/report/dmarc-market) discusses commercial expansion, but spending and revenue do not measure policy strength. Buying monitoring software may support progress; a purchase does not demonstrate completed enforcement.

The management question should shift from presence to ownership. Who owns safe progression? Which delivery risks remain unresolved? Who can authorize the work? Those questions make the minimum requirement a starting commitment rather than a finished control.

## The hard part is finding every legitimate sender

Changing a policy is easier than establishing whether every legitimate sender is ready. An inventory must extend beyond employee mailboxes to third-party services, marketing platforms, and [agency-managed campaigns](https://revenuebase.ai/companies/campaign-management-services/united-states). Each introduces configuration dependencies and business owners who may sit outside IT.

Legitimate mail can fail DMARC even when a provider authenticates its own infrastructure successfully. DMARC Report’s deliverability overview identifies third-party misalignment as a source of such failures. At least one successful SPF or DKIM result must align with the visible From domain.

Consider a marketing platform using a company’s address in the From field. If **SPF and DKIM** authenticate only unrelated provider domains, neither supplies the required alignment. Marketing may have authorized the campaign, but the message can still fail DMARC.

**Report analysis** helps teams identify these problems before enforcement. An unfamiliar sending source requires investigation; unfamiliarity alone establishes neither abuse nor business legitimacy. Technical observations need to be connected with operational responsibilities:

- **Marketing and sales:** identify approved platforms, external agencies, and campaign services.
- **IT and security:** investigate authentication failures and determine which configurations need correction.
- **Service owners:** confirm business purpose, coordinate changes, and validate affected messages.

DNS measurements reveal configuration gaps, but cannot answer those ownership questions. [DMARCguard’s February 2026 study](https://dmarcguard.io/research/email-authentication/) detected SPF, DKIM, and DMARC together on 14.7% of 5,499,028 domains, or 810,525 domains. Protocol presence does not establish that every legitimate message passes alignment.

![Dmarc Analyzer 6520](https://media.mailhop.org/dmarcreport/dmarc-analyzer-6520-1794828905534.jpg)

Source: DMARCguard, 2026 Tranco domain scan

The same study found 40.8% with no SPF or DMARC record and no DKIM key at the selectors probed. Selectors identify where DKIM [public keys](https://www.investopedia.com/terms/p/public-key.asp) are published. Probing selected names can miss keys elsewhere, so this finding does not establish definitive absence of all three protocols.

_Its five-component bundle was rarer: 1,940 domains, or 0.04%, had SPF, DKIM, DMARC, MTA-STS, and BIMI_. This measures detected bundle adoption, not the number of domains capable of effective **DMARC enforcement**.

MTA-STS and BIMI are not prerequisites for DMARC enforcement. Their absence does not establish ineffective authentication. Conversely, detecting all five components does not prove correct alignment for every sender. The operational question remains whether legitimate mail authenticates correctly.

Apparently inactive domains also require an inventory decision. DMARC Report’s dataset comparison notes that broad samples include parked domains, brochure-only sites, and **infrastructure properties**. Their presence in a sample establishes neither sending activity nor observed attacks.

_For an organization, “inactive” should prompt confirmation of intended use and ownership, not an assumption of safety._ The difficult work is resolving uncertainty about senders and dependencies before changing their treatment.

![Dmarc Lookup 3207](https://media.mailhop.org/dmarcreport/dmarc-lookup-3207-1794828978909.jpg)

A 10x10 grid representing the tiny share of domains that deploy DMARC, SPF, DKIM, MTA-STS, and BIMI together. Method: The waffle value uses DMARCguard’s reported 0.04% share of domains with the complete stack across 5.5 million Tranco domains, illustrating how few domains reach the highest maturity level of email authentication.

## A practical route from monitoring to enforcement

Move toward enforcement through accountable stages, not an arbitrary deadline. The following sequence synthesizes supplied guidance; it is not a tested implementation study. _Readiness depends on understanding legitimate traffic and investigating failures, rather than meeting an invented pass-rate threshold._

[Mailgun’s authentication guidance](https://www.mailgun.com/state-of-email-deliverability/chapter/email-authentication-requirements/) supports starting with monitoring and using the findings to introduce **stricter policies**. Each organization must apply that progression to its own delivery risks.

1. **Inventory domains and assign owners.**Create a register of domains, business owners, technical administrators, and expected email use. Include domains believed to send no mail, and have an accountable owner confirm that assumption._Specify who investigates failures, coordinates service changes, and approves policy updates. Maintain this register as part of the control, rather than treating inventory as a one-time task._
2. **Enable aggregate reporting and assign review.**Configure the rua destination and confirm that reports arrive where the responsible team can interpret them. Publishing an address is not enough. Reporting provides visibility; it is not required for an enforcing policy to function. [DMARC Report’s adoption analysis](https://dmarcreport.com/blog/the-dmarc-adoption-2026-domains-records-only-9-percent-protected/) emphasizes combining enforcement with reporting, but these remain distinct capabilities. One requests handling; the other supports investigation and maintenance. Give monitoring explicit objectives: discover senders, investigate failures, and prepare a policy decision. Record unresolved questions and their owners rather than promising a universal completion date.
3. **Identify legitimate services before authorizing them.**Compare reported sources with the [domain register](https://www.forbes.com/advisor/business/how-register-domain-name/) and information from business teams. Ask service owners to confirm each platform’s purpose and **configuration responsibilities**. Do not automatically authorize unfamiliar sources or assume they are abusive. Equally, recognizing a supplier does not prove that every associated message is correctly configured._Record confirmed services, unresolved sources, and the evidence supporting each classification._ This gives technical teams a specific investigation list and preserves the basis for later decisions.
4. **Repair alignment and verify representative traffic.**Correct legitimate services that authenticate without aligning to the visible From domain. [DMARC Report’s technical overview](https://dmarcreport.com/blog/email-authentication-impact-on-deliverability-spf-dkim-dmarc-inbox-placement/) explains that DMARC requires at least one successful, aligned SPF or DKIM result. Work with service administrators to repair sending or signing configurations. Check representative messages and subsequent reports to assess whether the changes worked. Document unresolved exceptions and their business consequences. A favorable overall pass rate should not conceal a failing critical service.
5. **Introduce enforcement through controlled changes.**Select a domain whose legitimate sending behavior is understood. Document the proposed policy, expected effects, **review responsibilities**, and authority for corrective action. Moving to `p=quarantine` requests restrictive handling; `p=reject` requests rejection. Distinguish those published requests from observed receiver behavior. After each change, review unexpected failures alongside delivery evidence and business feedback. Investigate legitimate failures before deciding whether to pause, reverse, or continue the change. Progress toward rejection when the evidence supports it, not merely because a calendar milestone arrives. This synthesis does not recommend percentage-based rollout because the supplied evidence does not reliably establish applicable protocol-version guidance.
6. **Maintain monitoring after enforcement begins.**Continue reviewing new sources, changed authentication results, and unexpected legitimate-mail failures. Require service owners to revisit authentication when adding or replacing sending platforms. Keep a named owner for exceptions and corrective work after reaching `p=reject`. **Preserve policy decisions**, repairs, and observed outcomes so future administrators can maintain the control without repeating discovery.

_The sequence is a decision framework, not a promise of disruption-free deployment. Its purpose is to make enforcement decisions traceable, reversible where necessary, and supported by evidence._

![Dmarc Service 6710](https://media.mailhop.org/dmarcreport/dmarc-service-6710-1794829007332.jpg)

A practical decision guide that leads domains from no DMARC or `p=none` monitoring toward enforced quarantine or reject policies with reporting. Method: Nodes and branches are derived from common implementation sequences described by Mailgun, DMARC Report, and cohort studies, abstracted into a generic progression from record publication through reporting, inventory, partial enforcement, and full reject.

## Measure a maintained control, not a checked box

[DMARC](https://dmarcreport.com/) success should mean a maintained control, not a published record. _Management reporting should distinguish configuration, operational visibility, and observed outcomes rather than compress them into one compliance percentage._

[Valimail’s 2026 report preview](https://www.valimail.com/dmarc-report-2026-preview/) separates enforcement, reporting-only, and `p=none` configurations without reporting. These categories provide a starting point. An internal scorecard should also expose ownership and unresolved risks.

Use five measures, each with a defined domain population and review date:

- **Publication:** Identify valid records and missing or invalid configurations. Keep the denominator explicit so inventory changes do not masquerade as progress.
- **Policy level:** Separate `p=none`, `p=quarantine`, and `p=reject`, noting relevant limits on enforcement scope.
- **Reporting coverage:** Distinguish configured destinations from reports actually received and reviewed.
- **Alignment problems:** Track unresolved legitimate-sender failures, affected services, business impact, and remediation status.
- **Ownership:** Record an accountable owner, next review date, and documented decision for each **monitoring configuration**.

Treat stalled monitoring and unresolved legitimate-sender failures as management issues, not merely technical backlog. _Track their age, blockers, and responsible teams without inventing universal deadlines or acceptable failure thresholds._

Enforcement without reporting still requests **protective action**. Missing reports reduce operational visibility; they do not convert quarantine or rejection into monitoring-only policies. Reporting supports maintenance but does not activate enforcement.

Keep configuration evidence separate from delivery evidence. A [DNS scan](https://www.cloudsek.com/knowledge-base/dns-scanner) establishes the published policy, not whether messages were rejected, reached inboxes, or caused disruption. Reports and delivery observations can inform those assessments, but their coverage remains incomplete.

Claims about broader phishing reduction or inbox-placement gains require outcome-specific evidence. The supplied material does not establish how much DMARC alone changes either result. Those claims should not substitute for **measurable policy** and operational improvements.

The central management decision is practical: give `p=none` a purpose, an owner, and a reviewed path toward enforcement. Measure whether teams resolve legitimate-mail risks and make informed policy decisions—not simply whether someone once added a DNS record.

## Limitations

- This paper relies on supplied summaries of vendor research. Original source text, datasets, and methods were not independently inspected or verified.
- _Studies use different populations, observation dates, and denominators. Their percentages are not interchangeable and do not form a single time series_.
- DNS scans measure published configurations, not delivery outcomes or organizational practices. Limited **DKIM selector** probing can miss deployed keys.
- Survey findings describe stated intentions, not subsequent behavior. The supplied summary does not establish the relevant survey’s sampling details or fieldwork date.
- Conflicting source mappings and unsupported outcome claims limit interpretation. The paper omits quantitative phishing-reduction claims and unverified **protocol-version guidance**.

## References

1. [DMARC Adoption 2026: 30.4% of 5.5M Domains, 12.8% Enforce](https://dmarcguard.io/research/email-authentication/)
2. [Email authentication adoption 2026: SPF, DKIM and DMARC in the top 10,000 domains](https://shipmail.to/research/email-authentication-adoption/2026)
3. [Email Authentication at Scale: A Systematic Review and 2026 …](https://spamcipher.com/insights/email-authentication-spf-dmarc-2026)
4. [Why 2026 Email Authentication Numbers Don’t Agree](https://dmarcreport.com/blog/why-2026-email-authentication-numbers-don-t-agree/)
5. [2026 State of DMARC Report - Valimail](https://www.valimail.com/dmarc-report-2026-preview/)
6. [The State of DMARC Adoption in 2026:938,000 Domains Have …](https://dmarcreport.com/blog/the-dmarc-adoption-2026-domains-records-only-9-percent-protected/)
7. [DMARC, SPF, and DKIM in 2026: Why Email Authentication Is Now …](https://www.duocircle.com/blog/dmarc-spf-dkim-2026-email-authentication-regulatory-requirement-best-practice/)
8. [Email Authentication Requirements in 2025](https://www.mailgun.com/state-of-email-deliverability/chapter/email-authentication-requirements/)
9. [DMARC Market Size, Share & Forecast Report 2025 to 2034](https://dataintelo.com/report/dmarc-market)
10. [DMARC Adoption Statistics 2026: Fortune Global 500 - SimpleDMARC](https://simpledmarc.com/research/state-of-email-authentication-2026)
11. [Email Authentication and Deliverability: How SPF, DKIM, and …](https://dmarcreport.com/blog/email-authentication-impact-on-deliverability-spf-dkim-dmarc-inbox-placement/)

![Brad Slavin](https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg) 

[ Brad Slavin ](/authors/brad-slavin/) 

General Manager

General Manager of DuoCircle. Product strategy and commercial lead for DMARC Report's 2,000+ customer base.

[LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) 

## Take control of your DMARC reports

Turn raw XML into actionable dashboards. Start free - no credit card required.

[Start Free Trial](https://app.dmarcreport.com/signup?plan=free) [Check Your DMARC Record](/tools/dmarc-checker/) 

 AutoSPF 

Automatic SPF Flattening

Streamline your SPF record management, enable DMARC compliance, and improve your email deliverability by fixing the SPF 10-lookup limitation.

[ Fix My SPF Record! → ](https://autospf.com/pricing/?utm%5Fsource=dmarcreport&utm%5Fmedium=blog-sidebar&utm%5Fcampaign=autospf-cross-promo&utm%5Fcontent=fix-my-spf) [ See How It Works ](https://autospf.com/how-it-works/?utm%5Fsource=dmarcreport&utm%5Fmedium=blog-sidebar&utm%5Fcampaign=autospf-cross-promo&utm%5Fcontent=how-it-works) 

Share this article

[ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F) [ ](https://twitter.com/intent/tweet?text=DMARC%20Compliance%3A%20Why%20a%20Published%20Record%20Is%20Just%20the%20Start&url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F) [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fdmarc-compliance-why-a-published-record-is-just-the-start%2F) Copy 

Related Articles

- [ ![10 Reasons Why DKIM Fails](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg)  10 Reasons Why DKIM Fails Intermediate ](/blog/10-reasons-why-dkim-fails/)
- [ ![ActiveCampaign SPF DKIM DMARC Setup](https://media.mailhop.org/dmarcreport/dmarc-service-6087-1795078247977.jpg)  ActiveCampaign SPF, DKIM & DMARC Setup Guide Intermediate ](/blog/activecampaign-spf-dkim-dmarc-setup-guide/)
- [ ![AppRiver SPF Record](https://media.mailhop.org/dmarcreport/dmarc-check-7224-1785846270575.jpg)  AppRiver SPF Record: How To Set It Up (Owned By Zix) Intermediate ](/blog/appriver-spf-record-setup-guide-for-zix-email-security-platform/)
- [ ![Best DMARC Reporting Tools in 2026: Honest Comparison](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-report-4236.jpg)  Best DMARC Reporting Tools in 2026: Honest Comparison Intermediate ](/blog/best-dmarc-reporting-tools-2026/)

## Related Articles

[  Intermediate 4m  10 Reasons Why DKIM Fails  Apr 19, 2022 ](/blog/10-reasons-why-dkim-fails/)[  Intermediate  ActiveCampaign SPF, DKIM & DMARC Setup Guide  Nov 19, 2026 ](/blog/activecampaign-spf-dkim-dmarc-setup-guide/)[  Intermediate  AppRiver SPF Record: How To Set It Up (Owned By Zix)  Aug 4, 2026 ](/blog/appriver-spf-record-setup-guide-for-zix-email-security-platform/)[  Intermediate 8m  Best DMARC Reporting Tools in 2026: Honest Comparison  Mar 25, 2026 ](/blog/best-dmarc-reporting-tools-2026/)

```json
{"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"473","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]}
```

```json
{"@context":"https://schema.org","@type":"WebSite","name":"DMARC Report","url":"https://dmarcreport.com","description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","publisher":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}}
```

```json
[{"@context":"https://schema.org","@type":"BlogPosting","headline":"DMARC Compliance: Why a Published Record Is Just the Start","description":"Learn why DMARC publication does not guarantee enforcement and how organizations can move from monitoring-only policies to stronger email authentication.","url":"https://dmarcreport.com/blog/dmarc-compliance-why-a-published-record-is-just-the-start/","datePublished":"2026-11-16T00:00:00.000Z","dateModified":"2026-11-16T00:00:00.000Z","dateCreated":"2026-11-16T00:00:00.000Z","author":{"@type":"Person","@id":"https://dmarcreport.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://dmarcreport.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the General Manager of DuoCircle, the company behind DMARC Report, AutoSPF, Phish Protection, and Mailhop. He founded DuoCircle in 2014 and has led the company's growth to 5,000+ customers across its email security product family. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement).","image":"https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"473","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://dmarcreport.com/blog/dmarc-compliance-why-a-published-record-is-just-the-start/"},"articleSection":"intermediate","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/dmarcreport/dmarc-record-6408-1794828515559.jpg","caption":"DMARC Compliance and Enforcement Challenges"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}}]
```

```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://dmarcreport.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://dmarcreport.com/blog/"},{"@type":"ListItem","position":3,"name":"Intermediate","item":"https://dmarcreport.com/intermediate/"},{"@type":"ListItem","position":4,"name":"DMARC Compliance: Why a Published Record Is Just the Start","item":"https://dmarcreport.com/blog/dmarc-compliance-why-a-published-record-is-just-the-start/"}]}
```
