Why are my emails going to spam?
Most often because your domain cannot prove the mail is really yours: SPF, DKIM or DMARC is missing, broken or not aligned with the From address. Next come the sending habits that mailbox providers measure, such as spam complaints and the lack of an easy unsubscribe. The checker above tests the records, and this guide covers the habits.
How to stop your emails going to spam
Check your domain
Type your domain, or any address on it, into the checker above. It reads public DNS only, sends no email and needs no access to your mailbox.
Read the verdict for each record
You get a plain result for SPF, DKIM, DMARC and MX, with MTA-STS, TLS reporting and BIMI as optional extras. Each gap comes with the record to publish.
List everything that sends as you
Your mailbox provider, website forms, invoicing tool, CRM, newsletter platform and booking system. Each one must be covered by SPF or sign with DKIM for your domain.
Fix SPF first
Keep one SPF record that names every sender and ends in
~allor-all. Two SPF records on one domain make SPF fail for both.Turn on DKIM in each service
Each sending service gives you a DKIM record to publish. If the checker finds no key on common selectors, look up the selector your provider uses before assuming DKIM is off.
Publish DMARC
Start with
p=noneand a reporting address, read the reports for a few weeks, then move to quarantine and reject once every real sender passes.Fix the habits
Send only to people who asked, put one-click unsubscribe in marketing mail, and keep complaints low. Gmail asks every sender to stay below a 0.3% spam rate.
Check again
Give the new records time to spread, then run your next check on the full email checker page and confirm each row has turned green.
The reasons, and what fixes each one
| Reason | What goes wrong | Fix |
|---|---|---|
| No SPF, or two SPF records | Receivers cannot tell which servers may send for you | One SPF record naming every sender |
| No DKIM | Your messages are not signed by your domain | Turn on DKIM in each sending service |
| No DMARC | You have not said what to do with mail that fails | Publish DMARC, starting at p=none |
| SPF or DKIM not aligned | The domain that passed is not the one in the From line | Send through services set up on your own domain |
| A high spam rate | People mark your mail as spam | Send only to people who asked, and make leaving easy |
| No one-click unsubscribe | Bulk marketing mail lacks a feature Gmail and Yahoo require | Turn on list unsubscribe in your newsletter platform |
| No reverse DNS on the sending IP | The server address does not resolve back to a name | Ask your host or provider to set it |
| MX missing or out of date | Replies to your quotes bounce | Point MX at your current mail provider |
The checker tests the DNS records in this table. Spam rate, unsubscribe headers and reverse DNS sit with your sending tools and your host.
Who uses this check
Business owners
Quotes, invoices and replies that land in a client's spam folder cost deals. One check shows whether your domain is the reason.
Freelancers
Moving from a free mailbox to your own domain? Check SPF, DKIM and DMARC on day one, before you send the first proposal.
Sales teams
Before an outreach push, check the domain you send from, so a low reply rate is not caused by mail that never reached the inbox.
Clinics and schools
Appointment reminders and letters to parents go to personal Gmail and Outlook addresses, where authentication decides whether they are seen.
Online stores
Order confirmations and delivery updates come from your store platform. Make sure it signs with DKIM for your own domain.
Marketers
Newsletters to more than 5,000 Gmail addresses a day need SPF, DKIM, DMARC and one-click unsubscribe, so check before the campaign.
Worked examples
Proposals that vanish
Suppose the check finds two SPF records, one left by your old host and one from your new mailbox provider, and no DKIM key. Two records make SPF fail, so your mail carries no valid authentication at all, while Gmail asks every sender for SPF or DKIM. Merge the two into one record, turn on DKIM in your mailbox provider, then add DMARC.
A newsletter that suddenly lands in spam
Suppose every record passes, yet a campaign goes to spam. Look at the habits instead: a list copied from somewhere else, no one-click unsubscribe, or a spam rate climbing towards 0.3% in Postmaster Tools. Clean the list and send only to people who opted in.
Website form emails in your own spam folder
Suppose enquiries from your contact form reach you as spam. The form sends as your domain through the web host, which is not listed in SPF. Add the host to SPF, or send the form through your mailbox provider, then check again.
UAE tips
Before seasonal campaigns
If you plan email for Ramadan, expected to begin on Monday 8 February 2027 subject to the moon sighting, or for either Eid, check your records weeks before the first send, not on launch day.
.ae domains work the same way
SPF, DKIM and DMARC are DNS records you add wherever your domain's DNS is hosted, whether the domain ends in .ae or .com.
Never send as a free mailbox
Do not put a gmail.com address in the From line of mail sent through another platform. Gmail asks senders not to impersonate Gmail From headers; use your own domain.
A second route for urgent replies
Add a WhatsApp link to your signature, made with the WhatsApp link generator, so a buyer can still reach you if one message is filtered.
What changes in 2027 for email delivery
Now
- Since 2024, Gmail has required every sender to set up SPF or DKIM, use TLS and keep the spam rate below 0.3%, and senders of more than 5,000 messages a day to publish DMARC and offer one-click unsubscribe as well.
- Yahoo applies matching rules (2024), including honouring unsubscribe requests within 2 days.
- Microsoft rejects mail with error 550 5.7.515 when a high-volume sender to its consumer email services does not meet its SPF, DKIM and DMARC requirements (2025).
Next
- AdEngage UAE expects more business mail systems in 2027 to follow the consumer providers, so treat these rules as the baseline for every sender, whatever your volume.
- Treat DMARC at p=none as the starting point, not the goal. Quarantine or reject is what stops other people sending email in your name.
- Recheck after every new tool that sends email for you, because each one needs its own SPF entry or DKIM key.