Free email deliverability test

Email deliverability test: send a real email, get a scorecard

Get a private test address, send from the setup you actually use, and see a graded breakdown of authentication signals and selected message-level checks.

What this scorecard can prove

DKIM is checked against the message itself: signed headers and body are canonicalized, the public key is fetched from DNS, and the signature is verified according to RFC 6376. The report also checks whether the signing domain aligns with the visible From address, which is the relationship DMARC evaluates.

SPF and DMARC publication signals are read from public DNS. For SPF, the scorecard only reports whether a TXT value begins with v=spf1; it does not validate syntax, duplicate records, DNS lookup limits, or a live result for this message. Selected message-level checks include the one-click unsubscribe mechanism defined by RFC 8058 and keep advisory findings separate from cryptographic results.

This is a deliverability foundation check, not an inbox-placement promise. Provider reputation, complaint rates, engagement, list quality, and each recipient's private filtering remain outside what any external scorecard can prove.

How to run an email deliverability test

  1. Click the button above to get a private test address. It is unique to this report.
  2. Send a message to it from the system you want to test: your mailbox, your newsletter platform, your CRM or the app that sends receipts. Send a real campaign or template, not a one-word test, so the message-level checks have something to read.
  3. Keep this page open. The scorecard appears here, usually within a minute or two.
  4. Fix the red items first, then send again. Each new address is a fresh report, so you can compare before and after.

Test each sending system separately. A domain often passes from Google Workspace and fails from the newsletter tool, because the tool signs with its own domain instead of yours. That gap is the most common reason a domain looks healthy in a DNS check while its campaigns still struggle.

Why a real message tells you more than a DNS lookup

A DNS check of SPF, DKIM and DMARC shows what your domain publishes. It cannot show what a particular sender actually does. Only the message reveals which domain signed it, whether the signature still verifies after your platform added tracking links, whether the envelope sender aligns with your From address, and whether bulk mail carries a working one-click unsubscribe header.

That is why this test verifies the DKIM signature cryptographically against the message you sent, rather than only confirming that a key exists in DNS. A key can be published and still fail, for example after a key rotation that the sending platform has not picked up yet.

How this compares with mail-tester and other spam score tools

Email testing tools tend to fall into three groups, and they answer different questions:

  • Spam score testers, such as mail-tester.com, typically run the message through content-filter rules and return a single score. They are useful for spotting content that filters dislike.
  • Inbox placement tests send your message to seed mailboxes at Gmail, Outlook and others and report where it landed. They are closest to the real experience, but one seed send is a small sample, and placement varies by recipient.
  • Authentication scorecards, which is what this page is, verify the foundations every provider checks first: DKIM signature, alignment with the From domain, SPF and DMARC publication, and bulk-sender basics such as unsubscribe headers and a plain-text part.

This test does not produce a SpamAssassin-style score and does not claim to know which folder your message will land in. If you are looking for a mail-tester alternative because you want to understand why a message fails authentication, this is the right tool. If you want content scoring or seed placement, use one of those alongside it. Fixing authentication first makes either result more meaningful.

What to do with a poor result

  • DKIM missing or signed by the platform's domain: set up a custom sending domain in that platform. The provider setup guides show the exact records for common services.
  • DKIM fails verification: check that the selector in the message matches the key in DNS with the DKIM checker, and that nothing rewrites the message after signing.
  • No DMARC record: publish one at p=none with the DMARC record generator.
  • Missing one-click unsubscribe on marketing mail: turn on List-Unsubscribe and List-Unsubscribe-Post in your sending platform. Gmail and Yahoo expect it from bulk senders.
  • A bounce instead of a report: paste the bounce into the bounce analyzer to decode the SMTP code.

Common questions

Is this a mail-tester alternative?+

It covers a different part of the problem. Spam score testers mostly grade message content against filter rules. This test verifies the DKIM signature on your actual message, checks alignment with your From domain, reads SPF and DMARC publication, and checks bulk-sender basics such as one-click unsubscribe. Many senders use both: this one to fix authentication, a content or placement test for everything else.

How does the email deliverability test work?+

Generate a private test address, send a normal email from the account or campaign tool you actually use, and keep the report page open. A Cloudflare Email Worker verifies the message's DKIM signature and alignment, checks for SPF and DMARC publication signals, and analyzes selected message-level properties. The scorecard appears in your browser without relying on a reply email.

Is the DKIM check a real cryptographic verification?+

Yes. We parse the DKIM-Signature header on the message, canonicalize the signed headers and body as RFC 6376 specifies, fetch the public key from DNS, and verify the signature. We also compare the signing domain with the visible From address for DMARC alignment.

What do the selected message-level checks inspect?+

They inspect one-click unsubscribe headers, a plain-text alternative, image-to-text balance, HTML size against Gmail's clipping threshold, and common spam-signal issues in the subject line. These are observable message signals, not a complete bulk-sender compliance assessment.

Does this prove that my email reaches the inbox?+

No. No external tool can guarantee inbox placement because Gmail, Yahoo, Microsoft, and other providers use private filters plus recipient-specific reputation and engagement signals. This test verifies the authentication and message-level foundations we can directly observe; it does not pretend to simulate a recipient's spam folder.

Why is SPF reported as a publication signal rather than pass or fail?+

A live SPF verdict depends on the sending IP seen by the receiving mail server, which the receiving platform does not expose to this Worker. The scorecard only reports whether it found a TXT value beginning with v=spf1; it does not validate SPF syntax, duplicate records, DNS lookup limits, or a message-specific result.

I sent an email but the report did not appear. What happened?+

Confirm that you sent to the exact private test address shown on the page and allow up to three minutes for delivery. The private report ID is already in the page URL, so you can reload or retry waiting without needing an automated reply.

How long is my report stored?+

The private report URL remains available for 7 days and is then automatically deleted. Anyone with that hard-to-guess URL can view the report during that window, so share it only with people you trust.