Email Deliverability Test
Send one email to a one-time address and see the real SPF, DKIM, DMARC, and ARC results the receiving server recorded — an email tester and email spam test in one, with no headers to copy and no guessing.
An email tester checks whether your email is set up to land in the inbox. To check your email deliverability, send one message to the one-time address below: the receiving server verifies your SPF, DKIM, and DMARC, and we read that verdict back to you with a 0–100 deliverability score — no headers to copy, no guessing.
Preparing your test address…
How it works. When you send mail to the one-time address above, the receiving server cryptographically verifies your SPF, DKIM, DMARC, and ARC and records the result in the message’s Authentication-Results header. We read that header — the receiver’s own verdict, not a prediction — and show it back to you alongside your sending domain’s published SPF record and DMARC policy. Nothing about your message is stored after the verdict is computed; the raw email is discarded immediately and the test address expires within the hour.
What a pass means. A pass for SPF or DKIM is the ground truth for that delivery: the receiver authenticated the message. DMARC pass means an aligned SPF or DKIM identifier matched your From domain — the signal Gmail and Outlook weigh most. If DKIM is absent, the message simply was not signed (its own state, not a failure). For deeper post-hoc inspection of a message you already have, paste its raw headers into the email header analyzer.
Email deliverability test FAQ
Is my email stored after the test?
No. The raw message is held only long enough to read the receiving server’s authentication verdict, then it is discarded immediately. The one-time test address itself expires within the hour. We never log the message body or recipients.
Why did my test time out with no result?
Mail usually arrives within seconds. If nothing shows up, a common cause is an SPF record ending in -all (hard fail): some receivers reject such mail at the SMTP layer before it reaches us, so we never see it. Check your record with the SPF checker, then start a new test.
What does "could not analyze" mean?
We received your message but it did not carry a trusted authentication result from the receiving server. Rather than guess a verdict, we say so explicitly — a false all-pass would be worse than no answer. Send again directly from the inbox you are testing.
How is this different from the email header analyzer?
The email header analyzer parses headers you already have, entirely in your browser. This tool is the opposite end: you send a live message and we read the verdict the receiver recorded for that real delivery. Use the analyzer for a message you have; use this test when you want to send one and see what happens.
How do I check email deliverability?
Send a real message from the inbox you want to test to the one-time address above. The receiving server authenticates it and records SPF, DKIM, and DMARC results, which we read back to you with a 0–100 score — the receiver’s own verdict, not a prediction. If you want to keep the result, the shared result link stays live for about 30 days; the raw email itself is still discarded immediately after the verdict is computed.
How do I test my email spam score?
The most reliable signal a receiver weighs is authentication: a message that passes SPF, DKIM, and DMARC and comes from a sending IP that is not on a major blacklist is far less likely to be filtered as spam. This test sends a live message, checks all three plus your sending IP against common blacklists, and gives you a 0–100 score with the specific gaps to fix. A shared result link stays live for about 30 days, while the raw email is discarded immediately.