Your enquiry emails land in spam: how to fix it
Set up SPF, DKIM and DMARC for your domain, and stop your website sending mail as the visitor. Both are free and fix most cases.
Quick answer
Enquiry emails land in spam when your domain cannot prove it authorised the message. Setting up SPF, DKIM and DMARC records is free, takes about an hour, and fixes most cases. The other common cause is a contact form sending as the visitor's address rather than your own.
3 records
SPF, DKIM and DMARC, which together prove your mail is genuine
Free
what setting them up costs
The From address
the other cause, when a form pretends to be the visitor
Enquiry emails land in spam when your domain cannot prove it authorised the message. Three DNS records fix most cases, they are free, and adding them is mostly copy and paste from your email provider.
The rest of the problem is usually a contact form claiming to send as the visitor, which is a settings change taking two minutes.
Why this happens
Email was designed without any check on who a message claims to be from. Anyone can send mail saying it comes from your domain, which is why spam and phishing work at all.
Mail providers responded by checking three things. If your domain has not set them up, your genuine mail looks exactly like a forgery, and it gets filed accordingly.
SPF lists which servers are allowed to send email for your domain.
DKIM adds a cryptographic signature proving the message came from you and was not tampered with.
DMARC tells receiving providers what to do when a message fails the first two, and asks them to report back.
None of them are optional any more. Large providers have tightened requirements considerably in recent years, and mail from domains without proper authentication increasingly gets junked rather than delivered.
Key takeaway
This is not something your website is doing wrong. It is something your domain has not been set up to do. The fix lives in DNS settings rather than in the website, which is why web developers sometimes shrug at it and email providers sometimes assume someone else did it.
Fixing it
1. Find out what you have now
Use a free tool like MXToolbox or Mail Tester to check your domain. It reports whether SPF, DKIM and DMARC exist and whether they are valid. This takes two minutes and tells you exactly what is missing.
2. Get the values from your email provider
Google Workspace and Microsoft 365 both publish the exact records to add. If you use your host's email, ask them. These are values to copy, not things to invent.
3. Add them at your domain registrar
Wherever your domain's DNS is managed. Paste the values in exactly, because one wrong character breaks it silently. Changes can take a few hours to take effect.
4. Include everything that sends as you
Your email provider, your website's contact form, any newsletter tool, any booking system. Each needs to be authorised in SPF or it will fail even when the rest is correct.
5. Test again
Send a message to Mail Tester and see the score. Anything below about 8 out of 10 is worth investigating further.
Start DMARC in monitoring mode
A DMARC record can instruct providers to reject failing mail outright. Set it to none first, which monitors without blocking, and check the reports for a few weeks before tightening. Going straight to reject can silently kill legitimate mail from a system you forgot about.
The contact form half of the problem
Separate cause, same symptom, and worth checking even after the DNS is right.
Many contact forms are configured to send with the visitor’s email address in the From field, so replies go to the right place. Sensible in intent, and technically it means your web server is claiming to send on behalf of gmail.com or wherever, which it has no authority to do.
The fix: set the From address to something at your own domain, like website@yourbusiness.co.uk, and put the visitor’s address in reply-to. Replies still reach them, and the message now passes authentication.
Contact form not sending emails covers the wider set of form delivery problems.
Other things that push mail toward spam
Once authentication is right, these are the remaining contributors:
Sending through the web server. Web servers have poor sending reputations, often because of other sites sharing them. Routing mail through a proper sending service fixes this and is free at small business volumes.
Free email addresses in the From field. A form sending as yourbusiness@gmail.com from your website’s server fails checks that a proper domain address would pass.
Spam trigger words in the subject. Less significant than authentication, but “URGENT” and excessive capitals do not help.
No history. A brand new domain sending mail has no reputation, and reputation builds over weeks of normal sending.
What this costs you while broken
Worth stating plainly, because this is easy to leave alone.
Every enquiry filed as spam is a customer who thinks you ignored them. They do not ring back. They go to whoever replied, and you never learn it happened.
A business getting six enquiries a month at £400 a job loses £2,400 a month, silently, for as long as this continues. Businesses regularly discover it after a year.
Check both directions
While you are looking at this, also check that mail you send reaches people. The same records affect your outgoing quotes and invoices, and a quote landing in a customer’s junk folder costs you the same job.
Send yourself a test to a Gmail address and to an Outlook address, and check both inboxes and both spam folders.
Background in why emails land in spam and SPF, DKIM and DMARC explained.
If you would rather not touch DNS records, our managed plans include email authentication setup and monitoring from £49 a month. Or send us your domain and we will tell you free which of the three records is missing, since the check takes us two minutes and plenty of people fix it themselves from there.
Frequently asked questions
Why do my enquiry emails go to spam?
Because your domain cannot prove it authorised them. Mail providers check SPF, DKIM and DMARC records, and if those are missing or wrong, legitimate mail looks forged. The other frequent cause is a contact form that puts the visitor's email in the From field, which your server has no right to send as.
How do I stop emails going to spam?
Set up SPF, DKIM and DMARC records for your domain, which is free and typically takes an hour. Then make sure anything sending mail as your domain, including your website's contact form, is included in those records and sends through a proper mail service.
What are SPF, DKIM and DMARC?
SPF lists which servers may send email for your domain. DKIM adds a signature proving a message was not altered. DMARC tells receiving providers what to do when a message fails those checks. Together they let a mail provider verify your messages are genuinely from you.
Can I fix this myself?
The DNS records are usually added through your domain registrar or hosting control panel, and your email provider gives you the exact values to paste in. It is copy and paste rather than technical work, though getting a character wrong breaks it silently, so check afterwards with a free mail tester.
Written by the A1 Digital team
We handle the entire online presence for small businesses, website, branded email, Google, AI search, content and reviews, for one simple monthly plan. No tech headaches, no lock-in.
On this page
Keep reading
Why your emails land in spam (and how to fix it)
Emails land in spam from missing SPF/DKIM/DMARC, sending via free Gmail, and poor habits. Fix all three and the inbox stops being a guessing game.
DefinitionWhat are SPF, DKIM and DMARC (in plain English)?
SPF, DKIM and DMARC are three DNS records that prove your emails are genuine, so they reach inboxes instead of spam and stop scammers spoofing your domain.
How-toContact form not sending emails: causes and fix
Check spam first, then whether the form sends from your own domain. Most contact form failures are email authentication, not the form itself.