SPF flattening that stays under the 10-lookup limit

SPF allows at most ten DNS lookups per evaluation, and every include, a, mx, or redirect mechanism spends one — nested includes spend more behind your back. Flattening resolves that tree into a compact record so receivers can evaluate it inside the budget. Palisade hosts the flattened result behind one include you publish once.

Receivers stop evaluating and return permerror. That means SPF neither passes nor fails cleanly — and under DMARC, mail that can't pass SPF has to lean entirely on DKIM. If DKIM has a gap too, your own legitimate mail starts failing authentication.

DMARC passes when SPF or DKIM passes and aligns with your domain. An over-limit SPF record silently removes one of those two paths for every sender you have. Getting the record under the limit is often one of the first tickets on the way to enforcement.

That's the classic risk of do-it-yourself flattening: you copy a provider's addresses once and they drift. With hosted SPF the record behind the include is maintained by Palisade, so you're not hand-tracking provider changes at the registrar.

No. You publish one TXT record with the Palisade include at your existing provider — same as any other SPF record. Your registrar and DNS host stay exactly where they are.

Yes. The include is built from the senders you've confirmed in Palisade. New sources show up as tickets to review, and nothing joins your SPF without your approval.