SPF and DKIM by provider

SPF record for Mailjet

Last updated 2026-08-26

Mailjet sends campaigns and transactional mail. Here is what to publish so it can do that as your domain, and what has to line up before DMARC will pass.

The SPF record

Add one mechanism to the SPF record on your sending domain:

In a complete record, alongside Google Workspace, that looks like:

One include on the domain you send from. Mailjet's sender domain screen shows it alongside the DKIM record, and it will tell you whether it can see both.

Then count your lookups. SPF allows ten DNS-querying mechanisms across the entire nested chain, and the eleventh turns the record into a permerror that authorises nothing. The record still reads correctly to a human while every check fails. Run the domain through the SPF checker after every change, because the number moves when your providers change their own records, not just when you change yours.

DKIM

Mailjet publishes a TXT record under the mailjet selector, with a key generated for your account. Copy the value from the account's sender domain page; it is long, and a truncated paste is the usual reason verification stays red.

DMARC alignment with Mailjet

DMARC passes when SPF or DKIM passes and the domain it authenticated matches the domain in your visible From address. A provider can pass both checks for its own domain and leave you failing. These are the Mailjet specifics:

• Validating a single sender address only proves you can read that mailbox. Domain authentication is a separate step and the one that affects DMARC.
• Mailjet sends with its own envelope sender on the default setup, so DKIM is what aligns.
• Keys are per account. Two Mailjet accounts sending as the same domain need the domain authenticated in both, and the second one will overwrite the first if you are not careful with the record names.

The general case is covered in alignment, explained, and the header you read to prove it is on the dmarc=fail page.

Verify it

Substitute your domain, and run these after the TTL on anything you replaced has expired:

Then send one message through Mailjet to a Gmail address you control, open Show original, and look for dkim=pass with your domain in header.i. That single check is worth more than any number of DNS lookups, because it tests the thing receivers actually do.

Our SPF checker gives you the lookup count, the DKIM checker confirms a selector resolves and the key is long enough, and the DMARC checker reads your policy back to you. All three are free and none of them ask for an account.

Values here were checked against Mailjet's own documentation, at Mailjet documentation. Providers change DNS requirements without much announcement, so if their screen disagrees with this page, believe their screen and tell us.

A record can read correctly and still fail alignment once real mail moves through it. Receivers write that verdict into the reports they send. We read them for you, and paid plans email you the same day one names a new sender that failed, instead of holding it for Monday. See whether this sender passes. Your first domain is free.