Smart DNS Deployment

DMARC deployment without hand-editing DNS.

Palisade publishes your SPF, DKIM, DMARC, BIMI and MTA-STS records into your own DNS, across 50+ providers. You approve the exact record; nothing waits on a ticket.

What Smart DNS Deployment helps you accomplish

The last mile is where DMARC dies

Knowing is not the same as publishing. Palisade's State of DMARC 2026 scan of the top 100,000 domains found 24.1% of domains with DMARC (13,928) collect the reports, can see exactly what is wrong, and still block nothing. The report is not the bottleneck. The DNS edit is.

You approve, Palisade publishes

Every change arrives as a record diff: the value now, the value proposed, and one button. Nothing reaches your zone until you accept it, access covers email-authentication records only, and you can disconnect at any time.

Works across a mixed estate

Free DMARC reporting from a DNS host only helps for the domains already parked there. Palisade recognises whichever provider answers for each domain and publishes there, so a portfolio spread across five registrars is one workflow.

Trusted by leading brands worldwide

Partner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner LogoPartner Logo
Quickstart

Works with the DNS manager you already have

Palisade recognises the provider answering for each domain and publishes there. These are the twelve most common; the full list is below.

  • GoDaddy
  • Cloudflare
  • Namecheap
  • Amazon Route 53
  • Squarespace
  • Wix
  • IONOS
  • Hostinger
  • Bluehost
  • HostGator
  • OVH
  • Network Solutions
See all 64 providers with automatic setup
  • 123-Reg
  • Alibaba Cloud
  • All-Inkl
  • Amazon Route 53
  • Aruba
  • Arsys
  • Bluehost
  • Cloudflare
  • ClouDNS
  • Crazy Domains
  • Domain.com
  • DigitalOcean
  • DNSimple
  • DreamHost
  • Dynadot
  • EasyDNS
  • Enom
  • Fasthosts
  • Freename
  • Gandi
  • GoDaddy
  • GreenGeeks
  • Hetzner
  • Home.pl
  • HostGator
  • Hosting.com
  • Hostinger
  • Hostpoint
  • Hover
  • Inmotion Hosting
  • IONOS
  • IWantMyName
  • LocaWeb
  • Mijndomein
  • Name.com
  • Namebright
  • Namecheap
  • NameSilo
  • Network Solutions
  • Netlify
  • O2switch
  • One.com
  • Openprovider
  • OpenSRS
  • OVH
  • Papaki
  • Porkbun
  • Register.com
  • Register.it
  • Registro.br
  • Shopify
  • Simply
  • SiteGround
  • Spaceship
  • Squarespace
  • Strato
  • TransIP
  • United Domains
  • Vercel
  • Web.com
  • Wix
  • Wordpress.com
  • World4You
  • Xneelo

Counted 2026-08-19. Providers are added upstream, so the list grows without a change here. If yours is not on it, the record is still written out in full for you to paste, and Palisade confirms when it goes live.

How it works

From report to published record

One connection turns every future fix into a review-and-approve.

1

Connect the provider once

Palisade checks which DNS provider answers for the domain and recognises it. You authorise the connection in that provider's own window. No password is shared with Palisade, and access is scoped to the email-authentication records.

2

The Agent drafts the fix

A new sender needs DKIM, an SPF source changed, a policy step is ready. The work arrives as a ticket with the exact record already written, not as a task telling you to go write one.

3

You approve the exact record

The ticket shows the current value and the proposed value side by side. Nothing is published until you accept it, and every approval is recorded.

4

Palisade publishes and verifies

The approved record is written into your own zone through the connection you authorised. Monitoring then confirms receivers can resolve it, so a change that silently failed becomes a ticket instead of a surprise.

At a glance

What access this actually grants

The question every security team asks first, answered before you connect anything.

What Palisade can writeEmail-authentication records only: SPF, DKIM, DMARC, BIMI and MTA-STS. MX, A, CNAME and everything else in the zone are never touched.
Who authenticatesYou do, with your own provider, in that provider's own window. Palisade never asks for, stores, or sees your DNS credentials.
What triggers a writeYour approval, every time. The Agent drafts the record and shows the before-and-after; no record reaches your zone unapproved.
ReversibilityDisconnect the provider whenever you like. Records already published stay in your zone. They are yours, written into your own DNS.
Your registrar and nameserversUnchanged. Nothing is transferred and Palisade never takes over your zone; the records simply stop being typed by hand.
If your provider isn't supportedThe record is still written out in full, ready to paste, and monitoring confirms when it goes live.
What's included

What you get

One-click publishing into your own DNS

Each approved record is written into your zone at your own provider. No values typed by hand.

Automatic provider detection

Palisade works out which provider answers for each domain before you start, so you know which path is open to you.

Record diffs before every write

Current value, proposed value, one approval. The diff is the unit of work, so nothing changes without being read first.

Scoped, revocable access

Email-authentication records only, authorised by you in your provider's window, and disconnectable at any time.

Portfolio publishing for MSPs

200 client domains at five auth records each is 1,000 hand-edits across a dozen provider dashboards, redone every time a sender changes. This is the alternative.

Post-publish verification

Monitoring confirms receivers can resolve each record after it lands, so a change that did not take becomes a ticket.

Teams that stopped copying records by hand.Less DNS work. More domains at enforcement.

Read more
Deliverability: 21% more meetings booked. How gaiia stopped landing in spam.

Deliverability

21% more meetings booked.How gaiia stopped landing in spam.

We increased our meetings booked by 21% and slept better at night knowing our emails are now secured

Marc-André Campagna, CEO, gaiia

Read the case study
gaiia's trade-show booth, its overhead banner reading "grow better with gaiia" above a mint-green wall that says "If your BSS is kind of BS, talk to us."
Questions

Smart DNS Deployment: FAQ

Stop waiting on the DNS ticket

1 domain free up to 1,000 emails/month