Adding an SPF record to the configuration of your domain name
Find out how to configure an SPF record for your OVHcloud domain name
Find out how to configure an SPF record for your OVHcloud domain name
Last updated 7th April 2021
Sender Policy Framework (SPF) allows a receiving server to verify that an email was sent by an authorised sender.
The authorisation is made possible by information included in the SPF itself. It consists of
When configuring an SPF, make sure to include all the sending sources for the emails of this domain in the SPF record. These sources might be your own servers, your provider's, or those of OVHcloud's email solutions.
Albeit a commonly accepted measure, an SPF record can only be a recommendation to servers that receive emails. It then lies within the server's responsibility whether to apply the policy as specified in the domain's SPF record.
This guide explains how to configure an SPF record for your OVHcloud domain name.
If your domain name does not use OVHcloud DNS servers, you will need to modify the SPF record using the interface of the service provider managing your domain name's DNS.
If your domain name is registered with OVHcloud, you can check if it is using the OVHcloud configuration in your Control Panel. Click on the DNS servers
tab of your domain name.
If you are using OVHcloud email accounts, we recommend using an SPF record with OVHcloud information in your domain name's DNS zone. It looks like this:
mydomain.ovh IN TXT "v=spf1 include:mx.ovh.com ~all"
If your domain uses OVHcloud DNS servers, you can check if an SPF record is already configured for it. Log in to the OVHcloud Control Panel and switch to Web Cloud
in the top navigation bar. In the Domains
section, select the domain name concerned. Click on the DNS zone
tab.
The table on this page displays your domain name's DNS zone at OVHcloud. Each DNS record is represented by one line in the table.
In case of doubt, verify that your domain is actually using OVHcloud DNS servers from the DNS servers
tab.
To find the row for the OVHcloud SPF record, a display filter can be applied to the table. Since the record can appear in two different places, select both the TXT
and the SPF
filter. You will receive one of the follwing results.
An SPF record that corresponds to OVHcloud email solutions is displayed: Your domain currently uses the OVHcloud configuration. If you no longer wish to use it, you must modify it in the next step.
An SPF record that does not match the OVHcloud configuration is displayed: Your domain already uses a custom SPF. If your configuration is incorrect, you will need to modify it. You can modify it or choose the OVHcloud configuration in the next step.
An SPF record does not appear in the target column: First check that the record does not actually exist as SPF or TXT by changing the filtering. If no SPF record is displayed in the zone at all, your domain does not use one. You can add it in the next step.
An SPF record always follows this form: "v=spf1 sources
qualifier
". For example, the OVHcloud SPF is: "v=spf1 include:mx.ovh.com ~all".
Log in to the OVHcloud Control Panel and switch to Web Cloud
in the top navigation bar. In the Domains
section, select the domain name concerned. Click on the DNS zone
tab.
To add an SPF record, click on Add an entry
in the right-hand menu.
In the window that pops up, the configuration assistant offers several different types of DNS records. There are two ways of adding an SPF record:
The configuration wizard enables you to customise your SPF record according to your needs. In order to apply your settings, answer the questions on this page. Some information requested may be aimed at advanced users. Please refer to the tables below for details.
Details | Description |
---|---|
Subdomain | Fill out if the SPF record must be applied to a subdomain of your domain, i.e. if you send emails from a subdomain. |
TTL | This is the propagation time that will apply to the configuration of this DNS record. |
Authorise an IP address to send emails | Check this box if your website and email addresses are hosted on a server using the same IP address (for example on a dedicated server). |
Authorise the MX servers to send emails | Tick if the servers that receive your emails can also send them. |
Authorise all servers with names ending with your domain to send emails | This option should be used with caution, as it allows a very wide legitimisation of the sending sources using your domain name. |
Regarding the question: "Do the emails of your domain originate from other servers belonging to other domains?", several values can be provided:
Details | Description |
---|---|
a | Enter domain names here to legitimise these servers to send emails with your addresses. |
mx | Enter the servers that receive your emails (MX servers) here if they can also send them. They will thus be identified as a legitimate sending source. |
ptr | Enter the host names for which the reverse path works (using a PTR record in the DNS zone). They will thus be identified as a legitimate sending source. |
ip4 | Indicates IP addresses or RIPE blocks (IPv4) authorised to send emails with your addresses. |
ip6 | Indicates IP addresses or RIPE blocks (IPv6) authorised to send emails with your addresses. |
include | Enter domain names here that include their own SPF rules. This will enable these for your own domain. For example, OVHcloud uses this method in its SPF configuration: "v=spf1 include:mx.ovh.com ~all". It allows OVHcloud to manage the SPF of mx.ovh.com and let customers use it for their services. |
Regarding the question: "Does the data you have entered describe all hosts that send email from your domain?", three choices are possible:
Details | Description |
---|---|
Yes, I am sure | Specify that servers receiving emails from your domain should reject them if they come from illegitimate sources (not present in your SPF record). |
Yes, but use safe mode | Specify that servers receiving emails from your domain should accept them if they come from illegitimate sources (not present in your SPF record), but tag them as potentially not legitimate (as spam, for example). |
No | Specify that servers receiving emails from your domain should accept them if they come from illegitimate sources (not present in your SPF record), without any particular action. The email header will however be increased. |
Once finished, click on Next
and verify that the values you have entered are correct by clicking Confirm
.
It can take between 4 and 24 hours until the configuration is fully effectual.
Choose the SPF
type record and then click on the Use the SPF for OVHcloud web hosting
button. In the following step, click on Confirm
to approve the action.
It can take between 4 and 24 hours until the configuration is fully effectual.
Choose the TXT
type record and enter the requested information. In the Value
field, enter the full SPF string for your domain.
Click on Next
and verify that the SPF you have entered is correct by clicking Confirm
.
It can take between 4 and 24 hours until the configuration is fully effectual.
Log in to the OVHcloud Control Panel and switch to Web Cloud
in the top navigation bar. In the Domains
section, select the domain name concerned. Click on the DNS zone
tab.
The table on this page displays your domain name's DNS zone at OVHcloud. Each DNS record is represented by a line in the table. Locate your TXT or SPF record in this table and click on the ...
button to edit the entry.
Refer to the guide section above if you need more information about editing the SPF record.
Editing the DNS servers for an OVHcloud domain name
Join our community of users on https://community.ovh.com/en/.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community