Records to publish
Hosts are full names, with {domain} standing for your domain; most DNS panels want only the part before it (@ for the domain itself). Anything else in {braces} is specific to your Mailjet account: copy it from Mailjet's setup screen, which shows the exact record.
| For | Type | Host | Value |
|---|---|---|---|
| SPF | TXT | {domain} | v=spf1 include:spf.mailjet.com ~allMerge the include into your existing SPF record. |
| DKIM | TXT | mailjet._domainkey.{domain} | k=rsa; p={public-key}Copy the key from Account Settings > Domains and Senders > Setup SPF/DKIM authentication. |
| Return path optional | CNAME | bnc3.{domain} | bnc3.mailjet.comPaid accounts only; after publishing it, open a support ticket so Mailjet activates it. |
| DMARC optional | TXT | _dmarc.{domain} | v=DMARC1; p=none; rua=mailto:{report-address}Mailjet suggests starting at p=none and moving to quarantine and reject gradually. |
SPF
Mailjet checks for include:spf.mailjet.com in your root SPF record, for example v=spf1 include:spf.mailjet.com ~all. That include doesn't make SPF align, because the default Return-Path is on bnc3.mailjet.com; only the custom bnc3.{domain} Return-Path aligns, under relaxed alignment.
DKIM
One TXT record at mailjet._domainkey.{domain} with the public key Mailjet shows; keys are 2048-bit by default since April 2024, with 1024- and 4096-bit selectable when you regenerate. Rotation is manual: Regenerate Key, then replace the DNS record; existing domains aren't upgraded automatically.
DMARC alignment
DKIM aligns: Mailjet signs with the key at mailjet._domainkey.{domain}. SPF doesn't align by default (Return-Path bnc3.mailjet.com); it aligns only with the custom bnc3.{domain} Return-Path and relaxed SPF alignment.
Common mistakes
- Mailjet's Quick Start calls the DKIM record a CNAME, but the value is a TXT public key, so publish it as TXT.
- Some DNS hosts append the domain to the host field automatically or need the TXT value in double quotes.
- Some DNS hosts reject or truncate 2048- or 4096-bit keys; regenerate a 1024-bit key if needed, which requires the whole domain to be validated.
- The custom Return-Path is paid-only, activated by support and limited to one per API key; keep aspf relaxed, since bnc3.{domain} never matches the From domain exactly.
- Mailjet's API default SPF value ends in ?all, while its help center uses ~all.
- Domain validation is per API key, so subaccounts need their own validation.
Check that it worked
DNS changes can take a few minutes to show. Then run the free checks, no account needed:
How EmailSecOps recognises Mailjet
A domain check names the services it finds in your DNS, leftovers from older setups included, so you can see which senders are set up and which are missing a key:
- SPF include, current or legacy: spf.mailjet.com
- Default DKIM selectors: mailjet
Questions
What SPF record does Mailjet need?+
What are the DKIM records for Mailjet?+
Does Mailjet mail pass DMARC?+
Do I need a separate DMARC record for Mailjet?+
Sources
- Authenticating Domains with SPF and DKIM: A Complete Guide (Mailjet help center)
- Quick Start with Mailjet (Mailjet help center)
- Understanding DMARC (Mailjet help center)
- Can I customize the return-path header with Mailjet? (Mailjet help center)
- How to validate an entire sending domain? (Mailjet help center)
- SPF and DKIM validation (Mailjet developer docs)
- Default 2048 DKIM support for all sending domains in Mailjet (release note)