Skip to content
  • There are no suggestions because the search field is empty.

Who usually owns SPF, DKIM, and DMARC

No standard assigns an owner. In many organizations, IT or an infrastructure team controls DNS and publishes the records, each sending platform's admin (often marketing ops for marketing tools, IT for Microsoft 365 or Google Workspace) turns on DKIM and the bounce domain inside that platform, and security, IT, or a named email-authentication owner reads the reports and decides when the DMARC policy tightens. The arrangement varies with company size and how much is outsourced. What doesn't vary: someone has to own the full list of services that send as your domain. (New to the three records? Start with What is email authentication?.)

What the Domain Owner is responsible for

The Domain Owner is the entity that has control of a given DNS domain, usually by holding its registration. The Domain Owner's jobs are to publish the DMARC record (What is DMARC covers what it is), send mail with at least one (preferably two) aligned identifiers, receive and monitor aggregate reports, and fix authentication problems.

Those are three different kinds of work: DNS, platform configuration, and analysis. In practice they rarely sit with one person. Large organizations frequently adopt a decentralized model for DNS management, with central IT delegating parts of the zone to departments.

Even if you outsource sending, authentication is tied to your domain, so coordinate with your provider to ensure correct DNS settings. If you use an email service provider, verify that they authenticate your domain's email with SPF and DKIM. Each provider's own rules are summarized in Google, Yahoo, and Microsoft sender requirements.

Who should own DMARC policy versus DNS changes?

It helps to split the work into three areas. The "often held by" column is common practice, not a rule.

Area What it covers Often held by
DNS and record publishing Write access to the zone: the SPF TXT record, DKIM keys or CNAMEs, the _dmarc record, a BIMI record IT or infrastructure, a web or hosting agency, or an MSP; sometimes whoever holds the registrar account
Sending-platform setup Turning on DKIM for your domain in each email platform, CRM, or helpdesk; setting a custom bounce domain (Envelope From vs Header From); unsubscribe headers That platform's admin: often marketing ops for marketing tools, IT for Microsoft 365 or Google Workspace
Policy and monitoring Reading aggregate reports, approving new senders, deciding p=none → quarantine → reject, BIMI readiness Security, IT, or a named email-authentication owner, often with marketing, which owns the mail streams and the brand

The dependency runs both ways. Marketing depends on the DNS and platform owners for its mail to pass and align. IT and security depend on marketing to declare every tool that sends as the domain. When that second half breaks down, a new platform goes live with its default settings and nobody hears about it until mail starts failing.

One owner for the inventory

If you only assign one thing, assign the inventory of sending sources. Policy can't safely move toward enforcement until every legitimate stream passes and aligns, and those gaps must be fixed first. Somebody has to know what's on the list, add new tools to it, and check the reports against it.

A handoff that doesn't stall

When marketing needs a change and IT has the DNS keys, many delays come from vague requests. A good request includes:

  • The exact record: host or name, type, and value.
  • Which platform it's for, and a link to that platform's setup page.
  • What "done" looks like, for example "DKIM passes with d=example.com on a test send."

For example:

Host:   s1._domainkey.example.com
Type:   CNAME
Value:  s1.domainkey.mailvendor.example
For:    newsletter platform, DKIM for example.com
Done:   test message shows dkim=pass header.d=example.com

Keep one shared list of every approved sending service with its SPF include, DKIM selector, and bounce domain. And agree who reads the DMARC aggregate reports, and how often.

MSPs and agencies

MSPs and agencies often hold DNS for their clients. With DMARC for MSPs, the sticking point is often authority rather than skill: get written approval from the client before policy changes. The client remains the Domain Owner, even when the agency does all the typing.

Where it usually goes wrong

  • A marketer adds a second SPF record instead of asking the DNS owner to merge the new include into the existing one. Two SPF records on one domain make SPF fail with a permanent error.
  • IT publishes p=quarantine without asking which marketing or invoicing tools send as the domain.
  • A vendor goes live on its default bounce and signing domains, so nothing aligns.
  • The DNS account belongs to a former agency or employee, and nobody can make changes.
  • Nobody reads the rua reports, so the domain sits at p=none forever.

Where BIMI Certifications fits

Our DMARC reporting and visual analysis gives IT, security, and marketing a shared view of which sources send as the domain and whether SPF, DKIM, and alignment pass. It doesn't edit DNS, change platform settings, or change how providers filter mail. It does give everyone the same picture when they sit down to decide.

Free DMARC account

Turn raw DMARC reports into a readable dashboard

Point your rua address to our platform and read the results by sender and source instead of opening XML files.

  • Results grouped by sending source
  • SPF, DKIM and alignment results per sender
  • The original XML reports are still there to download

Create a free DMARC accountTalk to an expert

FAQ

Can marketing set up DMARC alone?

Usually not. Marketing typically can't publish DNS records. It can turn on DKIM inside the platforms it administers and must tell IT about every tool that sends as the domain.

Our email platform says the domain is authenticated. Are we done?

Check two things: that DKIM signs with your domain, and that DMARC passes with alignment. A green badge can mean less than that.

Who decides when to move to p=reject?

Whoever owns the source inventory and the report review, with sign-off from the teams whose mail could be blocked. See The right order: SPF, DKIM, DMARC, then BIMI for the order of steps.

Does our MSP own our DMARC?

They may manage it, but the policy sits on your domain and you're the Domain Owner.

Where does this differ for Microsoft 365 and Google Workspace?

The split is the same; the platform-side steps differ.