# SPF record for Rackspace Email

URL: https://iblockspam.com/spf/rackspace-email
Last updated: 2026-10-22

Include: include:emailsrvr.com
Where it goes: Your domain (@)
DNS lookups: 1 of 10

Rackspace's example SPF record for Rackspace Email is v=spf1 include:emailsrvr.com ~all, a TXT record on host @ with a TTL of 3600. If other providers also send mail for your domain, Rackspace says to put their sending servers in the same SPF record and never to create more than one. The include costs 1 DNS lookup.

## Example records

- Rackspace Email only (Rackspace's example) (TXT, host @): `v=spf1 include:emailsrvr.com ~all`
- Rackspace Email and Microsoft 365 (for example during a migration) (TXT, host @): `v=spf1 include:emailsrvr.com include:spf.protection.outlook.com ~all`
- Rackspace Email and Zendesk (TXT, host @): `v=spf1 include:emailsrvr.com include:mail.zendesk.com ~all`

## Notes

- Rackspace documents SPF in its DNS record definitions; the example uses `~all` and the article doesn't discuss `-all`.
- Rackspace says DKIM is enabled automatically if you manage the domain's DNS in the Cloud Office Control Panel. Otherwise you add a DKIM TXT record yourself and click Verify TXT Record.

## How to add it

- Sign in where your domain's DNS is hosted. If Rackspace hosts it, edit the zone in the Cloud Office Control Panel; otherwise use your registrar or DNS provider.
- Look for an existing TXT record on `@` that starts with `v=spf1`.
- If there is one, add `include:emailsrvr.com` to it. If there isn't, create a TXT record on `@` with `v=spf1 include:emailsrvr.com ~all` and a TTL of 3600, as in Rackspace's example.
- Save, then check the live record with the SPF Checker below.
- Next, turn on DKIM in the Cloud Office Control Panel (Domains, Sender Authentication (DKIM)) and add a DMARC record. Rackspace recommends doing SPF, then DKIM, then DMARC.

## DKIM and DMARC

Rackspace signs new outgoing mail with your domain's DKIM key once you enable it under Sender Authentication (DKIM) in the Cloud Office Control Panel. It allows about 15 minutes to create the record and 24 to 48 hours for it to propagate. After that, publish a [DMARC record](https://iblockspam.com/blog/dmarc-record-examples).

## Common mistakes

- Publishing a second SPF record for another sender. Rackspace says not to create multiple SPF records; merge the includes into one.
- Stopping at SPF. Rackspace's own order is SPF, then DKIM, then DMARC.

**Q: What is the SPF include for Rackspace Email?**
`include:emailsrvr.com`. Rackspace's example record is `v=spf1 include:emailsrvr.com ~all`, published as a TXT record on `@` with a TTL of 3600. Other senders' includes go into the same record.

**Q: How do I turn on DKIM for Rackspace Email?**
In the Cloud Office Control Panel, open Sender Authentication (DKIM) under Domains, pick the domain and enable DKIM. If Rackspace hosts your DNS, it's automatic; otherwise add the TXT record shown and click Verify TXT Record.

**Q: Does include:emailsrvr.com use many DNS lookups?**
No. We measured it at 1 lookup on 22 October 2026, because the record lists IP ranges and nests no further includes. That leaves plenty of room for other services in the same record.

Sources:
- Rackspace Docs: DNS record definitions: https://docs.rackspace.com/docs/dns-record-definitions
- Rackspace Docs: Enable DKIM in the Cloud Office Control Panel: https://docs.rackspace.com/docs/enable-dkim-in-the-cloud-office-control-panel

---

Source: iBlockSpam, https://iblockspam.com/spf/rackspace-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