Free Email Deliverability Test

Check your domain's SPF, DKIM, DMARC and MX records in one click, and see exactly what to fix before your next campaign. Free, no signup.

Your sending domain

Test your email deliverability in one click: MX, SPF, DKIM and DMARC checked live from your browser. Free, with no signup.

How it works

1

Enter your domain

Type your sending domain — or paste an email address and we'll extract the domain.

2

We query DNS live

Your browser looks up the domain's MX, SPF, DKIM and DMARC records over secure DNS.

3

Read each verdict

Every record gets an OK, WARNING, MISSING or ERROR status with plain-English issues.

4

Fix what's failing

Each failing check links to a free generator that builds the correct record for you.

Testing email deliverability starts with your DNS records

When emails land in spam, the first suspects are four DNS records. MX proves your domain can receive replies. SPF lists the servers allowed to send as your domain. DKIM adds a cryptographic signature that receivers verify. DMARC tells Gmail, Yahoo and Outlook what to do when SPF or DKIM fails — and whether to trust your mail at all.

Testing email deliverability therefore starts here: mailbox providers evaluate these records on every single message you send. This free test queries DNS live from your browser and grades each record OK, WARNING, MISSING or ERROR, with the exact issue spelled out in plain English.

One SPF, DKIM & DMARC check — not three separate tools

Most record checkers make you test SPF, DKIM and DMARC in three different tools and stitch the answers together yourself. This test runs all of them (plus MX) in one pass and applies the validation rules that cause real-world failures: multiple SPF records are a permanent error under RFC 7208, +all authorizes anyone to send as you, more than 10 DNS lookups breaks SPF entirely, and a DMARC policy of p=none is monitoring only.

DKIM is the record most tools skip, because it lives under a selector you have to know in advance. We solve that by reading your MX records first: if your mail runs on Google Workspace we probe the google selector, if it runs on Microsoft 365 we probe selector1 and selector2, and otherwise we try the most common generic selectors like default, k1 and mail.

How authentication builds email domain reputation

Gmail and Yahoo score the reputation of your sending domain, and authentication is how that history gets attributed to you. Every message that passes SPF and DKIM with an aligned From domain adds to your domain's track record; unauthenticated mail either builds no reputation or, increasingly, gets rejected before it can.

DMARC is what makes that reputation yours alone: with an enforcing policy, spammers can no longer send as your domain and burn your reputation for you. That is why a complete record set matters even for small senders — it protects the asset every future campaign depends on.

Records are the entry ticket, not the whole game. Once they pass, email domain reputation is earned through engagement: real replies, low bounce rates, and complaint rates kept under 0.3%.

Run this email deliverability check before every campaign

DNS records drift. A new marketing tool adds a second SPF record and silently breaks the first. An IT migration drops your DKIM key. A registrar change wipes the _dmarc entry. A ten-second email deliverability check before each campaign catches these regressions before they cost you a week of inbox placement.

Be equally clear about what a record check cannot see: your actual inbox-versus-spam placement, your live reputation score, or how providers judge your content. Those depend on how you send — which is exactly the part Emailchaser automates, pacing your outreach and personalizing every message so healthy records turn into replies.

Common questions about email deliverability

What does this email deliverability test check?


It checks the four DNS records mailbox providers use to authenticate your mail: MX (can the domain receive replies), SPF (which servers may send for it), DKIM (cryptographic signing, probed across common selectors), and DMARC (the policy that ties them together). Each record gets an OK, WARNING, MISSING or ERROR status plus a plain-English explanation of any issue, using the same rules — like SPF's 10-lookup limit and the one-record rule — that cause real failures.

How do I test email deliverability?


Start with your DNS: enter your sending domain above and the test grades your MX, SPF, DKIM and DMARC records in seconds. If any record is missing or misconfigured, fix that first — it is the most common and most fixable cause of spam placement. Beyond records, deliverability depends on your sending behaviour, so also watch your volume, list quality and reply rates.

Why are my emails going to spam?


The usual causes fall into three buckets: authentication (missing or broken SPF, DKIM or DMARC records), content (spammy wording, heavy links or images), and sending behaviour (sudden volume spikes, stale lists, high bounce or complaint rates). Records are the easiest to diagnose and fix, which is why this test starts there. If your records pass but you still land in spam, look at your list quality and at how much and how fast you send.

What are the Google and Yahoo sender requirements?


Since February 2024, Gmail and Yahoo require all senders to authenticate with SPF or DKIM, and bulk senders (roughly 5,000+ messages a day to Gmail) to have both SPF and DKIM, publish a DMARC policy (at least p=none), align the From domain with the authenticated domain, offer one-click unsubscribe, and keep spam complaint rates below 0.3%. Mail that fails these checks is increasingly rejected outright rather than just filtered to spam.

What is a DKIM selector, and why do you probe common ones automatically?


A DKIM selector is the label that tells receivers where to find your public key in DNS — the record lives at selector._domainkey.yourdomain.com, so it cannot be looked up without knowing the selector name. This test detects your email provider from your MX records and automatically probes that provider's usual selectors: google for Google Workspace, selector1 and selector2 for Microsoft 365, plus common generic names like default, k1 and mail. If you sign with a custom selector, DKIM may still be configured correctly even if the probe reports it missing.

Does this test show my actual inbox placement?


No — and no DNS-based test can. This tool checks whether your authentication records are present and correct, which is necessary for reaching the inbox but not sufficient: actual placement also depends on your domain reputation, content and recipient engagement, which only mailbox providers can see. Treat a passing result as confirmation that nothing in DNS is holding you back, then earn inbox placement through good list hygiene and measured sending.

Ready to 10x your pipeline?

Send your first cold email campaign today, risk-free.

Try for free