Have you stopped getting the emails your own website used to send you? The contact form that used to land in your inbox, the appointment request, the new-lead alert, the order confirmation. For a lot of business owners, those notifications quietly went silent this year. The hard part is you usually don’t notice until you start wondering why the inquiries dried up, and by then you’ve already missed real business.
It’s rarely the website that broke. The major inbox providers changed the rules on which email they’ll accept, and a site that delivered those notifications reliably for years suddenly can’t get them through. We’ve been fixing exactly this for clients all year, and the pattern is almost always the same.
What changed
For a long time, the records that prove an email is legitimate were treated as best practice. Recommended, but optional. You could send mail without the full set and it generally arrived.
That began to shift in early 2024:
- Google and Yahoo (February 2024) started requiring senders to authenticate mail with SPF and DKIM, publish a DMARC policy, keep spam complaints low, and offer one-click unsubscribe on bulk email.
- Microsoft (Outlook, Hotmail, Live) followed in 2025 with its own version of the same requirements.
The driver underneath it all is simple: a flood of phishing, spoofing, and AI-generated spam. Forging a business’s email address used to be trivial. The new rules make it much harder by requiring every domain to prove its mail is genuinely its own.
Why it’s only really biting now
Here’s the part that catches people off guard. The rules were announced in late 2023 and took effect in February 2024, but the providers didn’t flip a switch. They rolled it out slowly on purpose, to avoid breaking the world’s email overnight.
At first, non-compliant mail just got a warning or a temporary failure. Then the scope widened, from only the largest bulk senders down toward everyday business volume. And DMARC, which most domains first published in a harmless “just monitor” mode, is now expected to actually be enforced. Each step tightened the screws a little more. By 2026 the grace periods are gone, enforcement reaches far more domains, and mail that squeaked through in 2024 is getting filtered or refused today. That’s why a setup that was “fine” a year ago can quietly stop working now.
Why so many domains need a DNS update, and why that’s nobody’s fault
Worth being clear about: nothing was set up wrong. The standards themselves didn’t change. The inbox providers moved them from “nice to have” to “required,” and then started enforcing them.
Because these records used to be optional, plenty of well-built sites never carried the complete set, especially DMARC, which was rare outside big corporations. There was no reason to add it, because nothing enforced it. Now that enforcement has caught up, those same domains need their DNS brought to the current standard. It’s less like fixing a mistake and more like a solid building meeting a new code that didn’t exist when it went up.
The three records every domain now needs
They live in your domain’s DNS. Think of them as your email’s ID, signature, and rulebook.
- SPF lists the services allowed to send email for your domain. Anything else looks like impersonation.
- DKIM signs each message, proving it really came from you and wasn’t altered along the way.
- DMARC ties the two together, tells inbox providers what to do when a message fails, and shows you who’s sending mail in your name.
The part that often saves money
Here’s something we run into again and again. To get their mail delivered, a lot of businesses were quietly nudged onto paid third-party sending services, an SMTP relay like SendGrid or Mailgun, often just to stop their site’s email from landing in spam. Those services carry a monthly bill that only grows with volume.
In a lot of cases, that expense is no longer necessary. Once a domain’s SPF, DKIM, and DMARC are configured correctly, mail sent straight from your own site and host authenticates and delivers on its own. We’ve brought several clients into compliance and retired the paid SMTP service in the same pass, so they walk away with better deliverability and a smaller monthly bill. Getting compliant and cutting a recurring cost in one move is a rare combination, and it’s become one of our favorite fixes.
Where to start
If your email has been unreliable, or you’re paying for a sending service you’re no longer sure you need, the first step is a quick look at your domain’s current DNS. If you have questions or would like a hand getting it sorted, reach out through our contact page and we’ll point you in the right direction.