Home/Notes/SPF: a field note from a bakery
SPF: a field note from a bakery
30 Jan 2025
How a bakery deals with SPF — and what usually goes wrong.
The problem: a lastmod stamp that never changes. The SPF check fails for a bakery.
We solved SPF for a bakery by moving it behind a reverse proxy. The old configuration stayed live as a fallback for forty-eight hours, then we pulled it.
Big agencies solve SPF with a team. We solve it with a checklist and a dig command. The result is the same; the invoice is shorter.
We keep a playbook for SPF. Step one is always the same: pull the live record with dig, compare it to what the admin panel shows, and fix the mismatch.
Search consoles like honest sitemaps. Every loc should be a document. Reserving ten thousand empty shells and hoping Google does not notice is not a strategy for SPF.
We moved SPF for a bakery to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com