Help Center
Docs

SPF, DKIM and DMARC Domain Setup

Set up SPF, DKIM, DMARC, and MX for your mail provider, keep one DMARC record, and understand how tracking domains work

Why Domain Authentication Matters

What the records prove, and what Laureo checks.

SPF, DKIM and DMARC are the DNS records that prove your cold email comes from your domain: SPF lists the servers allowed to send for it, DKIM puts a signature on each message, and DMARC tells receivers what to do with mail that fails those checks. Mailbox providers check these records on the mail they receive. Laureo checks the DNS records of the domain of every cold mailbox. A mailbox whose domain fails a blocking check takes no new leads. A sequence cannot launch until one of the mailboxes it can send from passes: an active mailbox of its owner that is not paused and, when you picked mailboxes for the sequence, one of those.

SPF, DKIM, DMARC, and MX

The DNS records a sending domain uses.

FieldDescription
SPFA TXT record at your domain that lists the servers allowed to send mail for it. A domain has one SPF record. To allow another mail service, edit that record and put the include of the service in it.
DKIMA signature your mail provider adds to each message. Receivers check it against a public key that your provider asks you to publish in DNS.
DMARCA TXT record at _dmarc that tells receivers what to do with mail that fails SPF and DKIM, and where to send reports. When a domain has two or more DMARC records, receivers ignore all of them.
MXThe record that names the server that receives mail for your domain. Replies to your cold emails arrive through it.

What Stops New Leads

Five DNS problems stop a mailbox from taking new leads. Every other finding is a warning.

The check stops new leads on a mailbox when its domain has one of these problems:

  • No SPF record
  • No DMARC record
  • More than one DMARC record
  • A DMARC record with no valid policy (p=)
  • An SPF record that cannot authorize your mail provider, with no DKIM key published
A failing mailbox takes no new leads
A mailbox whose domain fails one of these checks takes no new leads, and a paused mailbox cannot resume until it passes. Emails to leads it already contacted keep sending. A new mailbox also takes no new leads until a check of its domain finishes. A sequence cannot launch until one of the mailboxes it can send from passes: an active mailbox of its owner that is not paused and, when you picked mailboxes for the sequence, one of those. Fix the record at your DNS host, then press Re-check now on the mailbox card.

DKIM does not block sending on its own. To confirm it, send a test email and look for DKIM: PASS in the message source.

Every other finding is a warning or a note, and never stops sending on its own: an SPF record that needs more than 10 DNS lookups, SPF that ends in +all, a missing, revoked, or short DKIM key, a DMARC policy of p=none, a report address on another domain, and MX problems. A DMARC policy of quarantine or reject is also a warning when neither SPF nor DKIM passes for the provider of the mailbox: receivers then send its mail to spam or reject it. A record with pct=0 applies its policy to no mail, so it shows no such warning. Two SPF records, or an SPF record without the include of your provider, are a warning while a valid DKIM key is published at a selector of your provider. Without such a key, an SPF record that cannot authorize your provider stops new leads, because no message from the mailbox can pass SPF or DKIM. Fix warnings anyway: receivers can filter mail from a domain with a broken SPF record or a weak key.

Check What Is Already Published

A domain keeps one SPF record and one DMARC record.

Keep one DMARC record: edit the existing one, never add a second. Keep one SPF record: edit the existing one, never add a second.

Look at what is already published first. Expand the SPF or DMARC row of the DNS check on the mailbox card: it shows every record it found, as published, with the DMARC policy, the subdomain policy, the alignment, the share of mail the policy applies to, and the report addresses. When a record exists, the card shows Edit the existing record with the new value, when a check from the last 24 hours read the record. It shows Add this record only when a check from the last 24 hours proved that the domain has no such record.

When the last result is more than a day old, the card asks you to press Re-check now to see the live record first. A Re-check press asks the servers of your DNS host first, and follows a CNAME record there (the Microsoft 365 DKIM records, or a DMARC record you point to a report service), so it sees a new or changed record as soon as your host publishes it. Some answers still come from the shared DNS cache, which can keep an old answer for up to a few hours: a record you deleted, and every record when the servers of your DNS host cannot be reached or do not answer within one second. A Re-check press stores what it read. When one lookup times out or fails, only that row shows Could not check and no record block. The last result stays in effect when the SPF or DMARC lookup fails. A result from the last 24 hours also stays when the lookups of the SPF record cannot finish, or when a timeout can hide a problem with a Microsoft 365 DKIM key. Try Re-check now in a few minutes.

New records usually work within about 10 minutes. Some DNS hosts can take up to 48 hours. If the check still reports a missing record right after you added it, that is usually propagation rather than a mistake in the record.

Records for Your Mail Provider

SPF, DKIM, MX, and the DMARC policy the check suggests depend on who hosts the mailbox.

The check reads the provider of each mailbox: a Google mailbox is checked against the Google Workspace records, and a Microsoft mailbox against the Microsoft 365 records. DKIM passes when the check finds a valid key of 1024 bits or more at the provider's standard selector: google for Google Workspace, selector1 or selector2 for Microsoft 365. A key at any other selector does not count: the card reads DKIM could not be verified, and a key found at another common selector adds the note DKIM key at another selector.

Google Workspace

  • SPF: when the domain has no SPF record, publish v=spf1 include:_spf.google.com ~all. When it has one, edit it and put include:_spf.google.com before the all term.
  • DKIM: In Google Admin, open Apps > Google Workspace > Gmail > Authenticate email. Generate the record, publish it at your DNS host, then click Start authentication.
  • MX: Google Workspace receives mail at smtp.google.com (MX priority 1).

Microsoft 365

  • SPF: when the domain has no SPF record, publish v=spf1 include:spf.protection.outlook.com ~all. When it has one, edit it and put include:spf.protection.outlook.com before the all term.
  • DKIM: In the Microsoft Defender portal, open Email authentication settings > DKIM and select the domain. Publish the two CNAME records it shows, then turn on signing.
  • MX: Microsoft 365 receives mail at a host that ends in mail.protection.outlook.com or mx.microsoft. Copy the exact MX host from the Microsoft 365 admin center.

Another Service That Sends From the Domain

A cold mailbox connects through Google Workspace or Microsoft 365 only. When another service also sends mail from the same domain, it needs its own SPF include and its own DKIM key. Keep the MX records of the provider of your cold mailbox: replies arrive through them.

  • SPF, when the domain has an SPF record: Other mail service: ask your provider for its SPF include and DKIM record. Then edit your one SPF record to add the include.
  • SPF, when the domain has no SPF record: Other mail service: ask your provider for its SPF include and DKIM record. Then add one SPF record that lists the include.
  • DKIM: Ask your mail provider for its DKIM record, then publish it at your DNS host.

The DMARC Record

One record, a report address on your own domain, and a policy you choose.

The policy the check suggests depends on the provider of the mailbox and on its SPF record. When the mailbox is on Google Workspace or Microsoft 365 and SPF passes for that provider alone, the check suggests v=DMARC1; p=quarantine; sp=none; rua=mailto:dmarc@yourdomain.com. SPF passes for that provider alone when all of these are true: the domain has one SPF record, the include of that provider is the only sender in it, the record ends in ~all or -all, the check finished all the DNS lookups of the record, and the record needs 10 DNS lookups or fewer. Another include, an ip4, ip6, a, or mx term, or a redirect in the record counts as another sender. Every active cold mailbox of your workspace on the domain also has to be on that provider: when two of them are on different providers, the card of neither one raises the policy to quarantine. These providers send with your own domain as the envelope sender (the return address that SPF checks), so SPF aligns and DMARC passes before DKIM is proven. Publishing quarantine before DKIM is on can send forwarded mail to spam, so turn on DKIM next. The sp=none tag keeps subdomains at the policy they have today. For a domain with no DMARC record, in every other case the check suggests v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Move to p=quarantine once a test email shows DKIM: PASS in the message source. A mailbox on a subdomain with no DMARC record of its own uses the record of its parent domain. When that record only monitors mail (policy none) and SPF passes for the provider alone, the check suggests the quarantine value at _dmarc of the subdomain. It changes nothing for the parent domain. When the record of the parent already quarantines or rejects mail, there is nothing to change.

When the domain already has a DMARC record, edit it to the suggested value. When it has two or more, delete all but one, then edit the one left. When SPF passes for the provider alone, the check raises a published policy of none, or a record with no valid policy, to quarantine. When the domain has one DMARC record, the check never suggests a weaker policy than the one that record publishes. When it has two or more, receivers ignore all of them. When each of them publishes a valid policy, the check never suggests a policy weaker than the weakest of them. When one of them has no valid policy, the check suggests a policy of none, or quarantine when SPF passes for the provider alone. The check keeps a subdomain policy (sp) that you publish. When it raises the policy and you publish no sp, it writes sp=none, so the policy for subdomains does not change. The check keeps a pct value under 100 that you publish, so a staged rollout does not jump to all mail. With two or more records, it keeps the smallest pct of the records that publish the policy it suggests. When it raises a policy of none, it leaves out the pct: a pct on a policy of none stages nothing, and the new policy then applies to all mail. The new value also leaves out failure reports (ruf, fo, rf), the report interval (ri), strict alignment (aspf=s, adkim=s), the newer np, t and psd tags, and the report addresses (rua) it does not keep. The card names each tag the new value leaves out, a dropped pct too. It does not name a tag set to its default value (ri=86400, rf=afrf, fo=0): leaving that out changes nothing.

Send DMARC reports to an address on the sending domain, for example dmarc@yourdomain.com. The mailbox card picks the address for you. When the one DMARC record of the domain already sends reports only to addresses on the domain of the mailbox, and none of them is connected here for cold sending, the card keeps them. Otherwise it picks dmarc@ on the domain of the mailbox, or dmarc-reports@ or dmarc-rua@ when the ones before it are connected here for cold sending. When all three are connected here, the card gives no address and asks you to pick another one on the domain. When the card cannot check which addresses are connected here, it gives no address and says: Could not check which addresses are connected here for cold sending. Press Re-check now before you choose a report address. A report address on another domain shows a warning on the card.

Create dmarc@yourdomain.com as a group that a person reads. Do not make it an alias of a mailbox connected here for cold sending, do not forward it to one, and do not add one as a group member: reports would arrive among your cold replies.

When the Check Runs

On connect, on demand, once a day, and before each launch.

The check runs when you connect a mailbox and when the mailbox owner presses Re-check now on its card. Every active cold mailbox is also re-checked once a day. Right before a sequence launches, the mailboxes of its owner are checked again, unless they were checked in the last 10 minutes. Opening the Mailboxes tab also re-runs the check for up to three of your own mailboxes whose last result is more than a day old.

When a daily or pre-launch check finds a new blocking problem on a mailbox that passed before, the mailbox stops taking new leads, and its owner and your admins get an alert. When any lookup of a daily or pre-launch check cannot finish, the last result stays in effect. A Re-check press stores what it read and marks only the check it could not read.

Primary or Secondary Domain

Sending volume and feedback are tracked per domain.

Email providers track sending volume and feedback per domain. Cold email from your main company domain shares one record with your everyday and transactional mail. Cold email from a second domain keeps the two apart. Laureo supports both. If you connect a mailbox on your primary domain, its card says so.

Custom Tracking Domain

Tracked links run on a standard host today. Your own tracking domain is not switched on yet.

Open and click tracking on cold sequences runs on Laureo's standard tracking host today, a host that all Laureo workspaces share, so the two tracking switches on a sequence work with no setup. Setting up a tracking domain of your own is not switched on yet, so the card in outreach settings shows no field and no button. When it is switched on, a domain you own and have verified wins over the standard host, so the links your recipients see stay on a domain they recognize.

When the setup flow is switched on, the card grows a field and an Add tracking domainbutton, and moving tracked links onto your own domain runs like this:

  1. Choose a tracking subdomain (for example, link.yourdomain.com), never your root domain.
  2. Add the CNAME record Laureo shows you at your DNS host.
  3. Return to outreach settings and verify the domain.
  4. Once it is verified, new emails put tracked links, the unsubscribe link and the one-click unsubscribe header on your domain in place of the standard host. The tracking switches on your sequences stay as they are.
Tracking is optional
Opens and clicks stay off by default on every cold sequence. You can run cold sequences with tracking off and reply based metrics still work. Turning tracking on adds open and click signals to your cold outreach analytics. It does not fire the opened or clicked triggers in Automations: those triggers read campaign email sent to your contacts, and a cold lead is not a contact until you promote it.

Who can set a tracking domain up

Setting one up is a plan feature. Serving links from one is not.

Adding, verifying, retiring, or replacing a tracking domain is a plan feature, and only a teammate with organization-wide outreach access can do it. Everyone else sees the same card in read-only form.

Once a domain is verified, it keeps serving links on every plan. If your plan changes later, campaigns and sequences that already use the host carry on using it, and the one-click unsubscribe header keeps pointing at the same place. Only the ability to change the setup follows the plan. That is deliberate: a billing change should never move the links in mail that has already been delivered.

Retiring a tracking domain

Removing a domain retires it. Keep the DNS record published for 30 days.

The card action is Retire. It takes two clicks: the first arms a warning, the second confirms. Retiring turns open and click tracking off for every sequence in the organization straight away. A campaign that had already frozen the host carries on using it for the rest of its sends, which is why the CNAME record has to stay published.

  • Leave the CNAME record published. Unsubscribe links in mail you already sent resolve through that record. The card shows the date to keep it until, which is 30 days after the last send that used the host.
  • The domain stays claimed by your organization. Retiring does not release the name, so nobody else can pick up a host whose record still points at us and send mail branded with it.
  • You can restore it. The retired card carries a Restore action that brings the same host back as pending. Check the record is still published, then verify it again.
  • You can set up a different one instead. The retired card also shows the add form. Adding a new host retires the old one for you, so changing domains is one step and there is no limit on how many times you can do it.