All platforms
CRM-matched DNS
Pipedrive · 3 CNAME + 2 TXT · DKIM · BOUNCE · SPF · DMARC
Pipedrive DNS Checker
Pipedrive sends from your domain using its own required records
, 3 CNAME + 2 TXT covering DKIM, BOUNCE, SPF, DMARC. A generic SPF test
cannot see whether they match. We check your live DNS against
Pipedrive’s spec, host by host, character by character.
Free, no account.
domain only, we strip email and protocol automatically
What Pipedrive requires
Pipedrive Campaigns: 3 CNAME for DKIM + 1 TXT for SPF + 1 TXT for company identifier. Pipedrive delegates sending to Mandrill, so DNS may also match Mandrill. This is the exact table our verifier checks
your DNS against, not a generic template.
| Type | Host | Required value | Purpose |
|---|
| CNAME | pipedrive1._domainkey | pipedrive1.dkim.pipedrive.com | DKIM |
| CNAME | pipedrive2._domainkey | pipedrive2.dkim.pipedrive.com | DKIM |
| CNAME | mta | mta.pipedrive.com | BOUNCE |
| TXT | @ | v=spf1 include:spf.pipedrive.com ~all | SPF |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:[email protected] | DMARC |
How Pipedrive authenticates
Pipedrive handles DKIM by delegation: you publish 2 CNAME records (selectors pipedrive1, pipedrive2) pointing into pipedrive1.dkim.pipedrive.com, and Pipedrive hosts and rotates the actual signing keys on its side. You never see the public key, which also means a checker that only looks for TXT keys at _domainkey will wrongly report DKIM as missing here.
For SPF, Pipedrive needs its include (spf.pipedrive.com) present in the ONE SPF record your domain is allowed to publish. If you already have an SPF record, this include is merged into it, never added as a second record; two SPF records is an automatic PermError everywhere.
The non-DKIM CNAME handle tracking or bounce domains. They carry no authentication themselves, but Pipedrive's setup screen will not verify the domain until they resolve.
DMARC is yours, not the platform's: one record at _dmarc governs every sender on the domain. If another tool already publishes it, do not add a second; the spec row above shows the minimum this platform expects to find.
Mistakes we see on Pipedrive domains
Publishing the CNAME target as a TXT record. The record type matters: a TXT with the right value still is not a delegation, and the key lookup dies at your zone.
Proxying the _domainkey CNAMEs through a CDN. They must resolve as plain DNS; an orange-clouded record answers with the CDN's addresses and the key disappears.
Adding Pipedrive's SPF as a second TXT record next to an existing v=spf1. Receivers see two records and hard-fail both.
Why a generic checker misses this
A standard DNS tool tells you your SPF parses and your DMARC exists. It has no
idea Pipedrive is in the picture. It cannot tell you a required CNAME points at
the wrong target, a selector is missing, or the include chain never reaches
Pipedrive’s servers, which are precisely the failures that put
Pipedrive mail in spam while every generic check shows green.
Read the full Pipedrive setup guide →
Common questions
What DNS records does Pipedrive require?
Pipedrive requires 5 DNS records: 3 CNAME + 2 TXT, covering DKIM, BOUNCE, SPF, DMARC. The exact hosts and values are in the table above, they come from the same spec table our verifier checks against.
Why does a normal SPF checker pass my domain but Pipedrive mail still fails?
A generic checker only tests whether your SPF record parses. It does not know which include Pipedrive needs, which CNAME targets its DKIM keys live behind, or which selector names it signs with. We compare your live DNS against Pipedrive’s required records character by character, so a missing include or a typo in a CNAME target is called out by name.
Will adding these records break my existing email?
The DKIM CNAMEs and the DMARC record are additive. SPF is the one to be careful with: a domain must publish exactly one SPF record, so if you already have one, merge the new include into it rather than adding a second record, two SPF records is an automatic PermError.
Keep going