Why Microsoft Reports an MX Error — and Why It Is Not a Problem
In the Microsoft 365 administration interface, the DNS Records section automatically checks whether the domain’s public MX record points to Microsoft Exchange Online servers (*.mail.protection.outlook.com). If it does not, Microsoft displays an error.
In your domain’s case, this warning is normal and expected.
The domain is protected by Secuserve’s e-securemail solution. Therefore, the MX records have been intentionally configured to point to the e-securemail filtering gateways, which inspect and relay incoming email traffic before forwarding it to Exchange Online.
This is the standard behavior of an inline filtering architecture:
Internet → e-securemail MX (filtering) → Microsoft Exchange Online
Microsoft is unaware of this intermediate filtering layer. It simply expects to see its own MX record as the public entry point, just like any standard DNS verification tool would. This is exactly the same logic we apply on the Secuserve side for domains hosted on Optimails or SHEX.
This warning does not indicate any malfunction. Email services are operating correctly, and no action is required on the DNS records.