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

The right order: SPF, DKIM, DMARC, then BIMI

Set up SPF and DKIM for every service that sends as your domain first. Then publish DMARC at p=none with reporting turned on, use the reports to find and fix every legitimate source, and move to enforcement (p=quarantine, then possibly p=reject). Only after that does BIMI make sense, with an SVG Tiny PS logo and, for Gmail, a VMC or CMC. The order matters because DMARC can only pass when SPF or DKIM already passes and aligns, and BIMI only works once DMARC is at enforcement.

The slow part isn't any single record. It's the observation period between p=none and enforcement.

Step 1: SPF and DKIM for every legitimate sender

Every platform that sends as your domain needs SPF, DKIM, or ideally both, passing for a domain aligned with your From address (Envelope From vs Header From explains which From address). That includes your main mailbox provider, your marketing platform, your CRM, your helpdesk, and that invoicing tool finance switched on two years ago.

SPF and DKIM don't depend on each other, so either can come first. DMARC needs at least one of them aligned, and preferably both. Set up DKIM and SPF at least 48 hours before you add DMARC.

A typical starting point for a sending domain:

example.com.  TXT  "v=spf1 include:_spf.mailvendor.example ~all"

Our standing advice is ~all for domains that send mail, because -all can get mail rejected before DMARC is even evaluated. Domains that send no mail at all are a different case: they should publish v=spf1 -all.

Step 2: Somewhere for reports to go

Before you publish DMARC, decide where aggregate reports will land and who will read them (Who usually owns SPF, DKIM, and DMARC). Reports are machine-readable files meant to be parsed by software, not read by hand.

Step 3: Publish DMARC in monitoring mode

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

What p=none means

p=none is monitoring mode. You're telling receivers you offer no expression of preference about failing mail, and it must not modify existing mail handling. So p=none doesn't protect your domain and doesn't change where your mail goes. It earns you data, and only if rua is set. Without rua, you get nothing back at all.

How to build the record: the main-site DMARC setup guide.

Step 4: Inventory and fix your sources

This is where the work is. Read the reports, list every source sending as your domain, and sort them into "ours and passing," "ours and failing," and "not ours". Fix the failing legitimate streams, usually by turning on DKIM with your domain or setting a custom bounce domain in the platform.

These gaps must be addressed before you publish an enforcement policy.

How long should you watch? Guidance differs, and both ends of the range are worth knowing. A week at p=none is often enough to start collecting report data, but reaching confidence may take many months, depending on how often your different streams send. Treat a week as the minimum window for data, not a sign-off. A quarterly invoice run won't show up in seven days.

BIMI Certifications' DMARC reporting and visual analysis helps with exactly this step: it shows which sources send as your domain and whether SPF, DKIM, and alignment pass, before you change the policy. It doesn't move your policy for you.

Step 5: Move to DMARC enforcement

Enforcement is the state where the policy for your organizational domain and all subdomains below it is something other than p=none. The next step is p=quarantine:

_dmarc.example.com.  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com"

Quarantine says you consider failing mail suspicious. What a receiver actually does with it is the receiver's decision; it might be, for example, a junk folder or an admin-held quarantine, and receivers may override your policy entirely. Policies are requests, not commands.

Rolling out gradually without pct

The current DMARC standard (DMARCbis) removed pct, so don't add it to new records. Older guides and some provider pages still show it. The current standard added a testing flag, t=y, which asks receivers not to apply your stated policy while you test. It isn't clear whether Gmail, Microsoft, or Yahoo honor t=y.

Step 6: Consider p=reject, carefully

On dmarc reject vs quarantine: quarantine marks failing mail as suspicious; reject says the failure is a clear indication that the use of the domain name is not valid, and receivers may refuse it outright. Reject is the strongest request you can make, and for some domains it's where this sequence ends. The current standard adds real caveats, though:

  • Domains used for general-purpose email shouldn't deploy p=reject.
  • Domains whose users might post to mailing lists shouldn't either. If you still intend to, run p=none for at least a month, then p=quarantine for an equally long period, and compare the results first.
  • Any domain at p=reject must not rely solely on SPF and must apply valid DKIM signatures, because forwarding breaks SPF.

So p=reject is a considered decision per domain, not an automatic finish line.

Step 7: BIMI, only after enforcement

BIMI shows your logo next to authenticated mail in mailboxes that support it. For the basics, see What is BIMI on our main site. It sits at the end of this list for hard technical reasons:

  • BIMI requires DMARC at quarantine or reject on both your organizational domain and the From domain. BIMI must not be processed at p=none or sp=none.
  • DMARC must be at enforcement on the organizational domain and subdomains, and none policies are not accepted. If an old record still carries pct, remove it. Whether t=y affects BIMI isn't documented, so remove it before relying on BIMI. Check your subdomain policy too.
  • Gmail requires p=quarantine or p=reject, and Yahoo shows logos only with quarantine or reject.

Then, in order: an SVG Tiny PS logo (a restricted SVG profile), a VMC or CMC where the mailbox provider requires one, and a BIMI record at default._bimi.example.com.

VMC or CMC?

  • A VMC (Verified Mark Certificate) is issued against a registered trademark (What is a VMC).
  • A CMC (Common Mark Certificate) is for a logo that has been used on your own website, on the same domain, for at least 12 months, checked through the Internet Archive. Other official routes exist.

Gmail accepts either, recommends a VMC, and shows its checkmark only for VMC senders. Yahoo can show a logo without a certificate, but only on bulk mail from senders it sees as having enough reputation and engagement. Microsoft hasn't documented BIMI logo display in Outlook.com or Microsoft 365. More on choosing: Is VMC still worth it now that CMC exists?

And one expectation to set early: BIMI does not change message delivery. It's a display feature.

Mistakes that cost the most time

  • Publishing DMARC before your platforms sign with an aligned DKIM domain, then panicking at the first reports.
  • Publishing p=none with no rua, so there's no data to decide with.
  • Staying at p=none indefinitely because nobody reads the reports.
  • Leaving sp=none or an old pct value in the record and wondering why BIMI doesn't show.
  • Buying a VMC or CMC before enforcement. Or, for a CMC, before the logo has 12 months of archived history on the same domain.
  • Changing your logo shortly before applying for a CMC. The archived logo has to match.
  • Moving to p=reject on a domain whose staff post to mailing lists.

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 I set up BIMI with p=none?

No. Quarantine or reject is required for BIMI, and by Gmail and Yahoo.

Is p=reject always the end goal?

Not for every domain. The current standard advises against it for general-purpose mail domains and for domains whose users post to mailing lists. Decide domain by domain.

Should SPF or DKIM come first?

Either. DMARC needs at least one aligned, and both is better.

Does BIMI help deliverability?

No. It's a display feature that comes after enforcement.