21 June 2026 · 2 min read
Yes, absolutely. Keeping your current email provider is the whole point of how DMARC Engine works, and nothing about how you send or receive mail changes. We are a DNS-based service: we do not host your mailboxes, we do not relay or proxy your outbound mail, and we never sit in the path of a message. If you use Google Workspace, Microsoft 365, Zoho, Fastmail, an on-premise Exchange server, or any combination of these, you carry on exactly as before. Your MX records stay pointed at your provider, your users keep the same login, and your inbound and outbound mail flows are untouched.
What we actually configure lives entirely in DNS, in the form of TXT and CNAME records that authenticating receivers (Gmail, Outlook, Yahoo and the rest) read when they evaluate your mail. The DMARC record tells those receivers what policy to apply and where to send aggregate reports. SPF lists which servers are allowed to send for your domain, and DKIM publishes the public keys your provider uses to sign messages. None of these records intercept mail; they are published facts that receiving servers look up. Because of this, you can use as many sending services as you like alongside your main mailbox provider: a marketing platform, a CRM, a help-desk, a billing system, an invoicing tool. The job is to make sure every legitimate sender is correctly aligned and authorised, and that is precisely what taking you from p=none to p=reject does, safely and without blocking your own mail.
A few practical points worth knowing:
- You keep your own DNS, or delegate selectively. You can apply our recommended records yourself at your registrar, or use our hosted delegation for the DMARC, MTA-STS and BIMI records via a CNAME so changes propagate without you touching the zone each time. Either way, your authoritative DNS and your mail provider are unaffected.
- DKIM signing stays with your provider. We do not sign your mail. Your provider continues to sign with its own keys; we simply make sure the published selectors and policy are correct and aligned. If you ever switch providers later, you rotate the relevant records, and nothing else about the setup breaks.
- Switching or adding a provider is straightforward. Migrating from, say, Google Workspace to Microsoft 365 just means updating the SPF and DKIM entries for the new sender. Your DMARC policy and monitoring carry across unchanged.
The only thing that genuinely changes is visibility and protection. Once your DMARC record is live, receivers start emailing aggregate reports showing every source sending under your domain, legitimate or not, and we parse those into a clear view of who is sending your mail. That is how we get you to enforcement without surprises: we watch the real data first, confirm your provider and every other genuine sender pass alignment, then tighten the policy. You can confirm the current state of any domain at any time with our free DMARC checker, SPF checker and DKIM checker, none of which require you to change a single mail setting. In short: keep your provider, keep your mail flow, and let the DNS do the work.