A customer tells you they never got your quote. You sent it. You can see it in your sent folder. So you blame their spam filter, resend it, and hope for the best. Sometimes that’s the right call. But sometimes the problem is sitting in your own domain settings, and it’s been quietly killing your deliverability for months.
The problem, in plain terms
When you send an email from your business domain, the receiving mail server runs a quick check: is this message actually from who it says it’s from? Three records in your domain’s DNS, the system that tells the internet where your domain points, are what answer that question. They’re called SPF, DKIM and DMARC.
- SPF (Sender Policy Framework) lists which mail servers are allowed to send email on behalf of your domain. Without it, any server can send mail pretending to be you.
- DKIM (DomainKeys Identified Mail) adds a cryptographic signature, a tamper-evident seal, to each message so the recipient’s server can confirm it wasn’t altered in transit.
- DMARC (Domain-based Message Authentication, Reporting and Conformance) ties the first two together and tells receiving servers what to do if a message fails either check: let it through, quarantine it, or reject it outright.
Missing any one of these doesn’t stop your mail server working. The MX record, the one that actually routes incoming mail to your inbox, can be perfectly configured while all three authentication records are absent. That’s exactly the situation we found during a routine audit for a client recently: MX fine, SPF missing, DKIM missing, DMARC missing. Their quotes were going out. Whether they were arriving is a different question.
What that actually costs you
Work out the number on your own figures. Take the quotes you send in a week, multiply by the average job value, then ask honestly what proportion of “no response” jobs might have simply not arrived. You don’t need a big leak to feel it. Three missed quotes a month on a £500 average job is £1,500 a month in pipeline that disappeared before anyone even read your price.
The secondary problem is spoofing. Without SPF and DKIM, your domain is easy to impersonate. Someone can send an email that appears to come from your address, and there’s no technical signal telling the recipient’s server it’s fake. That matters for your reputation as much as your deliverability.
Three ways to handle this
Option 1: Blame the customer’s spam filter and move on. Sometimes accurate. Occasionally the problem really is on their end. But if you’re hearing “never got it” more than once a month, the odds that it’s always their filter get thin quickly. This option costs nothing and fixes nothing.
Option 2: Switch email providers. Moving from one provider to another, say from a shared hosting mailbox to Google Workspace or Microsoft 365, can improve deliverability because those platforms configure authentication records as part of setup. Google Workspace starts at a few pounds per user per month (check Google’s current published pricing). That’s a reasonable move if you’re on a cheap shared hosting mailbox anyway. But it’s a migration, it takes time, and if your domain records are the problem, switching providers without fixing them just moves the problem to a new address.
Option 3: Check your own domain’s three records first. This takes two minutes and costs nothing. Use MXToolbox’s free checker:
https://mxtoolbox.com/SuperTool.aspx
Type your domain (for example yourbusiness.co.uk) into the box and run the SPF, DKIM and DMARC lookups in turn. The tool tells you whether each record exists and whether it’s valid. If any of them come back missing or broken, you’ve found your problem before spending a penny.
Fixing a missing SPF record is a DNS change, not a rebuild. You log into wherever your domain is registered (GoDaddy, Namecheap, Cloudflare, your hosting panel), find the DNS settings, and add a TXT record. Your email provider’s help docs will give you the exact value to paste in. A typical SPF record for Google Workspace looks like this:
v=spf1 include:_spf.google.com ~all // add this as a TXT record on your domain
DKIM requires generating a key pair through your email provider’s admin panel, then adding the public key as another TXT record. DMARC is a third TXT record that references the first two. None of it requires touching your website or your inbox setup.
The recommendation
Check your records first. It’s free, it takes two minutes, and it either rules out the problem or pinpoints it. If all three records are present and valid, then look at your provider or the content of the emails themselves. If any are missing, fix those before you do anything else, because switching providers or rewriting your quote template won’t help if the authentication problem follows your domain to the new setup.
If you’re not comfortable in DNS settings, or you want a second pair of eyes before you change anything, that’s a straightforward job. I can look up your domain’s three records right now and tell you what’s there, what’s missing, and what needs to change. No commitment, just a clear answer. Tell me your domain on the services page and I’ll come back with what I find.




