Email senders
Elastic Email DMARC setup: SPF, DKIM and bounce domain
How Elastic Email authenticates your domain, why SPF does not align by default, and how to check which domain signs your DKIM.
SPF include for Elastic Email
include:_spf.elasticemail.com
Add this to the SPF record you already have. A domain must publish only one SPF record, so never create a second one.
- DNS lookups it uses
- 2 of 10
- Needed in your SPF record
- Elastic Email does not document this.
- Last checked in DNS
- 2026-11-11
DKIM for Elastic Email
- Selectors
- api
- How to enable it
- One TXT record on your domain at api._domainkey. Copy the name and value from your Elastic Email account, because the key can change over time.
Elastic Email does not document which domain it signs with
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Elastic Email’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- bounces.elasticemail.net by default, or a subdomain of yours through a custom bounce domain
Sending ranges of Elastic Email
Use these to recognize Elastic Email in your reports. They change over time, so do not copy them into your SPF record.
Elastic Email does not document this.
Does your domain authorize Elastic Email?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Elastic Email documentation
- Elastic Email: How to verify your domain
- checked 2026-11-09
- Elastic Email: What are common SPF errors
- checked 2026-11-09
- Elastic Email: Custom Bounce Domain
- checked 2026-11-09
- Elastic Email: Importance of SPF and DKIM on your domain
- checked 2026-11-09
- Elastic Email: The DMARC Generator Tool
- checked 2026-11-09
How it authenticates
Elastic Email DMARC setup starts under Settings > Domains > Manage Domains. You add your domain there and read the DNS records to publish.
SPF (Sender Policy Framework) lists the servers allowed to send for your domain. It is a TXT record on the domain itself. If you already have one, add the Elastic Email include to it.
DKIM (DomainKeys Identified Mail) signs each message with a private key. Elastic Email generates the key pair, and you publish the public half in a TXT record at api._domainkey.
The bounce address, also called the Return-Path or envelope-from, is the domain SPF is checked against. It defaults to bounces.elasticemail.net. A custom bounce domain replaces it with a subdomain of yours, usually bounces.example.com, published as a CNAME that points to bounces.elasticemail.net.
What to watch for
With the default bounce address, Elastic Email says SPF does not align with your domain. SPF can pass and still not count for DMARC alignment, so set up the custom bounce domain. Under strict mode, set with aspf=s, bounces.example.com no longer matches example.com.
The help center is inconsistent about DKIM. One article says the d= tag, which names the signing domain, should be elasticemail.com, and its sample header shows a customer domain. Send a test message and read the DKIM-Signature header with the email header analyzer. DKIM can only align when d= belongs to your domain.
The error Valid DKIM not found means the DNS record differs from the key in your account. Elastic Email lists three causes: an old value, a shortened value, or a name with the domain added twice.
Check the spelling of _spf.elasticemail.com, because Elastic Email warns that _spf.elasticmail.com is easily mistaken for it. On Cloudflare, turn off the proxy for the bounce CNAME.
Publish a single DMARC TXT at _dmarc if none exists; otherwise preserve its policy and report addresses. It covers all senders, so start at p=none and read reports before enforcement:
v=DMARC1; p=none; rua=mailto:dmarc@example.com