DMARC setup, by DNS provider
Publish DMARC on the host that actually answers for your domain, by hand or from the AI assistant you already use. Palisade returns the exact records and confirms them against live DNS.
All four publish the same thing: one TXT record at _dmarc. What changes is which nameservers answer for your domain. Run dig NS yourdomain.com and match the result.
Cloudflare
ns.cloudflare.com
A domain on Cloudflare's partial (CNAME) setup keeps its old nameservers, so detection reports whoever still answers for the zone rather than Cloudflare.
GoDaddy
domaincontrol.com
Buying a domain at GoDaddy does not mean GoDaddy hosts its DNS. Plenty of GoDaddy registrations point their nameservers at Cloudflare or Route 53.
Namecheap
registrar-servers.com
Namecheap's own nameservers cover BasicDNS, PremiumDNS and FreeDNS. A domain switched to Custom DNS answers from somewhere else entirely.
Amazon Route 53
awsdns-NN.com / .net / .org / .co.uk
Route 53 hands a domain four nameservers across different top-level domains. All four belong to the same delegation set, and detection expects all of them to be present.
Somewhere else? Palisade works the same way whatever hosts the zone, and Smart DNS Deployment publishes approved records into your own DNS across 64 providers. The full list is on Smart DNS Deployment.
Set up DMARC from the assistant you already use
1 domain free up to 1,000 emails/month