Email Deliverability Audit: Find Out Why Your Mail Is Being Filtered
Most deliverability problems are not mysterious. They are a handful of DNS records that were set up once, never revisited, and are now quietly telling inbox providers to distrust your mail. A deliverability audit is the diagnostic that finds out which ones, before you spend another month wondering why engaged subscribers stopped opening.
Quick answer: what does an email deliverability audit check?
An audit inspects the authentication and routing records that inbox providers read before they decide where your mail lands: SPF, DKIM, DMARC, MX and BIMI. It confirms each record exists, parses correctly, and actually aligns with the domain you send from — then reads those findings against the published thresholds Gmail and the other major providers enforce. A record that merely exists is not the same as a record that is doing its job, and the difference is where most audits earn their keep.
What we check, and why each one decides something
Our free domain audit reads SPF, DKIM, DMARC, MX and BIMI for any domain you enter, then a specialist reviews the result alongside the publicly available signals tied to your sending domain before we talk. What follows is what each record governs, so you can judge the findings rather than take them on trust.
SPF — who is allowed to send as you
SPF publishes the list of servers permitted to send mail for your domain. The common faults are not a missing record but a stale one: a platform you stopped using two years ago still authorised, a record that exceeds the DNS lookup limit and silently fails, or multiple SPF records on one domain, which is invalid and can cause the check to fail outright. Each of those reads to a receiver as an unresolved question about whether your mail is really yours.
DKIM — proof the message was not altered
DKIM signs your mail cryptographically so a receiver can confirm it left your infrastructure and arrived unmodified. The failure modes worth finding are a key that was rotated on the sending platform but never updated in DNS, a selector that does not resolve, and signing keys short enough to be treated as weak. A domain can pass SPF and still look unverified if DKIM is broken.
DMARC — and the setting that quietly does nothing
DMARC ties SPF and DKIM together and tells receivers what to do when a message fails both. This is where audits most often find a record that exists and achieves nothing, because the policy is set to p=none. That value means “monitor and take no action” — useful as a deliberate first step while you read reports, and a problem if it has been the permanent setting for two years.
Google’s sender guidelines require DMARC for anyone sending roughly 5,000 messages or more per day to personal Gmail accounts, alongside one-click unsubscribe for marketing mail. Having a record is the requirement; having a policy that does something is what protects the domain.
MX — whether anyone can reply to you
MX records route mail to your domain. They matter to outbound deliverability more than people expect: a sending domain with no working inbound path is a recognised spam signal, because legitimate senders can receive replies, bounces and abuse reports. Audits regularly find sending subdomains with no MX record at all.
BIMI — where a weak DMARC policy costs you visibly
BIMI is what puts your logo beside your mail in supporting clients, and it is the clearest example of why “the record exists” is the wrong test. Google’s own documentation sets conditions most senders fail without knowing: the DMARC policy option must be set to quarantine or reject, and Google states plainly that “BIMI doesn’t support DMARC policies that have the p option set to none.” The percentage option must be pct=100. Gmail displays a checkmark next to senders verified with a Verified Mark Certificate, and supports BIMI only via a PEM file referenced from the TXT record.
So a sender sitting on p=none has not just left DMARC inert — they have disqualified themselves from brand display as well, without any error message to tell them. That single finding is one of the more common things our audit surfaces.
The thresholds your setup is judged against
Records are only half the picture. The other half is the behavioural thresholds published by the providers themselves, because they are the numbers your sending is measured against regardless of how clean your DNS is.
Google asks senders to keep the spam rate reported in Postmaster Tools below 0.3%. That figure is lower than it sounds in practice: it is roughly three complaints in a thousand delivered messages, and a single badly targeted send to an unengaged segment can breach it for the day. Any audit that reports on authentication without telling you where you sit against that threshold has described the plumbing and skipped the diagnosis.
What an audit cannot tell you
Worth being straight about the limits, because they decide whether an audit is the right next step for you.
A record-level audit reads what is published in DNS and what is publicly observable about your domain. It does not, by itself, tell you where a given campaign landed across each provider’s inbox and spam folders — that requires seed testing an ongoing measurement, which is inbox placement monitoring rather than an audit. It will not tell you whether your list is the problem, which is what list management and hygiene addresses. And it cannot repair a reputation that is already damaged; that is a separate programme of work covered under domain reputation repair.
What it does do is tell you, quickly and for nothing, whether your foundations are sound — so that if the answer is yes, you stop looking there and start looking at list and content, and if the answer is no, you fix the cheap things first.
Who should run one
The audit is worth your time if open rates fell without a matching change in your sending, if you are moving to a new sending platform or adding a subdomain, if you are about to scale volume, or if you have inherited a domain’s sending setup from someone who has left. It is also the right first step before a warm-up, because warming a domain with broken authentication teaches providers the wrong thing about you.
It is not worth your time if you already have DMARC at enforcement, clean SPF and DKIM, and a spam rate comfortably inside Google’s threshold. In that case the problem is further down the funnel and we will say so rather than sell you a fix you do not need.
Frequently asked questions
Is the deliverability audit really free?
The domain check is free and you can run it on any domain you control. A specialist then reviews the output against the publicly available signals tied to your sending domain and walks you through it on a call. There is no charge for that review and no obligation afterwards.
How long does an audit take?
The record check returns immediately. The specialist review is the part that takes human time, and we aim to come back within one business day.
Will you need access to my sending platform?
No. Everything the audit reads — SPF, DKIM, DMARC, MX and BIMI — is published in public DNS by design, because that is how receiving servers read it. You do not hand over credentials to find out whether your authentication is sound.
My DMARC record exists. Is that enough?
Not necessarily. If the policy is set to p=none the record is in monitoring mode and takes no action on messages that fail authentication. It also makes you ineligible for BIMI, because Google’s documentation states BIMI does not support a DMARC policy with p set to none. Existence and enforcement are different things, and the audit reports which one you have.
What spam complaint rate should I be aiming for?
Google’s sender guidelines ask senders to keep the spam rate reported in Postmaster Tools below 0.3%, and to never let it reach that level in the first place rather than treating it as a ceiling to approach. Senders at roughly 5,000 messages a day or more to personal Gmail accounts also need DMARC in place and one-click unsubscribe on marketing mail.
Do I need BIMI?
It is not required for deliverability and it will not rescue a damaged reputation. It is worth pursuing once DMARC is already at enforcement, since at that point the main remaining cost is the Verified Mark Certificate. If DMARC is still at p=none, fixing that comes first — it is the prerequisite and the more valuable change on its own.
Get the audit
Bring the domain you send from and we will tell you what the records say, where you sit against the published thresholds, and what to fix first — in that order, and including the case where the answer is that your authentication is fine and the problem is somewhere else. Book a free consultation and we will have read your domain before the call starts.
Sources
- Google, Email sender guidelines — the 0.3% Postmaster Tools spam-rate threshold, and the DMARC and one-click unsubscribe requirements for senders at roughly 5,000 messages a day or more.
- Google Workspace, Add your logo to email messages with BIMI — DMARC policy must be
quarantineorrejectwithpct=100; BIMI does not supportp=none; Gmail shows a checkmark for senders verified with a VMC and supports BIMI only via a PEM file. - M3AAWG Sender Best Common Practices, version 4.0 — industry best common practice for authentication, address collection and sender transparency.
