To set up DMARC on OVHcloud, add a DMARC entry on the _dmarc subdomain in your domain's DNS zone, with the value v=DMARC1; p=none; rua=mailto:your-address. Do it only after SPF is in place and DKIM is turned on, then tighten the policy over a few weeks.
DMARC tells mailbox providers what to do with an email that claims to come from your domain without proving it. Set up well, it protects your name against spoofing and helps your real messages get past spam filters. This guide follows the English OVHcloud Control Panel, as documented in OVHcloud's help on November 13, 2026.
Before you start: SPF and DKIM
DMARC builds on the other two checks. OVHcloud asks for SPF or DKIM to be configured in the DNS zone first; in practice, aim for both.
SPF
For an OVHcloud shared email plan (MX Plan, Email Pro, Hosted Exchange), the value OVHcloud gives is v=spf1 include:mx.ovh.com ~all. If other services send with your domain, add their include: to this same record: a domain must have only one SPF record. Check yours with our free SPF checker.
DKIM
DKIM is turned on from your email service, not from the DNS zone:
- MX Plan: MX Plan > domain > General information tab > red DKIM badge > confirm;
- Email Pro: Email Pro > service > Associated domains tab > DKIM badge > confirm;
- Exchange: MICROSOFT section > Exchange > service > Associated domains > DKIM badge > confirm;
- Zimbra: Zimbra Mail > Domain tab > ⋮ menu > Diagnostics > DKIM tab.
OVHcloud's English guide calls the confirmation button Validate in one place and Enable in another: click whichever your screen shows. If the DNS zone is at OVHcloud in the same account, the records are created for you. Otherwise, OVHcloud shows two CNAME records to add at your DNS provider before you confirm. Allow 30 minutes to 24 hours; the badge then turns green.
Google advises waiting 48 hours after setting up SPF and DKIM before adding DMARC, so everything has time to propagate.
Step 1: prepare an address for reports
Mailbox providers that apply DMARC send daily XML reports to the address in rua. Create a dedicated address, such as [email protected], so the reports do not clutter a working inbox.
If that address is on a different domain from the one you protect, that other domain must publish a specific DNS authorization (the external destination verification rule of the DMARC standard). The simplest option is an address on your own domain.
Step 2: add the DMARC record
- In the Control Panel, go to Web Cloud > Domain names and select your domain.
- Open the DNS zone tab.
- Click Add an entry, then choose DMARC.
Fill in the form. OVHcloud's guide describes these fields:
- Subdomain:
_dmarc(OVHcloud adds your domain); - Version:
DMARC1; - Rule for the domain (p=):
noneto start; - Percentage of filtered messages (pct=): leave
100; - URI for global reporting (rua=):
mailto:[email protected]; - Rule for subdomains (sp=): leave empty, so the domain rule applies;
- Alignment mode for SPF (aspf=): leave
r(relaxed).
- Subdomain:
- Confirm.
Only "Subdomain" is quoted as an on-screen label in OVHcloud's English guide; the other names are the guide's own descriptions, so the form may word them slightly differently.
You end up with a record equivalent to:
_dmarc.yourdomain.com. TXT "v=DMARC1; p=none; pct=100; rua=mailto:[email protected]; aspf=r"Alternative: enter a full TXT record
The DMARC form does not offer every option. To set DKIM alignment (adkim), request failure reports (ruf) or other tags, choose the TXT type instead, keep _dmarc as the subdomain and paste the full value. Use only one method: two DMARC records on the same name are ignored by mailbox providers.
Check your domain for free. AttackScout reads your DMARC, SPF and DKIM records, flags a duplicate or a weak policy, then gives you the exact line to enter at OVHcloud. Run the free check
Step 3: tighten the policy gradually
p=none does not protect anything yet: it only observes. The goal is to reach quarantine (unauthenticated emails go to spam), then reject (they are refused).
- Start with
p=nonefor one to several weeks (Google says at least a week, OVHcloud says several): read the reports. Identify every service that sends with your domain and check that it passes SPF or DKIM with the right domain. - Then move to
p=quarantine: once the reports show only your legitimate senders, all passing. OVHcloud and Google both recommend this step-by-step approach. - Finally,
p=reject: if you want the strongest protection and nothing legitimate has failed for several weeks.
What about pct?
OVHcloud offers the pct field to apply the policy to only part of your messages, and Google still recommends it during rollout. But the updated DMARC standard published in May 2026 (RFC 9989) removed that tag. Many mailbox providers still read it, but do not rely on it alone: the real safeguard is reading your reports before each step.
Step 4: check that the record is published
After a few minutes to a few hours, check from a terminal:
nslookup -type=TXT _dmarc.yourdomain.comThe answer should contain a single line starting with v=DMARC1. You can also use our free DMARC checker, which also checks the policy and the report addresses.
For a full test, send an email to a Gmail address, open it, then choose Show original: SPF, DKIM and DMARC should all show PASS.
Common mistakes
- Doubled name: typing
_dmarc.yourdomain.comin the "Subdomain" field gives_dmarc.yourdomain.com.yourdomain.com. Enter only_dmarc. - Two DMARC records: a forgotten old TXT record plus a new DMARC entry. Filter the zone on
TXTandDMARCand keep only one. - Moving to
rejecttoo early: invoices sent by outside software or your newsletter may be refused. Read the reports first. - Skipping DKIM: with SPF alone, an email forwarded by a third party often fails DMARC. DKIM makes it more robust.
- A
ruaaddress withoutmailto:: the prefix is required.
Are your emails already going to spam? See our step-by-step guide to OVH emails going to spam.
Frequently asked questions
How long until DMARC is active at OVHcloud?
The entry is saved right away. Mailbox providers pick it up once DNS propagates: from a few minutes to a few hours, depending on the cache duration (TTL) of the old value.
Do I need DMARC on every subdomain?
No. Without sp=, the main domain's policy also applies to subdomains. Add a record on a subdomain only if it needs a different rule.
What do I do with DMARC reports?
They are XML files that are hard to read. Open a few to spot the IP addresses and services sending with your domain, or hand them to a report analysis tool.
Check your domain for free. In under a minute and without an account, AttackScout tells you whether your DMARC record really protects your domain, and what to fix next. Check my domain
Technical details
Exact configuration. A TXT record on the _dmarc name of your domain:
_dmarc.your-domain.com TXT "v=DMARC1; p=none; rua=mailto:[email protected]"Why. DMARC (RFC 7489) tells the receiving server what to do with an email that claims to come from your domain but passes neither SPF nor DKIM with that same domain name (alignment). p=none observes without blocking; p=quarantine sends to spam; p=reject refuses. rua receives the aggregate reports that show who sends in your name: tighten the policy only after reading them.
To check it yourself. Exactly one line must start with v=DMARC1:
dig +short TXT _dmarc.your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7489
Sources
Accessed November 13, 2026, unless stated otherwise.
- OVHcloud documentation, DMARC record guide: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-dmarc
- OVHcloud documentation, DKIM record guide: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-dkim
- OVHcloud documentation, SPF record guide: https://docs.ovhcloud.com/en/guides/web-cloud/domains/dns-zone-spf
- IETF, RFC 7489 (DMARC, 2015): https://www.rfc-editor.org/rfc/rfc7489.html
- IETF, RFC 9989 (DMARC, May 2026, replaces RFC 7489): https://www.rfc-editor.org/info/rfc9989
- Google Workspace, Set up DMARC (accessed November 12, 2026): https://knowledge.workspace.google.com/admin/security/set-up-dmarc
- Google Workspace, Recommended DMARC rollout: https://knowledge.workspace.google.com/admin/security/recommended-dmarc-rollout