21 June 2026 · 2 min read
Your records are yours, and cancellation is a clean exit rather than a cliff edge. Because DMARC Engine is a DNS-based service, nothing we manage lives inside our application in a way that traps you. Your DMARC policy, your SPF rules, your DKIM selectors, your MTA-STS and BIMI configuration are all expressed as ordinary DNS records that any provider can host. When you cancel, the question is simply where those records live and how lookups resolve, and you have full control over both. We do not delete your DNS or change your policy out from under you on the day a subscription ends; an enforcement policy you have already reached stays in effect because it is published in DNS, not gated behind our login.
How the handover works depends on which setup you chose. If you applied our recommended records directly at your own registrar or DNS host, there is nothing to unwind: those TXT and CNAME entries already sit in your authoritative zone, so cancelling the service changes nothing about how receivers evaluate your mail. If instead you used our hosted delegation, your _dmarc, _mta-sts, default BIMI and policy records resolve through a CNAME that points at us. To take that back in-house you replace each delegated CNAME with the flattened record it currently serves, so the same published values now live in your own zone. We give you the exact target records to paste in before you remove the delegation, which means there is no window where your DMARC, SPF or BIMI silently disappears.
A sensible cancellation runs in this order:
- Export your records. From the dashboard at app.dmarcengine.com you can download the current resolved values for every record we manage: DMARC policy, the flattened SPF, DKIM selectors and keys, MTA-STS policy and BIMI. Keep this as your source of truth.
- Publish them in your own DNS. Paste the exported TXT and CNAME values into your registrar or DNS host so the identical records resolve from your authoritative zone.
- Verify with the free tools. Confirm everything still resolves using the DMARC checker, SPF checker, DKIM checker and BIMI checker before you remove any delegation.
- Remove the delegation, then cancel. Once the checkers show your own zone serving the records, swap out the CNAMEs and close the subscription.
The honest trade-offs are worth stating plainly. Hosted SPF flattening refreshes automatically while you are a customer; once you take SPF in-house, you own the upkeep, and if an upstream sender changes its IPs you update the record yourself. The same applies to DKIM key rotation and to keeping your MTA-STS policy current. Aggregate (RUA) report monitoring and the parsed dashboards stop when the subscription ends, so you would point your rua= address elsewhere or read the raw XML yourself; our DMARC report analyzer remains free if you want to keep eyeballing reports. None of this affects mail flow: your provider, mailboxes and MX records are untouched throughout. If you later decide to come back, see migrating from another DMARC provider, the same delegation step simply runs in reverse.