In short. SPF (the list of servers allowed to send email with your domain) tells receiving mailboxes which senders are genuine. If it is missing or wrong, your messages can land in spam or be refused. You can do it yourself, or ask whoever manages your domain if that is a provider or agency. It takes a few minutes of setup, then OVHcloud says 4 to 24 hours for the change to take full effect.
To set up SPF on OVHcloud, open the DNS zone of your domain in the Control Panel, click Create a record, choose the SPF type and enter @ as the subdomain. For an OVHcloud email offer (MX Plan, Email Pro, Hosted Exchange), the value to end up with is v=spf1 include:mx.ovh.com ~all. If an SPF record already exists, edit it instead of creating a second one.
SPF tells mailbox providers which servers may send email with your domain. Without it, your messages are more often classed as spam, and DMARC cannot work properly.
Last verified: November 18, 2026, against OVHcloud's official English documentation.
Before you start: list your senders
One SPF record must cover everything that sends email with your domain. Note down, before touching the DNS zone:
- your mailboxes (OVHcloud, Microsoft 365, Google Workspace);
- your website, if it sends email (contact form, shop);
- your sending tools: newsletter, invoicing, booking, CRM.
Each tool gives the include: to add in its own help. For example, Google Workspace gives include:_spf.google.com and Microsoft 365 include:spf.protection.outlook.com. See our guides on SPF for Google Workspace and Microsoft 365.
These steps apply only if your domain uses OVHcloud DNS servers. OVHcloud says you can check this in the DNS configuration section of the domain's Overview tab. Otherwise, make the change at the provider that hosts your DNS zone.
Step 1: check whether an SPF record already exists
- In the Control Panel, go to
Web Cloud>Domains & DNS>Portfolioand select your domain. - Open the
DNS zonetab. - Filter by
TXT, then bySPF: OVHcloud says the record can appear under either type. Look for a value starting withv=spf1.
If there is one, go to Step 3 to edit it. If there are two, keep one and merge their include: entries.
Step 2: add the SPF record
- In the
DNS zonetab, click Create a record above the table. - Choose the type SPF (described as "Servers allowed to send emails").
Fill in the form:
- Subdomain: mandatory. Enter
@for the whole domain; - Include OVH email servers (include:mx.ovh.com): ticked by default, keep it if your mailboxes are at OVHcloud;
- Allow domain MX servers (mx) and Allow the domain's IP address (a): tick only if those servers really send email;
- Additional servers to authorise (include): add your other services, for example
_spf.google.com; - SPF policy:
~all("Accept but mark as suspicious", preselected and marked Recommended) to start; - TTL: By default.
- Subdomain: mandatory. Enter
- Check the Record preview, then click Add.
For an MX Plan alone, the preview should show:
v=spf1 include:mx.ovh.com ~allWith Google Workspace as well, it would look like:
v=spf1 include:mx.ovh.com include:_spf.google.com ~allVariant: type the full value
If you prefer to write the string yourself, choose the TXT type ("Free text") and paste the value in the Value field (the form also has an "Advanced mode" option). Use only one of the two methods: an SPF entry and a v=spf1 TXT entry on the same name make two SPF records.
Step 3: edit an existing SPF record
- On the row of the record, click the
⋮button in the Actions column. - Click
Modify. The row expands into an edit form. - Add the missing
include:before~allor-all, then confirm.
Private Exchange is different: OVHcloud says to declare the server's ip4 and ip6 addresses (for example v=spf1 ip4:203.0.113.1 ip6:2001:db8::1 ~all), and to add include:mx.ovh.com if you also use a shared email service. You find the IPs on the Overview tab of the Exchange service.
Step 4: check it works
OVHcloud says changes can take 4 to 24 hours to take full effect. Then, from a terminal:
nslookup -type=TXT yourdomain.comExactly one line must start with v=spf1. Our free SPF checker also checks the number of DNS lookups.
From ~all to -all
~all(soft fail): an unlisted server is suspicious, but the message is usually not refused. It is the right setting until you are sure you have listed every sender.-all(hard fail): an unlisted server should be refused. OVHcloud recommends it for stronger protection, but only once every legitimate sending source is listed.
Move to -all when your DMARC reports have shown for several weeks that every legitimate sender passes SPF. If you do not have DMARC yet, follow our guide on setting up DMARC on OVHcloud.
Known pitfalls
- Two SPF records: an old forgotten TXT plus a new SPF entry. The standard requires a single record: with two, SPF fails with an error for everyone.
- The 10-lookup limit: every
include:,a,mxorredirectcosts at least one DNS lookup, and includes often call others. Past 10, SPF fails with an error. Remove services you no longer use, and untickaandmxif they do not send email. - The domain typed in full: use
@in Subdomain. Typingyourdomain.comrisks a name likeyourdomain.com.yourdomain.com. - An
include:afterall: everything after~allor-allis ignored. - Moving to
-alltoo early: a forgotten invoicing tool would have its email refused.
Is your mail already going to spam? Also read why OVH emails go to spam.
Frequently asked questions
My website is at OVHcloud but my email is at Microsoft 365. Which SPF?
The Microsoft 365 one, plus OVHcloud only if your hosting also sends email (forms). For example v=spf1 include:spf.protection.outlook.com include:mx.ovh.com ~all.
Is SPF enough to stop landing in spam?
No. SPF is the first of three checks. Enable DKIM too, then publish DMARC. Gmail and Outlook.com require all three from senders of more than 5,000 messages a day.
How long before the change takes effect?
OVHcloud says 4 to 24 hours. The delay mostly depends on the cache duration (TTL) of the old value.
Verify it's fixed. AttackScout reads your SPF record from the internet, counts DNS lookups, spots duplicates and tells you whether your domain is ready for DMARC. Free, no account needed. Verify it's fixed
Technical details
Exact configuration. A single TXT record at the root of the domain, starting with v=spf1 and ending with an all mechanism:
v=spf1 include:<service-that-sends-your-email> ~allWhy. SPF (RFC 7208) lists the servers allowed to send email for your domain. The receiving server reads this TXT record and counts at most 10 DNS lookups (include, a, mx, exists, redirect): beyond that the result is permerror and SPF protects nothing. Two SPF records also give permerror. ~all flags without rejecting; -all makes receivers reject anything not listed.
To check it yourself. Exactly one line must start with v=spf1:
dig +short TXT your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7208
Sources
Accessed November 18, 2026.
- OVHcloud, Improving email security with an SPF record: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-spf
- OVHcloud, Improving email security with a DMARC record: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-dmarc
- IETF, RFC 7208 (SPF), section 4.6.4 on the 10-lookup limit: https://www.rfc-editor.org/rfc/rfc7208
- Google Workspace, Set up SPF: https://knowledge.workspace.google.com/admin/security/set-up-spf
- Microsoft Learn, Set up SPF for your Microsoft 365 domain: https://learn.microsoft.com/en-us/defender-office-365/email-authentication-spf-configure
- Google, Email sender guidelines: https://support.google.com/mail/answer/81126?hl=en