Free tool

Email deliverability test

Send one message to a temporary address and read how it arrived: SPF, DKIM, DMARC, the spam verdict, TLS and the unsubscribe headers. No account needed. The report lasts a day.

The SendRaven raven holding a wrench and a magnifying glass

Email deliverability test

No account needed. The address lasts a day and takes one message.

How to read the result

What one message can tell you

This address runs on the same inbound pipeline SendRaven gives customers to receive replies.

Authentication

Whether SPF, DKIM and DMARC passed on a real delivery, and whether the From domain aligns. This is what the records were for.

Content

Spam and virus verdicts on this address, and whether the message has a plain-text part. Other providers run their own filters, so treat this as a floor.

Headers

One-click unsubscribe and TLS as they arrived, after every system between you and the receiver had its turn.

A failure here usually traces back to DNS: the SPF, DKIM and DMARC checkers show why. Then check the rest of the bulk sender requirements.

FAQ

Questions about the deliverability test

How does this email test work?

You get a temporary address and send one message to it from the system you want to test. Our receiving servers record how it authenticated and what the filters said, and this page shows the report. Use the real sending path, because a message typed in your mail client tests your mail client.

Will passing mean my mail reaches the inbox?

No, and no test can promise it. Gmail and Outlook filter on your domain's sending history and how recipients react, which a single message cannot show. This test finds the faults that are certain to hurt, such as failing authentication and missing headers. A new domain with a clean report still needs warming up.

What is kept from my message?

The report holds the message's headers and the filter verdicts, and it is removed after a day. The body is not in the report, but the raw message is held in our mail storage for 30 days and then deleted, as all received mail is. We never reply to or forward it. Send a test message rather than one with personal data in it.

Can I test the same address twice?

Each address records its first message only, so start a new test after changing something. That keeps an old result from being mistaken for a new one.

Next step

Replies as threads, with the authentication already read

The pipeline behind this test is what SendRaven gives you: received mail parsed, joined to the message it answers, and flagged when its sender cannot be trusted.