Why your business email lands in spam

Your invoice went out on Monday. The client says they never got it. You ask them to check their spam folder, and there it is.

You did nothing wrong. Your email did not look trustworthy to the server that received it.

What the receiving server checks

Before it delivers anything, the server looks up your domain and asks: is this sender allowed to send as this company? Your domain answers with three public records, called SPF, DKIM and DMARC. Together they list who may send as you, prove the message was not changed on the way, and say what to do with a message that fails.

If a record is missing, wrong, or out of date, the server gets no clear answer. Unclear gets sent to spam.

Why it breaks

Three causes show up again and again:

1. You added a tool that sends email for you, such as invoicing, a newsletter or a booking system, and nobody told your domain it is allowed.
2. You switched email providers and the old records stayed behind.
3. Two records disagree with each other, so the server trusts neither.

None of these show up in your own inbox. Your sent folder looks fine. The problem sits in the records on your domain, and most owners have not looked at them.

Why ChatGPT could not fix it

It can explain the three records. It has no view of yours. The fix depends on what your domain says today, who sends for you, and which provider you use. A generic answer on a specific domain tends to leave the problem in place.

What fixes it

Someone reads the records on your domain, compares them to every service that sends as you, and corrects the gaps. The step-by-step guide is in our docs. Our free scan does the reading in about three seconds and gives your domain a score out of 10, with the gaps listed.

If the score is 10, you are done. If it is lower, Domain Security is $25 a month per domain, with a one-time $199 fix when the scan finds problems. A domain that scores 10 pays no fix fee. No contract.

Run the free scan on your domain →