.png)
Start by opening the Settings tab on the left side of the Palisade dashboard, select “Verified Senders,” and click “Add Sender Domain.” This registers your domain for authentication.
Palisade provides three CNAME records. The first points to return.palisade.email for SPF alignment, the second secures DKIM signing, and the third handles click/open tracking (optional).
Copy the SPF CNAME value and add it to your DNS host (e.g., Cloudflare) as a CNAME pointing to return.palisade.email. This ensures your domain inherits the provider’s whitelisted IPs.
Similarly, add the DKIM CNAME to your DNS. This enables cryptographic signing of outgoing mail, improving deliverability.
No. Palisade’s SPF CNAME works alongside your current SPF record, preserving alignment without extra changes.
The third CNAME handles tracking links for opens and clicks. You can add it if you want detailed engagement metrics, but it’s optional for basic authentication.
Use Palisade’s Email Investigation tool to run a live test. It checks the SPF and DKIM status and reports any issues.
Double‑check the CNAME values for typos, ensure they are saved as CNAME (not A) records, and allow DNS propagation (usually up to 48 hours).
If you already have a DMARC policy, keep it. Adding another DMARC record will cause conflicts because a domain can only have one.
Reach out to Palisade’s email security experts for personalized assistance.
.svg)