# SPF record for Elastic Email

URL: https://iblockspam.com/spf/elastic-email
Last updated: 2026-11-03

Include: include:_spf.elasticemail.com
Where it goes: Your domain (@)
DNS lookups: 2 of 10

Elastic Email asks for its include in the SPF TXT record on your domain (host @): its example value is v=spf1 a mx include:_spf.elasticemail.com ~all. If you already have an SPF record, add include:_spf.elasticemail.com to it rather than creating a second one. The include costs 2 DNS lookups.

## Example records

- Elastic Email's example value (TXT, host @): `v=spf1 a mx include:_spf.elasticemail.com ~all` Keep `a` and `mx` only if your own web or mail server sends mail; each costs one lookup.
- Google Workspace and Elastic Email (TXT, host @): `v=spf1 include:_spf.google.com include:_spf.elasticemail.com ~all`
- Microsoft 365 and Elastic Email (TXT, host @): `v=spf1 include:spf.protection.outlook.com include:_spf.elasticemail.com -all`

## Notes

- Elastic Email says most users never add or change MX records for it; an MX warning only means your domain has no mail server set up.
- If no default sender is set and you send from a domain that isn't verified, Elastic Email uses elasticemail.com instead of your domain.
- On 3 November 2026, `_spf.elasticemail.com` published a single `exists` mechanism rather than a list of IP ranges.

## How to add it

- In Elastic Email, go to **Settings > Domains > Manage Domains**, click **Start Verification** and choose your domain.
- At your DNS host, open the TXT record on `@` that starts with `v=spf1` and add `include:_spf.elasticemail.com`. If there is none, create one.
- Add the DKIM TXT record on `api._domainkey` and the tracking CNAME (`tracking` pointing to `api.elasticemail.com`) from the same screen.
- Elastic Email says DNS changes can take up to 48 hours. Then check the status in Manage Domains and the live record with the SPF Checker below.

## DKIM and DMARC

Elastic Email's DKIM record is a TXT key on `api._domainkey`, copied from your account. With SPF and DKIM verified, mail is sent as your domain, and DKIM gives DMARC an aligned pass. Elastic Email strongly suggests a DMARC policy of quarantine or reject once that works. See our [Elastic Email DKIM page](https://iblockspam.com/dkim/elastic-email).

## Common mistakes

- Publishing a second SPF record for Elastic Email. Elastic Email says there can be only one per domain, so add the include to the existing one.
- Pasting Elastic Email's example value over your current record and dropping the includes your mailbox provider needs.
- Leaving the tracking CNAME proxied on Cloudflare. Elastic Email says to switch it to DNS only.

**Q: What is the SPF record for Elastic Email?**
Elastic Email's example is `v=spf1 a mx include:_spf.elasticemail.com ~all` on your domain (host `@`). If your domain already has an SPF record, add `include:_spf.elasticemail.com` to it instead.

**Q: Do I need the a and mx terms in Elastic Email's SPF example?**
Only if your own web server or mail server sends mail for the domain. Elastic Email needs just `include:_spf.elasticemail.com`; `a` and `mx` each cost a DNS lookup, so drop them if they authorize nothing.

**Q: Why does Elastic Email send from elasticemail.com instead of my domain?**
Elastic Email says that when no default sender is set and you send from a domain that isn't verified, it uses elasticemail.com. Verify SPF and DKIM for your domain in Settings, Domains, Manage Domains.

Sources:
- Elastic Email Help Center: How to verify your domain: https://help.elasticemail.com/en/articles/4934400-how-to-verify-your-domain

---

Source: iBlockSpam, https://iblockspam.com/spf/elastic-email (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt