Email reputation is the trust score mailbox providers like Microsoft and Google assign to your domain, and it directly determines whether your emails land in someone's inbox or their spam folder. SPF, DKIM and DMARC are the three technical standards that protect it, and getting them right matters far more than most businesses realise.
What email reputation is
Every domain that sends email builds up a reputation with the major mailbox providers, based on things like how often recipients mark messages as spam, how consistent your sending patterns are, and whether your emails are properly authenticated. A poor reputation doesn't just affect the one email that gets flagged, it can push all your future email towards spam folders, even perfectly legitimate messages to genuine customers.
This is a genuinely common pattern we see: a business runs its primary mailboxes through Microsoft 365, but also has several other services sending email as if it's from their domain, an email marketing platform, third-party integrations, even office equipment like scanners that email documents out. If none of these are properly authorised in the domain's SPF and DKIM records, each one is effectively an unverified source claiming to be you. That doesn't just risk those individual emails being flagged, it can drag down the reputation of the domain as a whole, including the legitimate 365 mailboxes that everything else depends on.
Why this matters more than people think
A damaged reputation is genuinely difficult to fully recover, mailbox providers are slow to trust a domain again once it's been flagged. For a business that relies on email reaching clients, invoices, quotes, appointment confirmations, this isn't a technical footnote, it's a real operational risk.
SPF: who's allowed to send as you
SPF (Sender Policy Framework) is a DNS record that lists which mail servers are authorised to send email on behalf of your domain. When an email arrives claiming to be from your domain, the receiving server checks this list. If the sending server isn't on it, that's a signal the email might not be legitimate.
The catch: SPF alone is easy to misconfigure, particularly for businesses using several different services to send email (a website contact form, a CRM, an accounting platform, standard mailboxes). Each one needs to be included in the record, and it's commonly forgotten when a new tool gets added.
DKIM: proving the email wasn't tampered with
DKIM (DomainKeys Identified Mail) adds a digital signature to outgoing email, generated using a private key only the sending server has access to. The receiving server checks that signature against a public key published in your DNS. If it matches, the receiving server knows two things: the email genuinely came from an authorised source, and nothing in it was altered in transit.
DMARC: telling providers what to do about failures
DMARC (Domain-based Message Authentication, Reporting and Conformance) ties SPF and DKIM together and tells receiving mail servers what to actually do when an email fails those checks: reject it outright, quarantine it (send to spam), or just monitor and report on it without taking action. DMARC also provides reporting, giving visibility into who's sending email using your domain, including any attempts to spoof it.
Without DMARC, SPF and DKIM exist but nothing enforces what happens when they fail, which is a common gap even among businesses who believe they're properly protected.
-
01
SPF
Lists which servers are allowed to send as your domain
-
02
DKIM
Signs each email so tampering or spoofing can be detected
-
03
DMARC
Tells providers what to do when a check fails, and reports on it
How i90 manages this for clients
We set this up as standard for every new Microsoft 365 tenancy we create, it's not an optional extra, it's part of how a mailbox gets switched on in the first place. It's also one of the first things we check and correct on every 365 account we take over from a previous provider, this is an area we consistently find overlooked, accounts that are years old, never audited, effectively set up once and forgotten about by whoever managed them before us.
Beyond the initial setup, we check every 365 account we manage on a quarterly basis. We're also reactive where it matters, if a client reports a bounce-back or an undeliverable message, that gets looked at immediately rather than waiting for the next scheduled check. For clients on non-365 accounts using i90-hosted IMAP, we apply the same principle, though the setup and deployment differs given the different underlying infrastructure.
We also regularly run domains through online mail reputation testing tools for spot checks. These don't just check SPF, DKIM and DMARC, they also flag issues with email content, signatures, links, image alt descriptions, and whether a domain has ended up on any blacklists, all things that can affect deliverability alongside authentication itself.
Why this has gone from best practice to a hard requirement
This isn't just good hygiene anymore. Google and Yahoo made SPF, DKIM and DMARC authentication mandatory for bulk senders (5,000 or more emails a day) from February 2024, and Microsoft followed with its own enforcement from May 2025. For senders at that volume, non-compliant email doesn't get filtered to spam, it gets rejected outright at the point of delivery. Even below that threshold, the direction of travel is the same, Google requires at least SPF or DKIM from all senders, and Yahoo requires both regardless of volume. What used to be a "nice to have" is now, in practical terms, table stakes for reliable email delivery.
Why this ties into everything else we've written about
Email authentication is a quiet, foundational layer underneath a lot of what we've covered before. Spotting a phishing email is about training people to notice a fake, while our phishing simulation testing checks whether that training has actually stuck, but SPF, DKIM and DMARC are what stop attackers convincingly impersonating your domain in the first place. All three work together: one closes the technical gap, the others train the people who'd otherwise fall through it.
Common questions
Do I need all three, SPF, DKIM and DMARC, or is one enough?
All three, ideally. SPF and DKIM each authenticate email in different ways, but neither one tells receiving servers what to actually do when a check fails. DMARC is what enforces that, without it, the other two are more like a suggestion than a real protection.
Will setting up DMARC block my own legitimate emails by accident?
It can, if configured incorrectly or rushed. That's why DMARC has a "monitor only" mode, letting you see what would happen before you switch to actually rejecting or quarantining failing email. A careful, staged rollout avoids this risk.
How do I know if my domain's email reputation has actually been damaged?
Signs include emails increasingly landing in recipients' spam folders, lower open rates than usual, or direct reports from clients that your messages aren't arriving. Mailbox providers also offer reputation monitoring tools that can flag this before it becomes obvious.
Does this affect emails I receive, or only ones I send?
Primarily what you send, SPF, DKIM and DMARC protect your domain's reputation and stop others impersonating you. They don't directly filter what lands in your own inbox, that's a separate layer of spam filtering.
Is this a one-off setup, or does it need ongoing attention?
Both. The initial setup is the foundation, but it needs revisiting whenever a new service starts sending email on your behalf (a new CRM, a new marketing platform), and DMARC reports are worth reviewing periodically rather than set up and forgotten.
Not sure if your domain is properly protected?
Checking and maintaining SPF, DKIM and DMARC is part of how we manage every 365 tenancy we run, whether we set it up from scratch or take it over from a previous provider. If you're not sure where your domain stands, we're happy to take a look.
Get in touch