Understanding DMARC
Hosted records explained
How hosted DMARC, SPF, MTA-STS and BIMI work with a CNAME, and why it makes policy changes painless.
Normally every change to DMARC, SPF, MTA-STS or BIMI means editing DNS at your registrar or DNS host. Hosted records remove that step after the first setup.
How it works
You add a CNAME record that points the relevant name at a record we manage:
_dmarc.example.com CNAME abc123._dmarc.hosted-provider.example
When a receiver looks up your DMARC record, DNS follows the CNAME and returns the record we publish. When you change your policy in the dashboard, we update that record, and the change is live as soon as caches expire.
What can be hosted
- DMARC: policy, subdomain policy, percentage, alignment and report addresses.
- SPF: your authorised senders, kept in one include so you stay under the 10-lookup limit.
- MTA-STS: the policy file and the HTTPS host that serves it, including its certificate.
- BIMI: the BIMI record and your logo file.
TLS-RPT is published as a plain TXT record, because some checking tools do not follow a CNAME for it.
Is it safe?
A CNAME only delegates that one name. Your other records, mail routing and website are unaffected, and you can replace the CNAME with your own TXT record at any time.
See it on your own domain.
Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.
Start free