If customers tell you they never got your quote, or your own inbox shows your newsletter 'delivered' while nobody reads it, your emails are probably landing in the spam folder. This isn't a mystery: mail providers decide based on three records your domain either has, or doesn't. In plain English, here they are and how to check yours.
Check these first, yourself
Send yourself a test email and open it, then click 'show original' (Gmail) to see SPF — A DNS record listing which servers may send email as your domain; missing or wrong, your mail lands in spam., DKIM — A digital signature added to your emails proving they really came from your domain and were not altered., and DMARC — A DNS policy telling mailbox providers what to do when a message fails its SPF or DKIM checks. results at the bottom.
Look for a red line: FAIL, PERMERROR, or 'spf=none'. That's your smoking gun.
Publish an SPF record identifying which servers legitimately send your mail.
Publish a DMARC record that tells Gmail and Outlook what to do with faked mail from your domain.
Should you fix it yourself or call a rescue?
Still have questions?
Is it dangerous to fix SPF myself?
One wrong character in an SPF record can take all your email down. Because it's a text record on your DNS — The internet's address book: it turns your domain name into the server visitors actually reach., the fix is safe to attempt — but small errors are the #1 cause of 'it was working before that change' email emergencies.
Why did deliverability work before and break now?
Something changed: a new sending server, a new tool, or a colleague 'tidyed up' DNS TXT records. Deliverability isn't set once — it has to match exactly what your outgoing mail looks like, which is what the audit checks.