SPF (Sender Policy Framework) is a single DNS record that lists which servers are allowed to send mail for your domain. When receivers see something outside that list, they treat it as suspicious.
It does not forward your mail or expose it. DMARCFlow simply keeps the list tidy so the good senders stay in and everything else gets flagged.
How it works
Receivers compare the server that delivered your email with the list in your SPF record. That’s it.
We document every platform that sends mail (Microsoft 365, CRM tools, invoice systems) and add them to the SPF record.
When Gmail or Outlook receives a message, it checks if the connecting IP appears in your SPF list.
DMARC uses the SPF result to decide whether a suspicious message should be monitored, quarantined, or rejected.
We map out every service, keep the DNS entry under the 10-lookup limit, and monitor changes so nothing breaks.
SPF might be outdated or missing senders, so spoofed mail slips through.
We stage a cleaned-up record in monitor mode, add missing services, and remove dead includes.
You receive change logs and alerts whenever a new tool needs to be added. Email delivery keeps working as before.
Privacy promises
The SPF record is just a list of permitted hosts. DMARCFlow edits that list—it never sees who you email or what you send.
All information stays at the DNS layer.
We work with TXT values, not inboxes.
Mail continues to travel directly from your provider to the recipient.
Rolling back takes one DNS edit. There is no software lock-in.
We document every include, mechanism, and timestamp.
Next step
Let DMARCFlow map, clean, and monitor it so you never worry about delivery or privacy.