EN FR
Features How it works Pricing Contact Login
🕒 Last updated: September 10, 2026

Point your MX record to Clean Mailbox from OVHcloud

A step-by-step guide to edit your domain's DNS zone in the OVHcloud customer area, so incoming email flows through Clean Mailbox.

⚠️

OVHcloud's customer area changes regularly: the menus, labels and locations described below may differ from what you see today. This guide is provided as a courtesy to help you; it does not replace OVHcloud's own official support, which remains solely responsible for guiding its customers through their DNS zone management.

Why this is needed

Your domain's MX (Mail Exchanger) record tells servers sending you email where to deliver it. For Clean Mailbox to filter spam, phishing, malware and ransomware before it reaches your inbox, your domain needs to advertise Clean Mailbox as the entry point — that's exactly what the MX record does.

This is a one-time configuration at the domain's DNS zone level — not at the mailbox platform level. It doesn't move your mailboxes: whether they're hosted on Microsoft 365, Google Workspace or elsewhere, they stay right where they are. Only the path incoming email takes changes — it now flows through Clean Mailbox before being delivered.

💡

This guide covers changing the MX record from the OVHcloud customer area, for a domain whose DNS zone is managed at OVHcloud. If your domain is registered elsewhere, the fields to fill in (priority, target) stay the same — only the path through the interface differs.

MX value to use

Set the following record in your DNS zone:

PriorityTarget
1 mx.clean-mailbox.com
ℹ️

Unlike the IP address list used for allow-listing on the mailbox side (see the Microsoft 365 and Google Workspace guides), this MX target is a fixed hostname — you won't need to change it if Clean Mailbox's infrastructure evolves.

1

Access your domain's DNS zone

From the OVHcloud customer area, open Web Cloud → Domain names, select your domain, then open the DNS Zone tab. Your records are listed in a table, one row per record; use the search field or the type filter to find the MX rows.

2

Remove the existing MX record(s)

For Clean Mailbox to receive all of your incoming email, the old MX record needs to be removed — leaving it in place alongside the new one (even at a higher priority number) risks letting part of your email bypass Clean Mailbox entirely.

On each MX row, open the actions menu and select Delete entry. If your mailboxes are currently hosted directly at OVHcloud, you'll typically see entries such as mx0.mail.ovh.net (priority 1) and mx1.mail.ovh.net (priority 5) — these are the rows to remove.

⚠️

Only remove this record once you're ready to immediately move on to the next step: a domain with no MX record can no longer receive email.

3

Add the Clean Mailbox MX record

Click Add an entry above the table, then select the MX type. Fill in:

Confirm with Add. Then check in the table that the MX record shown is Clean Mailbox's, and that no other MX record remains.

Verify it works

According to OVHcloud, a DNS zone change typically takes between 4 and 24 hours to propagate. Once that window has passed, check propagation with the following command (Terminal on macOS/Linux, or PowerShell on Windows):

dig MX yourdomain.com +short

Replace yourdomain.com with your own domain name. The result should show 1 mx.clean-mailbox.com. and nothing else. If the old value still appears, wait a little longer — that's the old record's TTL expiring across DNS resolvers.

💡

For a more visual check, including propagation as seen from multiple resolvers worldwide, you can also use an online DNS propagation checker.

Next step: configure your mailbox platform

Pointing the MX at Clean Mailbox isn't enough on its own: once this step is done, your mailbox platform needs to be configured to trust Clean Mailbox as an inbound source, to avoid delivery issues caused by SPF and DMARC.

Frequently asked questions

Can I keep my old MX record too, "just in case"?

No. As long as another MX record stays active, part of your incoming email can keep being delivered directly to your old server, entirely bypassing Clean Mailbox's filtering. Only one MX record — Clean Mailbox's — should remain in place.

Does this move my mailboxes?

No. The MX record only defines the entry point for incoming email; your mailboxes stay hosted wherever they are today (Microsoft 365, Google Workspace, OVH Exchange, etc.). Clean Mailbox then relays the filtered email on to that same platform.

Do I also need to change my SPF record?

SPF governs authentication of your outgoing email and doesn't need to change for this inbound MX configuration. That said, once the MX is in place, follow the mailbox platform guide above — domains with a strict SPF/DMARC policy need a bit of extra configuration so that email relayed by Clean Mailbox isn't wrongly blocked.

Questions about this configuration?

Our support team can help you with the MX value to use or check propagation. For the management of your DNS zone itself, please reach out to OVHcloud support.

Contact Clean Mailbox →

Let's protect your mailbox.

Questions about the trial, setup, pricing, or a partnership? We're here — and we answer fast.

30-day free trial, no card required
Works with any mail server
Setup in under 5 minutess
Infrastructure based in France 🇫🇷