A zone cleanup can remove a mail policy
Email services often ask you to publish TXT or CNAME resources in your domain. Losing one of those records during a migration can break the intended setup even though the website still works. Start with the exact names and record types your provider requires.
DNStracr monitors those selected resources. Guided provider templates help you add the required names for supported providers without asking you to monitor the provider's infrastructure behind a CNAME. Saving suggestions still requires you to enable the checks you want.
Example: an SPF include disappears
These fictional values demonstrate a change to review, not a policy you should copy. An include references another policy; the example does not evaluate it.
example.com · TXT
Before: v=spf1 include:_spf.mail.example.test -all
After: v=spf1 -all
Also review: _dmarc.example.com · TXT- List the email services that should send for your domain.
- Monitor the relevant TXT and provider-requested CNAME resources in your own zone.
- Review policy changes against your provider's setup instructions; presence alone does not prove authorization is correct.
- Keep your existing DMARC policy unless an intentional, reviewed change is needed.
SPF and DMARC answer different questions
SPF describes authorized sending sources for the evaluated domain. DMARC adds policy around authentication and alignment; changing an SPF TXT record alone does not establish the effect on every message.
For a provider-requested DKIM resource, monitor the required hostname and record type. You do not need to recreate checks for every provider-managed target behind it. DNS changes are still performed at your DNS provider.
A DNS snapshot is not a deliverability test
The free scan checks MX, basic SPF syntax and DMARC policy. It does not evaluate nested SPF policies, discover DKIM selectors or send a message to test delivery. A published policy cannot establish inbox placement.
Ongoing monitors observe configured DNS resources; they do not validate every outgoing message or replace an email provider's domain verification. Review changes with that provider before strengthening a policy that could affect legitimate mail.
Technical reference: SPF authorization and evaluation — RFC 7208. Reviewed 10 October 2026.
Put this into practice
- Use suggestions and mail checks — Set up mail DNS suggestions and review SPF and DMARC checks.
YOUR NEXT STEP
Monitor the DNS records your mail depends on.
Create an account, add your sending domain and enable the relevant MX, SPF, DKIM and DMARC checks. Choose expectations and a notification target; DNS monitoring does not test actual email delivery.
Create your free accountFree plan: 3 domains, 15 active monitors and 1 member per organization. Minimum check interval: 60 minutes. Paid plans and checkout are not available.
Scan your domain free ↗The free scan reviews public email DNS once. It does not retain an ongoing policy-change history or test email delivery.