SPF flattening & hosted records
Your SPF record has ten DNS lookups. Most domains quietly run out.
Every include: you add spends one of them. Go over and receivers stop evaluating your record — not with an error anyone sees, but as a permerror that many spam filters score the same as having no SPF at all.
No signup, nothing saved. Or on the same domain.
Preview
Paste a domain and see its current SPF record, its lookup count, and which senders it points at — no signup required.
Flatten
Safe, non-critical senders collapse into direct ip4/ip6 mechanisms. Large, frequently-changing providers (Microsoft 365, Google Workspace, SES…) stay as includes so mail doesn't silently break when their ranges rotate.
Host it (optional)
Point an include: or redirect= at a token we manage, and we keep the flattened record fresh on our own DNS as your senders change — no manual re-flattening every time a provider updates its ranges.
Why a broken SPF record is hard to notice
Exceeding the lookup limit doesn't fail loudly. Receiving servers treat the record as a permerror and many filters score that the same as no SPF at all, which silently weakens your deliverability and your resistance to spoofing — usually until mail starts landing in spam and nobody can say when it started.